Skip to main content
Connect Granola when what customers say in support conversations needs to be read against what was said in meetings: a renewal call that raised the same complaint, a product review where a fix was promised, or a customer call that explains a spike in tickets. The Rippit agent searches your Granola notes, reads the meetings it finds, and links back to each note in its answer.

​
What the agent gets

  • Natural-language search across your meeting notes, with citations that link to each source note in Granola.
  • Meeting lists for a time range or folder, with titles, attendees, and note links.
  • Meeting details: your private notes, Granola’s AI summary, attendees, and metadata.
  • Transcripts, verbatim, when the exact wording matters. Paid Granola plans only.

​
Setup

Click Connect and sign in to Granola. There is nothing to create first: Granola’s MCP server uses browser sign-in and registers Rippit automatically, so there is no client ID, client secret, or API key to enter. On Granola Enterprise, MCP is off until a Granola workspace admin enables it in Granola’s security settings.

​
Identity, scope, and plan limits

The connection acts as the Granola user who signed in. Granola’s MCP server offers no API key or service-account option, so the connection can only ever see one person’s notes. What that person’s notes include depends on their Granola plan: On every plan, meetings shared with the user through shared folders are not returned. If you share the connection organization-wide, everyone using the agent reads the connecting person’s notes. Connect with an account whose meetings you are comfortable exposing that way.

​
Tools

Granola’s tools are all read-only. Manage tools on the connection card is the authoritative list for your connection; enable a tool there if it is not already on. A meeting’s ID is the UUID at the end of its Granola link, https://notes.granola.ai/d/<uuid>.