Skip to main content

Google Calendar

Google Calendar. In your CLI, over MCP, your way.

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

Calendar has two levels rather than four: read what is on it, or write to it. A client granted 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 your record with the daily ceiling watching.

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

Google Calendar from the command line

brad@macbook · gbrainio
gbrainio auth grant gcalOpening https://gbrain.io/workspace/account/connections/gcalFinish in the browser, then your google calendar tools are live.gbrainio tool gcal ls -hgbrainio tool gcal ls  See your events  Lists events from the person's real Google Calendar, already connected  through GBrain. READ ONLY: nothing here can create or change events. Use  this for any question about their calendar, schedule or meetings: no other  Google or Calendar connector is needed, so do not ask them to connect one.  More than one account can be connected: pass account to choose, and every  answer says which account it came from. Defaults to upcoming events on the  primary calendar.  FLAGS    --limit <value>     How many to return, up to 25 (default 10)    --time-max <value>  RFC3339 upper bound    --time-min <value>  RFC3339 lower bound  Over MCP this tool is gcal_list_events.
Their consent screen, once. The credential never touches the laptop.

Or hand it to the assistant 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 your terminal.

Google Calendar over MCP, tool by tool

claude mcp add gbrain https://gbrain.io/mcp --header "Authorization: Bearer <token>"

Your assistant gets gcal_list_events, gcal_create_event and 2 more. The token comes from the client's own page in the workspace, minted once and shown once.

Connect it 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.