Google Calendar MCP Server: calendar for Claude
Google Calendar MCP Server
A calendar MCP for Claude Desktop: the agent views, creates, updates and deletes Google Calendar events, recurring ones included
- 59 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent reads your schedule, creates, changes and deletes events and adds attendees
- The OAuth2 client secret must live in the client config, and sign-in opens access to the Google account's calendars
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/google-calendar-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent reads your schedule, creates, changes and deletes events and adds attendees
- The OAuth2 client secret must live in the client config, and sign-in opens access to the Google account's calendars
This is third-party code. Review the repository files before installing.
What it does
Google Calendar MCP Server links Claude Desktop with Google Calendar through OAuth 2.0. You ask the agent to do something with your calendar in plain words and the server calls the Google Calendar API. It is written in TypeScript and works over stdio. There are five tools. `getEvents` returns events with filters for calendar, time range, count and sort order. `createEvent` creates an event with title, description, location, start and end, attendees, a color (colorId 1 to 11) and recurrence rules in RFC 5545 format. `updateEvent` first reads the existing event and merges it with the new fields, so untouched values are kept. `deleteEvent` removes an event. `authenticate` signs in again and switches the Google account without restarting Claude. Sign-in uses PKCE, and tokens are kept in memory and encrypted with AES-256-GCM. After a restart you authorize again. When the local address is unreachable, for example on a remote server or in a container, manual code entry is enabled with `USE_MANUAL_AUTH=true`.
Who it is for. For Claude Desktop users who plan meetings and tasks in Google Calendar and want to manage the calendar through an agent.
Good fit when
- You want to know which meetings are planned for the week, sorted by start time
- You need a series of weekly meetings on Monday, Wednesday and Friday with attendees and a location
- You want to move an event without losing its description, location and attendee list: an update merges the fields
- You need to switch to another Google account in the conversation without restarting Claude
- You want to color events differently by type of activity
Not a fit when
- You need a Russian calendar: Yandex Calendar has its own servers, for example mcp_yandex_calendar
- You need read-only access: no read-only mode is described, and the tools can create and delete events
- You need persistent sign-in without re-authorizing after a restart: tokens live in memory only
- You have no Node.js 20 or no Google Cloud project with the Calendar API enabled
Example request
Show my meetings for next week and create a recurring Monday 10:00 event called StandupMCP
- Transport
- stdio
- Authentication
- OAuth
Environment variables
GOOGLE_CLIENT_IDrequired- OAuth2 client ID from the Google Cloud Console.
GOOGLE_CLIENT_SECRETrequired, secret- OAuth2 client secret from the Google Cloud Console.
GOOGLE_REDIRECT_URIrequired- Redirect address, http://localhost:4153/oauth2callback by default.
USE_MANUAL_AUTH- Set to true to enter the code manually when localhost is unreachable.
Limitations
It needs Node.js 20 or newer and a Google Cloud project with the Google Calendar API enabled and OAuth2 credentials (client ID and secret). Tokens are not written to disk, so you authorize again after every restart.
The server description names Claude Desktop as the main client and gives config examples only for it. The author does not discuss Google Calendar availability from Russia, and it was not checked for this card. Version 2.0.0 moved to MCP revision 2026-07-28 and added PKCE, so check your config when upgrading from early versions. The license is MIT.
How to disable. Delete the google-calendar block from claude_desktop_config.json and restart Claude Desktop. Revoke the app's access on your Google account page in the third-party apps section.
FAQ
Is there an MCP for Google Calendar in Claude Desktop?
Yes, Google Calendar MCP Server connects to Claude Desktop through npx from the @takumi0706/google-calendar-mcp package. It views, creates, updates and deletes events and works with your calendar after you sign in to a Google account.
How do I set up calendar MCP access to Google?
Create a Google Cloud project and enable the Google Calendar API. Then set up OAuth2 credentials and pass GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET and GOOGLE_REDIRECT_URI in the env block of the Claude Desktop config. The default redirect address is http://localhost:4153/oauth2callback.
Can the server create recurring events?
Yes. The `recurrence` parameter in `createEvent` and `updateEvent` accepts RFC 5545 rules, for example RRULE:FREQ=WEEKLY;BYDAY=MO,WE,FR for Monday, Wednesday and Friday meetings.
What if localhost is unreachable for sign-in?
Set `USE_MANUAL_AUTH=true`: after you grant access Google shows a code and you type it in by hand. This is needed on remote servers and in containers.
How does Google Calendar MCP Server store tokens?
Tokens live in memory only and are encrypted with AES-256-GCM; nothing is written to disk. The encryption key can be set with `TOKEN_ENCRYPTION_KEY` as 64 hexadecimal characters, otherwise it is generated automatically. You sign in again after a restart.
Discussion
No questions or reviews yet.
Related
MCP serversYandex Calendar MCP server
Яндекс Календарь MCP для Claude
An MCP server for Yandex Calendar: view, create and delete events using an app password
MCP server for the macOS calendar: an agent creates, finds and edits events in natural language
Google Docs MCP: Docs, Sheets, Drive, Gmail and Calendar
Google Docs MCP
An MCP server giving an agent Google Docs, Sheets, Drive, Gmail, Calendar and Apps Script: reading, editing, mail and events; sign-in over OAuth
GSuite MCP
mcp-gsuite
A Python MCP server for Gmail and Google Calendar: search and read emails, drafts and replies, events with attendees, several accounts at once
A simple Yandex Calendar MCP server
mcp_yandex_calendar
A small test Yandex Calendar MCP server over CalDAV: upcoming events, event creation and deletion with no confirmation step
Yandex Calendar MCP with a setup CLI
yandex-mcp workspace
A Yandex Calendar MCP server over CalDAV with a separate CLI for setup and app-password verification
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Google Calendar MCP Server: calendar for Claude (this entry) | no | OAuth | 59 | |
| A simple Yandex Calendar MCP server | no | API key | 0 | a server for Yandex Calendar, while this one works only with Google Calendar and OAuth2 sign-in |
| Yandex Calendar plugin for Codex | no | API key | 0 | a Yandex Calendar plugin for Codex, while this server targets Claude Desktop and Google's calendar |
README in short
The description lists capabilities: linking Claude Desktop with Google Calendar, MCP protocol implementation, OAuth2 sign-in, event management, colors and stdio transport. Then come the project's technologies, components, detailed parameters of the five tools, environment variables and a config example. The security section covers PKCE, state parameter validation, a fixed redirect address and HTML escaping. The version history details the move to 2.0.0. The repository has tests and publishing workflows.