Configure the Granola MCP Server

Overview

Granola operates an official hosted MCP server at mcp.granola.ai for meeting notes, transcripts, and folders. Access is authorized through OAuth 2.1 with dynamic client registration, so there’s no OAuth app to create in Granola first — the gateway registers itself when a user authorizes.

1. Add the MCP server to your gateway config

Go to your gateway in the Dtwo UI and open Configuration → Advanced. In the mcp_servers section add the following entry:

  - name: granola
    description: "Granola's official hosted MCP server for meeting notes, transcripts, and folders."
    url: https://mcp.granola.ai/mcp
    transport_type: streamablehttp
    authentication:
      type: oauth
      grant_type: authorization_code
      issuer: "https://mcp-auth.granola.ai"
      redirect_uri: "<CALLBACK_URL>"
      scopes:
        - openid
        - profile
        - email
        - offline_access
      dcr_enabled: true
      pkce_enabled: true

Replace the placeholder value:

• <CALLBACK_URL> — your Dtwo gateway’s OAuth callback URL, found in the Overview tab for your gateway in the Dtwo UI.

Granola doesn’t use per-tool permission scopes — the scopes above just identify the user and let the gateway refresh their token without sending them back through sign-in. What the agent can actually read is decided by the authorizing user’s plan and workspace settings.

2. Deploy and verify

Save the configuration and deploy the gateway.

Then, in your AI client, ask it to authorize Granola via the gateway. This opens the Granola sign-in and consent screen — sign in as the user whose notes the agent should access, and approve the consent prompt. Once authorized, confirm the server’s tools appear and run a quick call, such as listing recent meetings, to make sure the connection works.

If the tools don’t appear after you authorize, refresh the tool list in your AI client — some clients don’t pick it up automatically.