Google Calendar MCP
English | Русский
Agenten stärken
Der eigene Befehl des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
npx -y @a1-x-tech/[email protected]Claude Code hat keinen Installationslink für einen lokalen Befehl. Kopieren Sie den Befehl unten und führen Sie ihn in einem Terminal aus.
GOOGLE_CALENDAR_CLIENT_ID=<value> GOOGLE_CALENDAR_CLIENT_SECRET=<secret> GOOGLE_CALENDAR_REFRESH_TOKEN=<secret> GOOGLE_CALENDAR_ACCESS_TOKEN=<secret> GOOGLE_CALENDAR_OAUTH_PORT=<value> GOOGLE_CALENDAR_API_BASE=<value> GOOGLE_CALENDAR_TIMEOUT_MS=<value> GOOGLE_CALENDAR_MAX_RETRIES=<value> claude mcp add io.github.a1-x-tech-mcp-google-calendar -- npx -y @a1-x-tech/mcp-google-calendar@1.1.2In einem Terminal ausführen.
{ "mcpServers": { "io.github.a1-x-tech-mcp-google-calendar": { "command": "npx", "args": [ "-y", "@a1-x-tech/[email protected]" ], "env": { "GOOGLE_CALENDAR_CLIENT_ID": "<value>", "GOOGLE_CALENDAR_CLIENT_SECRET": "<secret>", "GOOGLE_CALENDAR_REFRESH_TOKEN": "<secret>", "GOOGLE_CALENDAR_ACCESS_TOKEN": "<secret>", "GOOGLE_CALENDAR_OAUTH_PORT": "<value>", "GOOGLE_CALENDAR_API_BASE": "<value>", "GOOGLE_CALENDAR_TIMEOUT_MS": "<value>", "GOOGLE_CALENDAR_MAX_RETRIES": "<value>" } } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
English | Русский
MCP server for the Google Calendar API: events, recurrence, invitations, availability, calendars.
A1 Google Calendar MCP lets an AI app manage Google Calendar in plain language. Review your week, schedule a meeting with guests and a Google Meet link, reschedule or cancel it, find a slot when everyone is free, and block Out of Office or Focus Time.
It uses the Google Calendar API with your Google account. It distinguishes a whole recurring series from a single occurrence and makes the limits of the Calendar API explicit instead of implying that every calendar task is possible.
send_updates.calendar.events and calendar.readonly, without the broad calendar scope.Start with a read-only question:
What's on my calendar this week? Point out any overlapping meetings.
You: What does my Thursday look like, and when are Anna and I both free?
Assistant: Shows Thursday's events and the free slots you share. Nothing changes.
You: Book a 45-minute design review with Anna in the first shared slot, with a Google Meet link.
Assistant: Shows the proposed time, guest list and Meet link, then asks for confirmation before creating the event.
You: Confirm.
Assistant: Creates the event. Nobody gets an email unless you ask it to send invitations.
You need Node.js 20+, a Google account and OAuth credentials from a Google Cloud project with the Google Calendar API enabled.
In the app: open Settings → MCP servers, select Add server, choose STDIO, enter the command npx -y @a1-x-tech/mcp-google-calendar@latest and environment variables GOOGLE_CALENDAR_CLIENT_ID, GOOGLE_CALENDAR_CLIENT_SECRET, GOOGLE_CALENDAR_REFRESH_TOKEN, then select Save and Restart.
From the command line:
codex mcp add google-calendar \
--env GOOGLE_CALENDAR_CLIENT_ID=your_client_id \
--env GOOGLE_CALENDAR_CLIENT_SECRET=your_client_secret \
--env GOOGLE_CALENDAR_REFRESH_TOKEN=your_refresh_token \
-- npx -y @a1-x-tech/mcp-google-calendar@latest
codex mcp list
claude mcp add \
--env GOOGLE_CALENDAR_CLIENT_ID=your_client_id \
--env GOOGLE_CALENDAR_CLIENT_SECRET=your_client_secret \
--env GOOGLE_CALENDAR_REFRESH_TOKEN=your_refresh_token \
--transport stdio --scope user google-calendar \
-- npx -y @a1-x-tech/mcp-google-calendar@latest
claude mcp list
The current official path is Settings → Extensions. For a custom desktop extension, open Advanced settings → Extension Developer → Install Extension…, select a .mcpb file and follow the prompts.
This repository currently publishes an npm stdio package and does not contain a .mcpb bundle. For Claude Desktop builds that still support local configuration, use the following JSON stdio configuration as a fallback:
{
"mcpServers": {
"google-calendar": {
"command": "npx",
"args": ["-y", "@a1-x-tech/mcp-google-calendar@latest"],
"env": {
"GOOGLE_CALENDAR_CLIENT_ID": "your_client_id",
"GOOGLE_CALENDAR_CLIENT_SECRET": "your_client_secret",
"GOOGLE_CALENDAR_REFRESH_TOKEN": "your_refresh_token"
}
}
}
}
In those builds, save it to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows.
Add this to ~/.cursor/mcp.json on macOS/Linux or %USERPROFILE%\.cursor\mcp.json on Windows:
{
"mcpServers": {
"google-calendar": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@a1-x-tech/mcp-google-calendar@latest"],
"env": {
"GOOGLE_CALENDAR_CLIENT_ID": "your_client_id",
"GOOGLE_CALENDAR_CLIENT_SECRET": "your_client_secret",
"GOOGLE_CALENDAR_REFRESH_TOKEN": "your_refresh_token"
}
}
}
}
Run MCP: Open User Configuration and add:
{
"servers": {
"google-calendar": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@a1-x-tech/mcp-google-calendar@latest"],
"env": {
"GOOGLE_CALENDAR_CLIENT_ID": "${input:calendar_client_id}",
"GOOGLE_CALENDAR_CLIENT_SECRET": "${input:calendar_client_secret}",
"GOOGLE_CALENDAR_REFRESH_TOKEN": "${input:calendar_refresh_token}"
}
}
},
"inputs": [
{ "type": "promptString", "id": "calendar_client_id", "description": "Google OAuth client ID" },
{ "type": "promptString", "id": "calendar_client_secret", "description": "Google OAuth client secret", "password": true },
{ "type": "promptString", "id": "calendar_refresh_token", "description": "Google OAuth refresh token", "password": true }
]
}
Check it with MCP: List Servers.
calendar_id: "primary" is your main calendar; other calendars come from list_calendars, and writes need writer access.list_event_instances) exactly one.update_event changes only the fields you provide, but a nested object replaces its predecessor wholesale — a new attendees list replaces the whole guest list.send_updates says so — the Calendar API's default is silence.Out of Office and Focus Time blocks exist only on the primary calendar of a Google Workspace account; consumer Gmail and secondary calendars reject them. Creating an event does not check for conflicts — ask for a free/busy check first. All-day events end on an exclusive date: an event through Friday ends on Saturday's date.
The AI client controls confirmation prompts. The server marks reads, writes and destructive tools so the client can distinguish an inspection from a live change.
Access to your own calendars requires OAuth 2.0; an API key is not enough. There are two ways to connect, and the first one needs no configuration file at all.
Start the server with no credentials and ask the assistant to connect. It walks you through it with six built-in tools:
The login takes effect immediately: the next tool call works without restarting the AI client. The token is stored in ~/.config/mcp-google-calendar/credentials.json (on Windows, under %APPDATA%), readable only by your account, and never leaves your machine.
The classic path, and the one to use for CI and headless installs:
Create or select a Google Cloud project and enable Google Calendar API.
Configure the OAuth consent screen and create a Desktop app OAuth client.
Authorize the Google account whose calendars you want to manage. The OAuth 2.0 Playground can obtain the refresh token when Use your own OAuth credentials is enabled.
Request both scopes:
https://www.googleapis.com/auth/calendar.events
https://www.googleapis.com/auth/calendar.readonly
The broad https://www.googleapis.com/auth/calendar scope is needed only for raw_request calls that manage calendars or sharing rules themselves.
Environment variables always win over a login taken in the chat, so an existing configured install keeps behaving exactly as before.
Testing-mode OAuth refresh tokens can expire after seven days. Publish the OAuth app, or use an Internal app in a Workspace domain, when you need long-lived access. Treat the client secret and refresh token as passwords.
* Provide either the OAuth trio or an access token. Without credentials the server still starts and completes the MCP handshake; the first tool call then names the exact variables to set.
ASKADS_TELEMETRY=0 to opt out.429, the server retries with backoff; reads also retry after network and 5xx errors, while writes are not replayed after an uncertain failure — a duplicated event could re-email every guest.list_events supports incremental checks via updated_min; if your AI app supports scheduled tasks, it can check your calendar periodically.Found a bug or need a scenario? Create an issue or write in Telegram.
MCP server for the Google Calendar API: events, recurrence, invitations, availability, calendars.
{ "mcpServers": { "io.github.a1-x-tech-mcp-google-calendar": { "command": "npx", "args": [ "-y", "@a1-x-tech/[email protected]" ], "env": { "GOOGLE_CALENDAR_CLIENT_ID": "<value>", "GOOGLE_CALENDAR_CLIENT_SECRET": "<secret>", "GOOGLE_CALENDAR_REFRESH_TOKEN": "<secret>", "GOOGLE_CALENDAR_ACCESS_TOKEN": "<secret>", "GOOGLE_CALENDAR_OAUTH_PORT": "<value>", "GOOGLE_CALENDAR_API_BASE": "<value>", "GOOGLE_CALENDAR_TIMEOUT_MS": "<value>", "GOOGLE_CALENDAR_MAX_RETRIES": "<value>" } } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Der Herausgeber nennt diese Umgebungsvariablen: GOOGLE_CALENDAR_CLIENT_ID, GOOGLE_CALENDAR_CLIENT_SECRET, GOOGLE_CALENDAR_REFRESH_TOKEN, GOOGLE_CALENDAR_ACCESS_TOKEN, GOOGLE_CALENDAR_OAUTH_PORT, GOOGLE_CALENDAR_API_BASE, GOOGLE_CALENDAR_TIMEOUT_MS, GOOGLE_CALENDAR_MAX_RETRIES.
Google Calendar MCP läuft lokal über stdio.
Zuletzt geprüft: 2026-11-11. MCP server for the Google Calendar API: events, recurrence, invitations, availability, calendars.