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 Headless Automation

Use the Granola CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

5 functions 3 read 2 write API key auth

Submit Granola feedback View package source

Granola CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Granola CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Granola CLI for Headless Automation
kosmokrator integrations:configure granola --set api_key="$GRANOLA_API_KEY" --enable --read allow --write ask --json
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

Discovery Before Execution

Agents and scripts can inspect Granola docs and schemas 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

Useful Granola CLI Functions

Function	Type	Parameters	Description
`granola.granola_list_meetings`	Read	limit, offset, query, start_date, end_date	List recent meetings from Granola. Returns meeting titles, dates, participants, and summaries. Supports search by query and date filtering.
`granola.granola_get_meeting`	Read	id	Get a single meeting from Granola by ID. Returns the full meeting details including transcript, summary, notes, and participant list.
`granola.granola_create_note`	Write	meeting_id, content	Create a note on a Granola meeting. Use this to add follow-up notes, action items, or comments to a meeting.
`granola.granola_share_meeting`	Write	meeting_id, emails, message	Share a Granola meeting with other people. Specify email addresses of recipients and an optional message.
`granola.granola_get_current_user`	Read	none	Get the profile of the currently authenticated Granola user. Returns name, email, and account details.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Granola CLI Pages

CI Granola CLI for CI. Cron Jobs Granola CLI for cron jobs. Shell Scripts Granola CLI for shell scripts. Coding Agents Granola CLI for coding agents.