Google Calendar MCP Server

Google Calendar MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Enables interaction with Google Calendar through Claude Desktop using the Model Context Protocol.

What the assistant can call

Once Google Calendar is connected, these are the calls the assistant has available:

• create_event — Create new calendar events
• list_events — View upcoming calendar events
• Resources — The Resources tool exposed by this server
• Tools — The Tools tool exposed by this server
• Prompts — The Prompts tool exposed by this server
• Debugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

• Node.js (v14 or higher) - A Google Cloud Project with Calendar API enabled - OAuth 2.0 Client credentials

Choosing this one

Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Google Calendar's toolset — create_event, list_events, Resources and 3 more — is a fair guide to whether it matches your workflow. It is maintained by thisnick; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the google calendar mcp server does with a few real requests.