Can I use Google Calendar as a CLI?

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

Can I expose Google Calendar through MCP?

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

Where are Google Calendar credentials stored?

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

Can I deny write access for Google Calendar MCP tools?

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

productivity

Google Calendar CLI for Shell Scripts

Use the Google Calendar CLI for shell scripts with headless JSON commands, schema discovery, credentials, and permission controls.

8 functions 5 read 3 write OAuth browser flow auth

Submit Google Calendar feedback View package source

Google Calendar CLI for Shell Scripts

Call integration functions from shell scripts with stable JSON input and output.

Use shell scripts for small local automations that need one or more integration calls. The Google Calendar CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Google Calendar CLI for Shell Scripts
kosmokrator integrations:configure google_calendar --set access_token="$GOOGLE_CALENDAR_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call google_calendar.google_calendar_create_event '{"calendar_id":"example_calendar_id","summary":"example_summary","description":"example_description","location":"example_location","start_date_time":"example_start_date_time","end_date_time":"example_end_date_time","start_date":"example_start_date","end_date":"example_end_date"}' --json

Discovery Before Execution

Agents and scripts can inspect Google Calendar docs and schemas before choosing a function.

kosmo integrations:docs google_calendar --json
kosmo integrations:docs google_calendar.google_calendar_create_event --json
kosmo integrations:schema google_calendar.google_calendar_create_event --json
kosmo integrations:search "Google Calendar" --json
kosmo integrations:list --json

Useful Google Calendar CLI Functions

Function	Type	Parameters	Description
`google_calendar.google_calendar_create_event`	Write	calendar_id, summary, description, location, start_date_time, end_date_time, start_date, end_date, time_zone, attendees, recurrence	Create a Google Calendar event. Use startDateTime/endDateTime for timed events, or startDate/endDate for all-day events.
`google_calendar.google_calendar_delete_event`	Write	calendar_id, event_id	Delete a Google Calendar event by its ID.
`google_calendar.google_calendar_freebusy`	Read	time_min, time_max, calendar_ids	Check free/busy availability across one or more Google Calendars. Returns busy time slots within the specified time range. Useful for finding open slots for scheduling meetings.
`google_calendar.google_calendar_get_event`	Read	calendar_id, event_id	Get a single Google Calendar event by its ID.
`google_calendar.google_calendar_list_calendars`	Read	max_results, page_token	List all Google Calendars the user has access to.
`google_calendar.google_calendar_list_events`	Read	calendar_id, time_min, time_max, query, max_results, page_token	List or search events in a Google Calendar. Supports date range filtering and text search.
`google_calendar.google_calendar_quick_add`	Read	calendar_id, text	Create a Google Calendar event from natural language text (e.g., "Lunch with Alice tomorrow at noon").
`google_calendar.google_calendar_update_event`	Write	calendar_id, event_id, summary, description, location, start_date_time, end_date_time, start_date, end_date, time_zone, attendees, recurrence	Update an existing Google Calendar event (partial update). Only specified fields are changed.

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 Google Calendar CLI Pages

CI Google Calendar CLI for CI. Cron Jobs Google Calendar CLI for cron jobs. Headless Automation Google Calendar CLI for headless automation. Coding Agents Google Calendar CLI for coding agents.