gcal MCP server

A private, self-hosted bridge between one Google Calendar account and the AI assistant its owner uses.

What it is

gcal is a Model Context Protocol (MCP) server. An AI assistant connects to it and, through it, works with the Google Calendar of the one account that authorised the server. It runs on the operator's own computers, for the operator alone: there is no sign-up, no multi-user service and nothing offered to the public. This page exists because Google asks every published OAuth application to have one.

What it does

On the account owner's instructions, given to the assistant in conversation, the server lists, creates, edits and deletes events and calendars, answers free/busy questions, and manages who a calendar is shared with. It does nothing on its own: every action is a request the owner made.

Why it asks for access to Google Calendar

The server requests the scope https://www.googleapis.com/auth/calendar, which is full read and write access to the authorising account's calendars and events. Read-only access would not let it add or change appointments, and the narrower events-only scope would not let it create or share calendars, both of which the owner uses. Access is granted once by the account owner on Google's consent screen and can be withdrawn at any time from the Google account's permissions page.

How the data is handled

The privacy policy describes what data the server touches, where it keeps the one credential it holds, and the fact that calendar data it reads is shown to the assistant in the owner's conversation. The short version: nothing is kept beyond the request that needed it, nothing is shared with anyone else, and nothing is used for any purpose but carrying out the owner's own requests.