## Granola integration

Granola is an AI meeting notepad that transcribes meetings and turns them into summarized notes.

Agen.co connects to Granola through Granola's own hosted MCP server as an **Official** connector. Each user authorizes with their own Granola account, and agents can search and read the meeting notes that user can access.

Prerequisites
- A Granola account. No app needs to be registered with Granola — the MCP server registers Agen.co as a client automatically, so there is no Client ID or Client Secret to copy.
- On Enterprise workspaces, an admin controls MCP access under **Settings** → **Workspace** → **General** → **Apps & connectors** → **MCP access**. If neither **Personal notes** nor **Public notes** is enabled there, members have no MCP access, and turning off **Meeting transcripts** blocks transcript access across the workspace.


### Connect Granola in Agen.co

1. In the Agen.co portal, go to **Connectors** → **My connectors** and click **Add connector**.
2. In the **Select connector** drawer, search for `Granola` and select it. The **Add Granola** panel opens.
3. Fill in the field:
| Field | Required | Description |
|  --- | --- | --- |
| **Instance Slug** | Yes | Prefixes each imported tool as `slug__tool`, so several instances of the connector can coexist. Prefilled with `granola`, or with the next free slug such as `granola-2` if Granola is already connected. Use lowercase kebab-case. You can change it later from the connector's settings. |
4. Click **Connect**. Granola opens in a new tab, and the panel shows **Waiting for authorization — complete it in the opened tab…**
5. Sign in to Granola if prompted. On the **MCP OAuth Client would like access to your account** screen, which lists `mcp` as the access requested, click **Allow access**. The requesting client is named **MCP OAuth Client**, with your Agen.co gateway host as the redirect, rather than Agen.co.
6. Back in Agen.co, the panel switches to **Select the tools to import from Granola.** Every tool is toggled on; turn off any you don't want to import, then click **Add**.


The connector is created and its tools imported only when you click **Add**. If you close the panel before that, nothing is saved, even though the Granola tab reported success.

### Authorize each user

Adding the connector doesn't authorize anyone's tool calls yet. The first time each user's agent calls a Granola tool, the call returns an authorization link instead of a result. The user opens the link, signs in to Granola, and clicks **Allow access**. After that, the user's tool calls run with their own Granola account, in the workspace that is active in their Granola account. Notes from other workspaces aren't reachable.

Once connected, Granola appears under **My connectors** with these tools:

| Tool | What it does |
|  --- | --- |
| `query_granola_meetings` | Answers natural-language questions about the user's meetings |
| `list_meetings` | Lists meeting notes the user can access, with title, date, and attendees |
| `get_meetings` | Reads meeting notes, including private notes and summarized notes |
| `get_meeting_transcript` | Reads a meeting's raw transcript |
| `list_meeting_folders` | Lists the folders the user can access |
| `get_account_info` | Returns the email and active workspace of the connected Granola account |


Transcript and folder tools, and notes older than 30 days, aren't available on every Granola account; those calls return an error when the account doesn't include them. Granola limits requests to around 100 per minute across all tools.

Enabling the Granola connector isn't enough on its own. Tool calls remain denied until you create a [policy](/agen-for-work/policies/overview) that grants access to the specific tools you want to expose.

### Additional resources

- [Granola MCP help center](https://docs.granola.ai/help-center/sharing/integrations/mcp)