Skip to main content

Granola

Read your Granola meeting notes, summaries and transcripts.

Connect it with: API key, MCP. Granola's own documentation: https://docs.granola.ai/introduction.

What agents can do​

Connect Granola so the agents working your tasks can reach it. With it connected, they can:

  • Find the notes from a meeting a task names and read its summary.
  • Read a meeting's transcript to pull out decisions and action items.
  • Through Granola's MCP server (sign in with Granola, then link the secret to a project), search notes and ask questions across meetings.
  • List recent meetings, or those in a folder, to prepare a weekly report.

Before you start​

  • A Granola Business or Enterprise workspace. On Enterprise, an admin must turn on API access for members (Settings > Workspace > General).
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Granola​

Granola's MCP server signs you in itself, so connecting needs no key and no app of your own.

  1. In Jaah, open Secrets and select New.
  2. Search for Granola and select its card.
  3. Name the secret and choose who can use it (see Who can use it).
  4. Select Connect Granola, sign in to Granola in the window that opens, and approve the access it lists.
  5. You land back in Jaah on the new secret. Then link it to the projects whose agents should use it (see Use it in an agent session).

Connect with an API key​

Find each value first:

  • API key: Granola desktop app > Settings > Connectors > API keys > Create new key: choose the scopes, then Generate API Key and copy it - Granola shows it once (a Business or Enterprise workspace is required).

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Granola card.
  2. Name the secret and choose who can use it.
  3. Fill in API key.
  4. Select Save. Jaah tests the secret straight away (see Test the connection).

Jaah encrypts what you type and never shows it again — not to you, and not to an admin.

Use your own OAuth app​

Not needed: Granola's MCP server registers Jaah itself when you connect, so there is no app of your own to create.

Test the connection​

Select Test on the secret. Jaah calls Granola's API once (GET https://public-api.granola.ai/v1/notes?page_size=1) with the stored values, and shows whether Granola accepted it, or which value Granola refused and the status it answered. Jaah also tests automatically when you save or reconnect.

The last result and its time stay on the secret's page, so you can see whether it still works without testing again.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.

A key connection hands the agent its fields: api_key.

Tell the agent in your task description which secret to use, for example “use the Granola secret org/granola”.

Granola also runs an MCP server, which gives agents ready-made Granola tools instead of raw API calls. A project's agents get those tools only once you link the secret to the project:

  1. Open the project and its MCP tab.
  2. Select Link, pick the Granola secret, and confirm.
  3. New tasks on the project start with the Granola tools. Tasks already running keep the tools they started with.

Jaah connects agents to the server through a local bridge, so the token never appears in the agent's configuration or its transcript. A Google Antigravity session in the terminal runtime runs without these tools; on ACP it gets them.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Granola once the test passes. Steps: Replace or delete a secret.
  • Reconnect: when Granola ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Granola's side too, revoke Jaah in Granola's settings, or revoke or delete the key at Granola.

Limitations​

  • Granola's API is read-only: agents cannot create or edit notes.
  • Only notes that have a generated summary and transcript are returned.
  • A personal key reaches your own notes and those shared with you; a workspace key, created by an admin, reaches the workspace's shared notes.
  • Agents can do only what the connected Granola account and its granted scopes allow.

Troubleshooting​

Test says Granola rejected the API key (401)

The key was revoked, expired or mistyped. Create a new key under Settings > Connectors > API keys and select Replace on the secret.

There is no API keys option in Granola's settings

Your workspace is not on Business or Enterprise, or an Enterprise admin has not enabled API access for members. Ask your Granola admin.

The secret shows Needs reconnect

The Granola sign-in for the MCP server ended. Select Reconnect and sign in to Granola again.

New tasks on the project have no Granola tools

Link the secret on the project's MCP tab, then start a new task. Tasks already running keep the tools they started with.

Test passes but a meeting is missing

Its notes have not finished generating, or the key's user cannot see them. Wait for the summary, or share the note with that user.

Still stuck? Select Test and read the result: it names the value Granola refused and the status it answered.

FAQ​

Does Jaah record my meetings?

No. Jaah reads the notes Granola already made.

API key or sign-in?

Either. An API key serves the REST API on Business and Enterprise. Signing in serves Granola's MCP server, also on Basic (notes from the last 30 days only); on Enterprise an admin must allow it. One secret holds one of them.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Granola account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.