Skip to main content
Connect your AI tools to your Granola meeting notes with Granola MCP. Once connected you can use this to: search through your meeting notes, find specific topics discussed in past meetings, browse meeting folders, extract action items or decisions from your notes, answer questions based on your meeting history and more.

​
What MCP can access

MCP connects as you, an individual Granola user. It returns notes you can access in your active workspace — the workspace currently selected in the Granola app — subject to the access scopes below.
  • If you belong to more than one workspace, switch workspaces in Granola (or ask your AI tool to switch for you) before asking another question. MCP does not combine notes across workspaces.
  • Notes created in another workspace are not included, even if you can see them in the active workspace through sharing.
Personal notes access does not include every private note in the workspace. The note must be yours, shared directly with you, or in a private folder shared with you. Your plan and workspace settings determine which scopes MCP uses: If you upgrade from Basic, the extra tools and higher rate limits apply from your next query.

​
Set-up guide

​
Pre-requisites

  • A Granola account with existing meeting notes
  • AI tool that supports MCP, such as Claude and ChatGPT

​
How to connect

You can sign in to your AI tool and Granola with different email addresses. Sign in to the Granola account you want your AI tool to access.
  1. Open and sign in to Claude
  2. Go to Settings
  3. Go to Connectors, search for Granola
  4. Connect, authenticate and make sure you’re toggled on when chatting
  1. Open and sign in to ChatGPT
  2. Go to Settings
  3. Search for ‘Granola’ and connect
  4. You can now @Granola or just ask to reference your meetings in ChatGPT
  1. Run claude in your terminal
  2. Run this command:
  1. Open a new terminal tab and run claude again
  2. Run /mcp, select the granola MCP, and select ‘Authenticate’
  3. Ask Claude to reference your meetings
You can manually connect to the Granola MCP by using the public URL https://mcp.granola.ai/mcp as a custom connection.Your AI tool must support:
  • MCP client protocol using Streamable HTTP transport
  • OAuth 2.0 authentication and metadata discovery — for a standard connection, your tool must be able to open a browser window for the user to sign in to Granola. After sign-in, the tool receives a bearer token to include in subsequent requests.
Each connection acts on behalf of an individual Granola user; there is no API key or service account access method for MCP. Enterprise clients can use Enterprise-Managed Authorization instead of the standard Granola sign-in.
If you need API key access for scripts, automations, or custom integrations, see our Granola API instead.

​
Tools and descriptions

​
Troubleshooting and FAQ

  1. Ask your AI tool: “Which Granola account am I signed in with?” It uses get_account_info to return the email and active workspace connected to MCP.
  2. Right email, wrong workspace: switch workspace in the Granola desktop app (click your workspace name in the bottom-left corner and pick the right one), or ask your AI tool: “Switch my Granola workspace to [workspace name].”
  3. Wrong email entirely: disconnect and reconnect with the correct account. For Claude, see Signed into Claude with the wrong account.
  4. If the account and workspace are right, check that the note is covered by your access scopes.
If you’re getting a message that your LLM agent can’t access your meeting notes or use the Granola MCP tools, try re-authenticating.
If Granola is connected in Claude but shows No tools available, reconnect the Granola connector in Claude to reset the connection:
  1. Go to Claude connector settings on the web. You must do this on claude.ai even if you use the Claude desktop app.
  2. Select Granola.
  3. Click the three-dot menu in the top-right.
  4. Choose Disconnect.
  5. Without refreshing the page or navigating away, choose Connect again and complete authentication.
If you’re on a Claude Team or Enterprise plan, you may need a workspace admin to disconnect and reconnect Granola for you.
Here’s how to reconnect Claude MCP with a different Granola account:
  1. Ask Claude to log out of Granola.
  2. Click the mcp-auth.granola.ai/api/logout link that it gives you.
  3. Ask Claude to reconnect to Granola, and sign in with your main Granola account email.
The reason a normal disconnect/reconnect doesn’t fix this is that your existing Granola session stays active, so it skips the login step. Logging out through the link clears that session, which lets you pick the right account.
First, check which access scopes apply to you:
  • Basic (Free): Personal notes and public notes from the last 30 days.
  • Business: Personal notes and public notes.
  • Enterprise: Workspace admins configure which scopes are available to members.
If you see this error after completing the OAuth sign-in flow, you may have authenticated with a different email address than the one your Granola account is registered under.To check which email your Granola account uses, open the Granola app and go to Settings (⌘ + , on macOS, Ctrl + , on Windows). Your account email is shown under your profile picture in the top left.When reconnecting MCP, make sure you sign in with that same email address during the OAuth flow.
Rate limits will vary depending on your Granola subscription plan and the MCP tool that you’re using. Rate limits currently average around 100 requests per minute across all tools. Rate limits are subject to change.
For a standard browser OAuth connection, no. Granola MCP uses Dynamic Client Registration (DCR), which means credentials are handled automatically. You don’t need to generate or enter any client ID or client secret.If you’re using a third-party platform (like Composio) that shows client ID and client secret fields, leave them blank — the platform will register with Granola automatically when you connect.For Enterprise-Managed Authorization, see Client ID at resource.

​
Enterprise admin controls

Enterprise admins choose which note access workspace members get through MCP:
  1. Go to Settings → Workspace → General.
  2. Find MCP access under Apps & connectors.
  3. Click Manage.
  4. Enable Personal notes, Public notes, both, or neither. If neither is enabled, members have no MCP access.
All Enterprise workspace members can see this setting, but only admins can change it. These note access controls apply to non-admin members; Enterprise admins can always access both personal and public notes through MCP. To stop AI tools from reading meeting transcripts, turn off Meeting transcripts over MCP in the same dialog. It applies to every meeting in your workspace, for everyone who can access it, including admins and people a note is shared with. Notes and summaries stay available. It is on by default. The Make changes over MCP switch lets AI tools add or remove notes from folders and send feedback to Granola. Turn it off to make MCP read-only. It applies to everyone, including admins, and is on by default.

​
Enterprise-Managed Authorization

Enterprise-Managed Authorization (EMA) lets your company approve Granola MCP access once for everyone, instead of each user completing browser OAuth. Users open their MCP client with their work account and Granola is already connected. Each connection uses a signed identity assertion (an ID-JAG). You choose who signs it: The identity source controls who can connect. Granola’s Enterprise admin controls control which notes they can access.

​
Before you begin

You need:
  • A Granola Enterprise workspace with SSO already enabled. SSO is available on Enterprise only, and requires at least 50 seats: 50 active workspace members, or an Enterprise subscription with a minimum commitment of 50 seats.
  • Administrator access to your Granola workspace and to Claude or your IdP, or help from the relevant admins
Each user should already have a Granola account associated with their company identity. If they haven’t used company SSO with Granola before, ask them to sign in to Granola with SSO once before using EMA.

​
Set up Claude auto-connect (beta)

With Claude auto-connect, also called Claude-issued enterprise-managed auth, members with a matching Granola account are connected to Granola in Claude automatically, with no sign-in or consent screen. Members act as themselves in Granola, with the note access they already have. You also need a Claude Team or Enterprise plan, and each member’s Claude email must match the email they use to sign in to Granola.
Granola doesn’t yet have an in-app setting for the Claude issuer URL. During the beta, Granola can register it for an Enterprise workspace that already has SSO enabled (at least 50 seats).
  1. In Granola, enable the note access your company wants to allow under Enterprise admin controls.
  2. In Claude, go to Organization settings > Connectors and select Granola.
  3. Next to Managed authorization, click Set up.
  4. In the Connect step, under Identity source, select Claude-issued.
  5. Copy the Issuer URL shown in Claude. It is unique to your Claude organization.
  6. Send the issuer URL and your Granola workspace name to your Granola account team or hey@granola.so only if this workspace is on Enterprise and SSO is already enabled. SSO requires an Enterprise plan with at least 50 seats (50 active workspace members, or a subscription with a minimum commitment of 50 seats). Wait for confirmation that it’s registered before continuing.
  7. Back in Claude, leave Tenant ID (optional) empty.
  8. Click Run test and confirm that every check passes, and that the authorization server shown is https://mcp-auth.granola.ai.
  9. Click Enable and continue, then choose which roles get the connector. All roles get it by default.
Members with a matching Granola account now see Granola already connected in Claude. A member without a matching account sees the normal Connect prompt. To make sure members only connect through your Claude organization, turn off browser sign-in (individual auth) on the Granola connector in Claude. Otherwise, Claude tries auto-connect first and only offers browser sign-in if it fails. Every other workspace connects Claude with the standard sign-in in How to connect.

​
What to know

  • What Claude confirms. Claude confirms that a person is a current member of your Claude organization with that email address. It doesn’t confirm a sign-in at your IdP or check MFA. Granola receives the member’s email address and an opaque identifier.
  • Offboarding. Removing a member from your Claude organization stops Claude from connecting them to Granola. Remove them from Granola as well, because a token already issued lasts until it expires. With directory sync (SCIM), Claude removes a member when your directory deletes them, but not when it only suspends them.
  • Reassigned email addresses. Before you give a former member’s email address to someone new, remove their Granola account. Otherwise the new person is connected to the old account.
  • Turning it off. In Claude, open the connector’s Managed authorization settings and choose Disable. Members then connect to Granola themselves. To stop trusting Claude entirely, ask Granola to remove the issuer URL.

​
Troubleshooting

Run test stops at the first check that fails. If Claude says Granola’s authorization server address changed, run the test again, check that the new address is https://mcp-auth.granola.ai, and confirm it.

​
Set up with your identity provider

Your IdP and MCP client must support EMA. Granola has tested with Claude & Okta.
  1. In Granola, enable the note access your company wants to allow under Enterprise admin controls.
  2. In your IdP, add or select Granola and enable its managed authorization or resource server capability.
  3. Create a managed resource connection from your MCP client to Granola.
  4. Enter the values below. Your IdP may use different field names or infer some values automatically.
  1. Assign the appropriate users or groups to both Granola and the MCP client, then activate the managed resource connection.
With EMA, assigned users do not complete a separate Granola OAuth consent flow. Their access remains subject to both your IdP policy and the MCP access configured in Granola.

​
If your company builds its own MCP client

The Meeting transcripts over MCP and Make changes over MCP switches apply to everyone, including admins. Your client must implement the MCP EMA extension, obtain an ID-JAG from the company’s IdP, and publish a public HTTPS metadata document that declares private_key_jwt and a jwks_uri. Use Granola’s OAuth metadata to discover the supported capabilities and endpoints, and use the exact advertised issuer as the audience of the client assertion. See the MCP EMA specification for the complete protocol requirements.

​
Example: Claude and Okta

Granola has tested EMA with Claude and Okta Cross App Access (XAA):
  1. In Okta, add the Granola integration.
  2. Open the Resource server tab and enable Cross App Access (XAA).
  3. Follow Okta’s instructions to configure a resource server connector between Claude and Granola.
  4. Use https://claude.ai/oauth/mcp-oauth-client-metadata as the Client ID at resource.