What it does
calendarport exposes Google Calendar calendars and events as MCP tools, calling the Google Calendar API. It is a clean-room rebuild of the core surface of the Google Calendar reference MCP server, written from the public Calendar API documentation. The core subset has ten tools: list_calendars, get_calendar, create_calendar, list_events, get_event, create_event, update_event, delete_event, quick_add_event and check_free_busy.
It suits anyone who wants an MCP client to read or change Google Calendar calendars and events, or to check free and busy times. On event tools, calendar_id is optional and defaults to primary.
Running it requires a Google OAuth access token set as an environment variable. The API base URL can optionally be overridden with CALENDAR_API_URL, which defaults to the Google Calendar v3 endpoint. Without the token, every tool call fails with an error naming the missing variable. The publisher documents a CLI where each tool is a subcommand taking one JSON object, MCP client configuration, and Docker use. The project is released under the MIT licence.
Limitations and requirements
A Google OAuth access token is required; without it every tool call fails. Calendar ACL and rules, event move, import, instances and watch, attachments, conference data, settings and colors are not part of this tool subset.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/calendarport
Google Calendar calendars, events and free-busy checks, as MCP tools.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it