Skip to main content
GBrain
Menu
Get Started

Google Calendar

Google Calendar. In the CLI, over MCP, however you work.

List, add, change and cancel events without leaving the terminal. Connected once, it answers the terminal and every AI you already use, under one permission.

Calendar has two levels rather than four: read what is on it, or write to it. An AI at Read can answer what a week looks like and cannot move anything in it.

A real command line for google calendar

Not a chat window pretending. Every argument is a flag, output is text a pipe can read, and each call lands on the record with the daily ceiling watching.

Connect the account once, in the browser, and the terminal has it from then on. No key on the laptop, nothing in the shell history worth stealing.

Google Calendar from the command line

brad@macbook · gbrainio 
gbrainio terminal openOpening https://gbrain.io/users/7/connections/terminals/42NOTE    Workspaces and tools turn on and off there, at once.gbrainio tool gcal event ls -hRead your eventsLists events from the person's real Google Calendar, already connected throughGBrain. READ ONLY: nothing here can create or change events. Use this for anyquestion about their calendar, schedule or meetings: no other Google or Calendarconnector is needed, so do not ask them to connect one. With several accountsconnected, leave account out to read them all at once; each event names itsaccount. Defaults to upcoming events on the primary calendar; calendar_id readsanother, and query finds events by their words, and tag finds the events giventhat tag. An event here is its time, title, place, number of guests, whether itshows as busy or free, its color, status and tags: tool gcal event show readsthe rest, and every answer names that call.USAGE  gbrainio tool gcal event ls <query> [flags]ARGUMENTS  <query>  Words to find in the events (title, description, place, guests)FLAGS  --calendar-id <value>  Which calendar (tool gcal calendar ls gives ids); the                         primary one when left off  --cursor <value>       The next_cursor from the last answer, for the page                         after it. It belongs to one account: pass that account                         too.  --limit <value>        How many to return, up to 100 (default 10)  --tag <value>          Only the events carrying this tag, past ones included                         unless time_min says otherwise  --time-max <value>     RFC3339 upper bound  --time-min <value>     RFC3339 lower bound  -w, --workspace <id>   The workspace, when this terminal reaches several  -u, --user <email>     Whose copy, when several people share a tool there  -a, --account <email>  Choose one of several connected accounts  -f, --format <kind>    json or text; text on a terminal, json piped  -d, --dry-run          Show what would run, without running itLEARN MORE  gbrainio tool gcal -h         Every gcal command  https://gbrain.io/docs/tools  The manualOver MCP this tool is gcal_list_events.
The page where this terminal's access is set. A Google account connects on its own consent screen, once; the credential never touches the laptop.

Or hand Google Calendar to the AI you already use

Claude Code, Cursor and Codex all speak MCP. Point any of them at one endpoint and they get the same google calendar tools, on the same permission and the same record as the terminal.

Google Calendar over MCP, tool by tool 

claude mcp add gbrain --transport http https://gbrain.io/mcp

The AI gets gcal_list_events, gcal_list_calendars and 7 more. Run /mcp in Claude Code and choose Authenticate, and GBrain asks what it may reach.

Connect Google Calendar once, use it everywhere

Their consent screen, one click, and one connection answers all of these. No key is pasted anywhere, and nothing runs before you allow it.

Sign in Every application