The Granola connector.
Meeting notes and transcripts (Granola). Connect once with your own key. Every agent your team runs reads the same 4 tools under one permission model.
How access is governed
4
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
Granola exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
Granola defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every Granola tool
4 tools, named as the agent sees them.
- list_meetingsread
List recent Granola meeting notes, newest first. Returns id, title, date, and owner for each. Use get_meeting_notes to read the notes body for one of them.
- get_meeting_notesread
Get the full notes for one Granola meeting: title, date, attendees, and the AI-written summary in markdown. Optionally includes the raw transcript.
- search_meetingsread
Find Granola meetings whose title or notes mention a term. Granola has no server-side search, so this scans a recent window of meetings and matches locally — widen `since` if an older meeting is missing.
- list_meeting_foldersread
List the Granola folders available to this workspace. Use a folder id or name with list_meetings to narrow a listing.
Use it from any agent
The same Granola tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a Granola API Key in your Granola account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect Granola once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.