meetings
Granola MCP Gateway for AI Agents
Expose Granola tools to Claude Code, Cursor, Codex, and other MCP clients through the local KosmoKrator MCP gateway.
5 functions 3 read 2 write API key auth
Granola MCP Gateway
Expose Granola to MCP clients with `kosmokrator mcp:serve --integration=granola`.
If the client has never used KosmoKrator before, install it first, then register this integration as a stdio MCP server. The gateway exposes only the selected integration in the example below.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash kosmokrator mcp:gateway:install --integration=granola --write=deny --json {
"mcpServers": {
"kosmokrator-granola": {
"type": "stdio",
"command": "kosmo",
"args": [
"mcp:serve",
"--integration=granola",
"--write=deny"
]
}
}
} Serve Manually
kosmokrator mcp:serve --integration=granola --write=deny MCP Tool Names
KosmoKrator exposes integration tools through the gateway with stable names:
| MCP tool | Source function | Type |
|---|---|---|
integration__granola__granola_list_meetings | granola.granola_list_meetings | Read read |
integration__granola__granola_get_meeting | granola.granola_get_meeting | Read read |
integration__granola__granola_create_note | granola.granola_create_note | Write write |
integration__granola__granola_share_meeting | granola.granola_share_meeting | Write write |
integration__granola__granola_get_current_user | granola.granola_get_current_user | Read read |
Write Access
Start with --write=deny for read-only MCP clients. Use --write=ask or
--write=allow only when the client and workspace are trusted.