Claude Granola connectorWhat Claude can do in your Granola account.
The Claude Granola connector exposes 4 tools. 3 read your meeting notes, 0 write anything back, and 1 has no official description at all. Below: what Claude can pull up, what your Granola workspace keeps out of reach, and who can cut access.
Verified Trustpilot reviews · AI, automation & growth agency
Why plug Granola into Claude
Granola already sits in your calls and writes the notes. Once connected, Claude can open those notes while it answers you. Ask what the customer said about the rollout date, and Claude finds the call, reads what Granola captured and gives you the answer in the chat. No app switching, no copy and paste.
Find the call when you only remember the person. You spoke with a vendor last Thursday but the calendar invite had a vague title. list_meetings returns the notes you can access with dates and attendees, so Claude can narrow it down.
Turn notes into a to-do list. Before a weekly sync, get_meetings opens the notes themselves, summaries and your private jottings included. Claude pulls out who still owes what.
Quote people exactly. When a summary is too smooth, get_meeting_transcript brings back the raw transcript, handy when a recap has to use the customer's own words.
What Claude does not do here: by default, its sheet only exposes reading. No documented tool drafts, files or shares a note in Granola. Treat that as an observed floor, not a hard guarantee. It also sees one Granola workspace at a time, the one active in the app. And nothing runs by itself: no note gets pushed to Claude when a call ends. That kind of hands-off chain is the job of an automation tool, which is a different trade; the Integrations hub covers that side. To see what a connector that does write looks like, compare with the Claude airtable connector.
Five terms before you connect
Enough vocabulary to read the rest of this page without tripping.
- Connector
- The link you set up once between Claude and your Granola account, so Claude can work with it while it answers you.
- Tool
- One named capability the connector opens to Claude. Claude decides which ones to call, and the directory sheet lists each by name.
- Authorization
- Granola's own sign-in screen, where you hand Claude the access it will use later. Given once per person, and revocable the same way.
- Approval
- The confirmation Claude waits for before it goes through with something that would change your account, shown right in the chat.
- MCP
- The shared standard behind every connector: it is what lets an assistant like Claude talk to an outside service such as Granola.
Connect Granola to Claude in three steps
- 01
Find Granola in your settings
In Claude's settings, go to Customize, then Connectors, and look for Granola. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector for the organization first; each member then signs in on their own.
- 02
Sign in to your account
Click Connect on the Granola row and sign in through the window Granola opens itself. If you keep a personal and a work account, pick the one that actually holds your team calls.
- 03
Review the authorization screen
Read the authorization screen before you accept. It belongs to Granola, not Claude, and it decides what the access covers. If the link breaks later, hit Disconnect and connect again; you can also revoke it from Granola.
The 4 tools of the Claude Granola connector
Granola gives Claude 4 tools: 3 that read your account, 0 that change something in it, and 1 no official source describes.
Three lookup tools and one name nobody documents. Tool names stay exactly as Claude shows them.
- 3 read
- 1 not documented
What Claude reads (3)
3 toolsThree tools that look at your meetings without touching them.
list_meetings
Returns the meeting notes your account is allowed to open, each with its ID, title, date and attendees. Claude uses that roster to zero in on the right call before reading anything.
get_meetings
Opens the substance of one or more meetings: attendees, date, the summary Granola wrote and the private notes you typed. This is what gives Claude something real to reason about.
get_meeting_transcript
Pulls the raw transcript of a meeting rather than the summary, so Claude can quote a line word for word instead of paraphrasing it.
Undocumented (1)
1 toolThe directory publishes this name and nothing else. No official source says what it does, and a name is not a description.
query_granola
This name shows up in the directory list and nowhere else: no official source documents what it does. Granola's help describes a tool with a similar name, but not this one, and the two are not treated as the same.
What Claude checks with you first
By default, Claude stops and asks before any action it takes on an account on your behalf. Here, the three documented tools only read.
On a Team or Enterprise workspace, owners decide whether members can let some actions through without being asked every time. They can also cap what a connector may do across the whole organization, for instance allow reading and block writing, and nobody can override that from their own account. Claude also works with your Granola permissions and nothing more: a note you cannot open yourself stays invisible to it. The official read-versus-write label for each tool only appears inside the settings of a connected account, never on a public page.
Which Claude plans include Granola
None of the 819 directory sheets shows plan availability. For individual connectors, that information is simply not published anywhere, and that is a genuine gap in the catalog.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members can connect one by one. For Granola's current status on your account, check its sheet in the official directory. Granola's own tiers are a separate matter: they change what the tools return, covered under limits below.
Where the Granola connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing fires when a meeting wraps up.
Only the publisher documents this connector: neither Claude's help center nor Anthropic's developer docs have a page on it, so the limits below come from Granola's help article. The tool list is an observed floor, not a ceiling, since an admin can open actions no public sheet mentions. The partner badge in the directory is not a security audit either, and Anthropic says on every sheet that it does not pick a publisher's tools or vouch for how they behave. Granola's help also lists tools that are missing from the directory sheet and names one of them differently. The name Claude shows you is the one that counts.
Need help connecting Granola to Claude?
A person reads every message.
