Granola can give Aurora access to meeting notes the connected user is permitted to see. Finta can connect those notes to durable relationship context, surface commitments and changed investor signals, and prepare the next move for review.
The differentiated job is not another meeting summary. It is turning conversation evidence into relationship momentum while preserving the source, the evidence boundary, and the user's judgment. Finta's catalog configuration matches Granola's official endpoint and dynamic OAuth model. Sanitized production evidence shows connected records and a six-tool inventory, but no successful meeting read was captured in this campaign.
Current status
| Connection detail | Current evidence |
|---|---|
| Connection model | Catalog MCP |
| Official server | https://mcp.granola.ai/mcp |
| Official transport | Streamable HTTP |
| Official authentication | Granola user OAuth with dynamic client registration |
| Finta repository configuration | Endpoint, metadata URL, and oauth_dynamic mode aligned on August 22, 2026 |
| Production connection state | Five records observed, including three in connected state, on August 22, 2026 |
| Live tool inventory | Six exact tool names stored on the latest connected record |
| Known meeting read | Pending |
| Transcript availability | Plan-dependent and pending account proof |
Granola's official hosted MCP flow uses browser OAuth and dynamic client registration. Granola says the ordinary connection does not require the user to paste an API key or create a service account.
The production review used sanitized aggregate state only. It did not expose organization identifiers, user identities, credentials, tokens, meeting titles, or provider content.
Publish this as a configuration and tool-discovery-backed workflow guide. One stored production inventory does not prove that every Granola user, workspace, or plan receives the same access, and it is not evidence that a meeting read succeeded.
What is documented and what Finta verified
Granola documents the following tools for its hosted MCP server, and the same six exact names were stored on Finta's latest connected production record. The plan, workspace, and user still determine what content each tool can access.
| Tool or capability | Purpose | Finta evidence |
|---|---|---|
| query_granola_meetings | Query permitted meetings using natural language | Exact name discovered in production; safe query pending |
| list_meeting_folders | List meeting folders | Exact name discovered in production; plan-specific behavior pending |
| list_meetings | List meetings visible to the connected user | Exact name discovered in production; safe list pending |
| get_meetings | Retrieve meeting content | Exact name discovered in production; known-meeting receipt pending |
| get_meeting_transcript | Retrieve a transcript when available | Exact name discovered in production; plan-specific safe read pending |
| get_account_info | Return connected Granola account information | Exact name discovered in production; sanitized account receipt pending |
Setup and proof path
- Sign in to Finta and confirm the intended organization before connecting a personal Granola account.
- Open Aurora, select the plus control, and choose Connect App.
- Search for Granola and select Sign in with Granola.
- Review Granola's authorization screen and authorize the intended user and workspace.
- Return to Aurora and open Manage tools for the Granola connection.
- Capture the exact tools/list response rather than assuming every documented tool is available.
- Run get_account_info and verify the connected user and workspace before querying meetings.
- Choose one known non-sensitive investor meeting and retrieve its title, date, attendees, and note content.
- Reconcile the result directly in Granola, including the source meeting and the user's access to it.
- Use transcript retrieval only when it appears in the live tool list, the account plan permits it, and the additional detail is necessary.
- Keep generated follow-up in a prepared state until the user reviews the evidence, recipients, and complete draft through the separately connected Finta workflow.
Flagship workflow
Investor conversation to source-linked commitments ledger
This workflow turns permitted conversation evidence into accountable relationship follow-through. It preserves the difference between what the investor said, what Aurora inferred, and what the user chooses to do next.
- Identify the exact investor meeting by participant, date, and title.
- Confirm the connected Granola account and workspace before reading meeting content.
- Retrieve the permitted meeting notes and retain the source meeting identifier.
- Use a transcript only when it is available, necessary, and allowed by the user's plan and permissions.
- Extract direct evidence for investor interests, objections, questions, promises, and timing.
- Match the participants and fund with Finta contacts, companies, and the active deal.
- Separate direct meeting evidence from Aurora inference and unresolved ambiguity.
- Create a commitments ledger with owner, action, due date, confidence, and source passage.
- Recommend one next move based on the relationship stage, the commitment, and its timing.
- Draft the follow-up but do not send or mutate CRM records as part of the read-only analysis.
Sample prompts
Using Granola, find my latest meeting with the selected investor. Return the meeting title, date, attendees, and cited note passages. Match it to Finta relationship context, list every commitment, and draft the follow-up. Do not send or change CRM records.Search my permitted Granola meetings from the last thirty days for investors who asked for updated traction. Show the supporting meeting and passage for each result, then rank the follow-up by stated timing.Compare prior Granola notes for the selected fund. Flag changes in thesis, timing, objections, or next steps. Keep direct statements separate from inference and identify missing context.
Expected output
The output specification below describes the evidence a useful result should contain. It is not presented as a live tool receipt unless the verification ladder says otherwise.
| Output field | Expected evidence |
|---|---|
| Connected account | Granola user, active workspace, and account context |
| Source meeting | Meeting identifier, title, date, attendees, and source location |
| Evidence | Cited note or transcript passages supporting each statement |
| Finta relationship context | Matching contact, fund, deal, stage, relationship owner, and relevant prior context |
| Commitments | Owner, action, requested material, due date, and supporting passage |
| Changed signal | New objection, thesis shift, timing update, or re-engagement evidence |
| Evidence boundary | Direct statement, Aurora inference, and unresolved question separated |
| Recommended next move | One relationship-aware action with timing rationale |
| Draft follow-up | Prepared subject and body, not sent |
| Completed writes | None in the read-only workflow |
| Limitations | Plan, workspace, transcript, recency, or transcription caveat |
Permissions and limitations
- Granola access follows the connected individual user and the notes they are permitted to see in the active workspace.
- Granola says the MCP server does not combine notes across separate workspaces.
- Basic-plan access can be limited to recent personal notes, while Business and Enterprise visibility depends on plan and workspace policy.
- Folder and transcript tools can require a paid plan.
- Enterprise administrators can control access and scopes for their workspace.
- Granola currently documents an approximate average limit of one hundred requests per minute across tools, subject to change.
- Meeting notes and transcripts can contain transcription, speaker-attribution, and summarization errors.
- The user should verify consequential investor statements against the underlying note or recording context.
- A tool stored for one connected production record is not proof that it appears for every Finta user, workspace, or plan.
- The documented Granola tool set is read-oriented. Any future write-capable tool must receive a separate review and verification ladder.
- Preparing a follow-up from Granola evidence does not authorize an external send or an automatic CRM mutation.
Verification ladder
| Evidence level | Evidence | State |
|---|---|---|
| Level 0 | Granola MCP, permissions, plan, and rate-limit documentation reviewed | Complete, August 22, 2026 |
| Level 1 | Finta Granola endpoint, metadata URL, and oauth_dynamic catalog configuration inspected | Complete, August 22, 2026 |
| Level 2 | Sanitized production connection state observed | Complete, August 22, 2026; five records included three connected states |
| Level 3 | Exact six-tool inventory captured on the latest connected record | Complete, August 22, 2026 |
| Level 4 | Connected account and active workspace confirmed with get_account_info | Pending |
| Level 5 | One known meeting returned and reconciled in Granola | Pending |
| Level 6 | One commitment ledger manually checked against the source note | Pending |
| Level 7 | Transcript behavior tested for the connected plan, if claimed | Pending |
| Level 8 | Reversible write | Not applicable to the currently discovered read-only tool set; reassess if discovery changes |
| Level 9 | Public page, metadata, image, and responsive rendering | Complete, August 22, 2026 |