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 CLI for AI Agents

Use the Granola CLI from KosmoKrator to call Granola tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

5 functions 3 read 2 write API key auth

Submit Granola feedback View package source

Granola CLI Setup

Granola can be configured headlessly with `kosmokrator integrations:configure granola`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure granola --set api_key="$GRANOLA_API_KEY" --enable --read allow --write ask --json
kosmokrator integrations:doctor granola --json
kosmokrator integrations:status --json

Credentials

Authentication type: API key api_key. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

Key	Env var	Type	Required	Label
`api_key`	`GRANOLA_API_KEY`	Secret `secret`	yes	API Key
`url`	`GRANOLA_URL`	URL `url`	no	API Base URL

Call Granola Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call granola.granola_list_meetings '{
  "limit": 1,
  "offset": 1,
  "query": "example_query",
  "start_date": "example_start_date",
  "end_date": "example_end_date"
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:granola granola_list_meetings '{
  "limit": 1,
  "offset": 1,
  "query": "example_query",
  "start_date": "example_start_date",
  "end_date": "example_end_date"
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs granola --json
kosmo integrations:docs granola.granola_list_meetings --json
kosmo integrations:schema granola.granola_list_meetings --json
kosmo integrations:search "Granola" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Granola.

`granola.granola_list_meetings`

Read read

List recent meetings from Granola. Returns meeting titles, dates, participants, and summaries. Supports search by query and date filtering.

Parameters: limit, offset, query, start_date, end_date

Generic CLI call

kosmo integrations:call granola.granola_list_meetings '{"limit":1,"offset":1,"query":"example_query","start_date":"example_start_date","end_date":"example_end_date"}' --json

Provider shortcut

kosmo integrations:granola granola_list_meetings '{"limit":1,"offset":1,"query":"example_query","start_date":"example_start_date","end_date":"example_end_date"}' --json

`granola.granola_get_meeting`

Read read

Get a single meeting from Granola by ID. Returns the full meeting details including transcript, summary, notes, and participant list.

Parameters: id

Generic CLI call

kosmo integrations:call granola.granola_get_meeting '{"id":"example_id"}' --json

Provider shortcut

kosmo integrations:granola granola_get_meeting '{"id":"example_id"}' --json

`granola.granola_create_note`

Write write

Create a note on a Granola meeting. Use this to add follow-up notes, action items, or comments to a meeting.

Parameters: meeting_id, content

Generic CLI call

kosmo integrations:call granola.granola_create_note '{"meeting_id":"example_meeting_id","content":"example_content"}' --json

Provider shortcut

kosmo integrations:granola granola_create_note '{"meeting_id":"example_meeting_id","content":"example_content"}' --json

`granola.granola_share_meeting`

Write write

Share a Granola meeting with other people. Specify email addresses of recipients and an optional message.

Parameters: meeting_id, emails, message

Generic CLI call

kosmo integrations:call granola.granola_share_meeting '{"meeting_id":"example_meeting_id","emails":"example_emails","message":"example_message"}' --json

Provider shortcut

kosmo integrations:granola granola_share_meeting '{"meeting_id":"example_meeting_id","emails":"example_emails","message":"example_message"}' --json

`granola.granola_get_current_user`

Read read

Get the profile of the currently authenticated Granola user. Returns name, email, and account details.

Parameters: none

Generic CLI call

kosmo integrations:call granola.granola_get_current_user '{}' --json

Provider shortcut

kosmo integrations:granola granola_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

`granola.granola_list_meetings`

List recent meetings from Granola. Returns meeting titles, dates, participants, and summaries. Supports search by query and date filtering.

Operation: Read read
Schema command: kosmo integrations:schema granola.granola_list_meetings --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of meetings to return (default: 20).
`offset`	integer	no	Number of meetings to skip for pagination.
`query`	string	no	Search query to filter meetings by title or content.
`start_date`	string	no	Start date for filtering meetings (ISO 8601, e.g., "2025-01-01").
`end_date`	string	no	End date for filtering meetings (ISO 8601, e.g., "2025-01-31").

`granola.granola_get_meeting`

Get a single meeting from Granola by ID. Returns the full meeting details including transcript, summary, notes, and participant list.

Operation: Read read
Schema command: kosmo integrations:schema granola.granola_get_meeting --json

Parameter	Type	Required	Description
`id`	string	yes	The meeting ID.

`granola.granola_create_note`

Create a note on a Granola meeting. Use this to add follow-up notes, action items, or comments to a meeting.

Operation: Write write
Schema command: kosmo integrations:schema granola.granola_create_note --json

Parameter	Type	Required	Description
`meeting_id`	string	yes	The meeting ID to add the note to.
`content`	string	yes	The note content text.

`granola.granola_share_meeting`

Share a Granola meeting with other people. Specify email addresses of recipients and an optional message.

Operation: Write write
Schema command: kosmo integrations:schema granola.granola_share_meeting --json

Parameter	Type	Required	Description
`meeting_id`	string	yes	The meeting ID to share.
`emails`	array	yes	Email addresses of the recipients (e.g., ["[email protected]", "[email protected]"]).
`message`	string	no	Optional message to include with the shared meeting.

`granola.granola_get_current_user`

Get the profile of the currently authenticated Granola user. Returns name, email, and account details.

Operation: Read read
Schema command: kosmo integrations:schema granola.granola_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.