Skip to main content
Search notes and transcripts, pull out action items or decisions, browse folders, and ask questions across your meeting history directly from your AI tools. On paid plans, your AI tool can also update Granola for you: organize notes into folders, rename meetings, add to private notes, edit summaries, and regenerate a summary using one of your templates. On Business and Enterprise plans, it can also read your agent brief (Enterprise admins can turn this off under Permissions).

What MCP can access

MCP connects as you and returns notes from your active workspace (the workspace currently selected in the Granola app).
  • If you belong to multiple workspaces, switch workspaces in Granola or ask your AI tool to switch for you. MCP only searches one workspace at a time.
  • Notes created in another workspace aren’t included, even if they’ve been shared with you in your active workspace.
Which scopes and tools you get depends on your plan: If you upgrade from Basic, the extra tools and higher rate limits take effect on your next query.

Setup guide

You’ll need a Granola account with meeting notes and an AI tool that supports MCP, such as Claude or ChatGPT.

How to connect

Your AI tool and Granola don’t need to use the same email address. During sign-in, authenticate with the Granola account whose notes you want to access.
  1. Open and sign in to Claude.
  2. Go to Settings > Connectors and search for Granola.
  3. Click Connect and sign in to your Granola account.
  4. Make sure the Granola connector is turned on in your chat.
  1. Open and sign in to ChatGPT.
  2. Go to Settings, search for Granola, and connect your account.
  3. Mention @Granola or ask ChatGPT about your meetings.
  1. Run claude in your terminal.
  2. Add the Granola MCP server:
  3. Open a new terminal tab and run claude again.
  4. Run /mcp, choose granola, and select Authenticate.
  5. Ask Claude about your meetings.
  1. Open Granola in the Cursor Marketplace, or search for Granola under Marketplace in Cursor.
  2. Click Install and sign in to your Granola account when prompted.
  3. Ask Cursor about your meetings.
  1. Open Antigravity and go to Customizations > Marketplace.
  2. Search for Granola and install the plugin.
  3. Sign in to your Granola account when prompted.
  4. Ask Antigravity about your meetings.
  1. Open Granola in Perplexity Connectors, or search for Granola in Perplexity’s connector settings.
  2. Connect and sign in to your Granola account.
  3. Ask Perplexity about your meetings.
Add https://mcp.granola.ai/mcp as a custom MCP connection.Your AI tool needs to support:
  • Streamable HTTP transport from the MCP specification.
  • OAuth 2.0 and metadata discovery, including opening a browser window so you can sign in to Granola and receive a bearer token.
Each connection signs in as an individual Granola user. MCP doesn’t support API keys or service accounts, though Enterprise workspaces can use Enterprise-Managed Authorization to skip individual sign-in.For scripts, automations, or custom integrations that need an API key, use the Granola API instead.

Tools and descriptions

Your AI tool picks the right tools automatically based on what you ask, so you don’t need to name them. Which tools appear depends on your plan, your workspace’s admin controls, and the AI tool you use.

Find and read meetings

Organize and edit notes

Available on paid plans, except list_templates. Your AI tool should only run these when you ask.

Account and profile

Troubleshooting and FAQ

  1. Ask your AI tool: “Which Granola account am I signed in with?” It will return the email address and active workspace connected to MCP.
  2. Right email, wrong workspace: Switch workspaces in the Granola desktop app (click your workspace name in the bottom-left corner), or ask your AI tool to “Switch my Granola workspace to [workspace name].”
  3. Wrong email: Check which email your Granola account uses in Settings (⌘ + , on macOS, Ctrl + , on Windows) under your profile picture in the top left, then reconnect MCP with that email. If you use Claude, follow Signed into Claude with the wrong account below.
  4. Right account and workspace: Check that the note falls within your plan and workspace access scopes (for example, the 30-day window on Basic or your Enterprise admin’s scope settings).
If your AI tool reports that it can’t reach Granola or run MCP tools, disconnect Granola in your AI tool’s settings and sign in again to refresh the connection.
Reset the Granola connector in Claude to restore the tools:
  1. Open Claude connector settings in a browser (even if you use the Claude desktop app).
  2. Select Granola, open the three-dot menu in the top right, and choose Disconnect.
  3. Without refreshing or leaving the page, click Connect and sign in again.
On a Claude Team or Enterprise plan, a workspace admin may need to disconnect and reconnect Granola for you.
A normal disconnect and reconnect keeps your existing Granola browser session active, so Claude skips the login screen. To switch accounts:
  1. Ask Claude to log out of Granola.
  2. Open the mcp-auth.granola.ai/api/logout link it returns to clear your Granola session.
  3. Reconnect Granola in Claude and sign in with the email address for your Granola account.
Each tool has its own rate limit, which depends on your plan. These are the standard limits; some accounts have lower ones, and limits may change over time.
  • Paid plans: most tools allow 5 requests per second. query_granola_meetings allows 50 an hour, and tools that edit notes have lower limits, such as 10 summaries an hour.
  • Basic (Free): query_granola_meetings allows 15 requests an hour, get_meetings, get_meeting_attachment, and list_templates allow 10 an hour each, and other tools allow up to 2 a second.
Not for a standard browser OAuth connection. Granola MCP uses Dynamic Client Registration (DCR), so your AI tool registers itself automatically.If a third-party platform (such as Composio) shows client ID and client secret fields, leave them blank. For Enterprise-Managed Authorization, see Client ID at resource under Set up with your identity provider.

Enterprise admin controls

Enterprise admins choose what AI tools can read and change through MCP in Settings > Workspace > General > Apps & connectors > MCP access. All Enterprise workspace members can view these settings, but only admins can change them.

Note access

Turn on Personal notes, Public notes, both, or neither. If neither is enabled, workspace members have no MCP access. These note access controls apply to non-admin workspace members; Enterprise admins can always access both personal and public notes through MCP.

Permissions

Permissions apply to everyone in the workspace, including admins. All permissions are on by default. To make MCP read-only, turn off Organise notes, Edit notes, and Send feedback.

Enterprise-Managed Authorization

Enterprise-Managed Authorization (EMA) lets your company approve Granola MCP once for everyone, so workspace members don’t have to sign in individually through a browser. When they open their AI tool with their work account, Granola is already connected. EMA works by having a trusted identity source sign an identity assertion (an ID-JAG) for each user: Your identity source decides who can connect; Granola’s Enterprise admin controls still decide which notes they can see and what permissions they have.

Before you begin

EMA requires:
  • A Granola Enterprise workspace with SSO enabled (SSO requires Enterprise with at least 50 seats: 50 active workspace members, or a subscription committing to at least 50 seats).
  • Admin access to Granola and to either Claude or your IdP.
Each workspace member also needs an existing Granola account tied to their company identity. If someone hasn’t signed in to Granola with company SSO yet, have them sign in once before using EMA.

Set up Claude auto-connect (beta)

Claude auto-connect (also called Claude-issued enterprise-managed auth) connects workspace members to Granola in Claude automatically, without a sign-in or consent screen. Each person acts as themselves in Granola with their normal note access. You’ll need a Claude Team or Enterprise plan, and each person’s Claude email must match their Granola email. Workspaces without Enterprise and SSO should use the standard flow in How to connect. You register Claude’s issuer URL yourself in Granola, under Enterprise-managed authorization in Settings > Workspace > General > Apps & connectors > MCP access. Only Enterprise admins can see this section. Your workspace’s domain must be verified for SSO.
  1. In Granola, configure the note access you want 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, set Identity source to Claude-issued.
  5. Copy the Issuer URL shown in Claude (this is unique to your Claude organization).
  6. In Granola, open MCP access. Under Enterprise-managed authorization, click Manage next to Claude managed access.
  7. In the page that opens, paste the issuer URL and save it.
  8. Back in Claude, leave Tenant ID (optional) blank.
  9. Click Run test and confirm every check passes, with https://mcp-auth.granola.ai shown as the authorization server.
  10. Click Enable and continue, then pick which roles should receive the connector (all roles are selected by default).
Workspace members with a matching Granola account will see Granola already connected in Claude; anyone without a matching account will see the normal Connect prompt. If you want to prevent individual browser sign-ins, turn off individual auth on the Granola connector in Claude. Otherwise, Claude tries auto-connect first and falls back to browser sign-in if it fails.

Things to keep in mind

  • Identity checks: Claude confirms that someone is an active member of your Claude organization with that email address, and sends Granola their email and an opaque ID. It doesn’t verify an IdP sign-in or MFA.
  • Offboarding: Removing someone from your Claude organization stops future connections, but remove them from Granola too so existing tokens don’t stay valid until expiry. If you use SCIM directory sync, Claude removes users when they are deleted from your directory, not when they are only suspended.
  • Reassigned emails: Remove a former employee’s Granola account before reusing their email address for someone else, or the new hire will connect to the old account.
  • Turning it off: Open the connector’s Managed authorization settings in Claude and click Disable to return to individual sign-in. To stop trusting Claude completely, remove the issuer URL with Manage next to Claude managed access in Granola.

Troubleshooting

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

Set up with your identity provider

Your IdP and MCP client both need to support EMA. Granola has tested this with Claude and Okta.
  1. In Granola, configure the note access you want to allow under Enterprise admin controls.
  2. In your IdP, add or open Granola and enable its managed authorization or resource server capability.
  3. Create a managed resource connection from your MCP client to Granola using these values (field names vary by IdP, and some values may be filled in automatically):
  1. Assign the right users or groups to both Granola and the MCP client, then activate the connection.
Assigned users won’t see a Granola OAuth consent screen. Their access is governed by both your IdP policy and Granola’s MCP settings.

Building your own MCP client

To connect a custom client with EMA, implement the MCP EMA specification, obtain an ID-JAG from your IdP, and publish a public HTTPS metadata document declaring private_key_jwt and a jwks_uri. Discover supported endpoints and capabilities from Granola’s OAuth metadata, and use the advertised issuer as the audience for your client assertion.

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 guide to configure a resource server connector between Claude and Granola.
  4. Enter https://claude.ai/oauth/mcp-oauth-client-metadata as the Client ID at resource.