Can I use Granola as a CLI?

Yes. KosmoKrator exposes a Granola CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Granola through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Granola tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Granola credentials stored?

Granola credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Granola MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

meetings

Granola MCP Integration for Claude Code

Connect Granola to Claude Code through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

5 functions 3 read 2 write API key auth

Submit Granola feedback View package source

Connect Granola to Claude Code

Connect local KosmoKrator integrations to Claude Code through one scoped MCP gateway entry.

Add KosmoKrator as a stdio MCP server in the Claude Code project config and select the integrations that should be visible. The gateway is local, scoped to this integration, and starts with --write=deny so Claude Code can inspect read-capable tools without receiving write access by default.

Granola MCP Config for Claude Code

Claude Code can launch the local kosmo binary directly from the project MCP config.

{
  "mcpServers": {
    "kosmokrator-granola": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=granola",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=granola --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Granola instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Granola Tools Visible to Claude Code

Claude Code sees stable MCP tool names generated from the Granola integration catalog.

MCP tool	Source function	Type	Description
`integration__granola__granola_list_meetings`	`granola.granola_list_meetings`	Read	List recent meetings from Granola. Returns meeting titles, dates, participants, and summaries. Supports search by query and date filtering.
`integration__granola__granola_get_meeting`	`granola.granola_get_meeting`	Read	Get a single meeting from Granola by ID. Returns the full meeting details including transcript, summary, notes, and participant list.
`integration__granola__granola_create_note`	`granola.granola_create_note`	Write	Create a note on a Granola meeting. Use this to add follow-up notes, action items, or comments to a meeting.
`integration__granola__granola_share_meeting`	`granola.granola_share_meeting`	Write	Share a Granola meeting with other people. Specify email addresses of recipients and an optional message.
`integration__granola__granola_get_current_user`	`granola.granola_get_current_user`	Read	Get the profile of the currently authenticated Granola user. Returns name, email, and account details.

Related Granola Pages

Granola CLIUse direct JSON commands instead of MCP discovery. Granola MCPFull gateway reference and MCP tool names. KosmoKrator for Claude CodeClient-level gateway setup.