MCP servers · cloudcorprecords

calendarport: Google Calendar MCP tools

MCP server providing ten tools for listing, creating, updating, deleting and checking Google Calendar calendars and events.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

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.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
cloudflare

Cloudflare MCP servers

Cloudflare's hosted MCP servers for its products: documentation search, sandbox containers, browser rendering, Radar internet data, logs and analytics, Workers and more.

4.5K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
microsoft

Playwright MCP (browser automation)

Microsoft's MCP server that lets an AI assistant open web pages, click, type and read them through a real browser, using the page structure instead of screenshots.

39.6K GitHub starsTesting & QAWeb, search & browser
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026