Google Calendar MCP Server
Manage Google Calendar events across multiple accounts and calendars from Claude and other assistants.
Sources and review
Checked against public documentation on . Suitability guidance is our editorial judgment; this is not a performance benchmark or an endorsement.
Scheduling across work and personal Google calendars through an assistant.
You can't create a Google Cloud project with the Calendar API and desktop OAuth credentials; setup requires both.
About Google Calendar MCP Server
This community MCP server integrates Google Calendar with AI assistants. It connects several Google accounts at once, lists events across calendars, detects conflicts between them, creates, updates, deletes and searches events including recurring ones, checks free/busy availability, and can add events from images, PDFs or web links.
Google Calendar MCP Server is listed in this index written primarily in TypeScript, with 1.2k stars on GitHub. Its latest recorded repository push was in October 2026; that is not an ASE editorial review date.
Before connecting: access and data
This record's specific permissions have not been reviewed by ASE. Read the publisher's documentation before copying setup or connecting.
- List the accounts, files and services the enabled tools can read, change or execute. Check your actual credentials and discovered tools.
- Use narrowly scoped credentials and read-only mode where supported. Review proposed writes before approving them; a generated configuration does not apply these limits for you.
- Local launch is not local-only data processing. External services receive requests, and your client may pass tool results to its model provider. Check both destinations before sharing private data.
- Keep keys and browser session files out of shared config, repositories and screenshots. Know how to disconnect the server and separately revoke its credentials or account sessions.
Add Google Calendar MCP Server to your MCP client
Generated from the launch command in the project's README. Your client starts the server on demand.
Claude Code
claude mcp add google-calendar-mcp -e GOOGLE_OAUTH_CREDENTIALS=/path/to/gcp-oauth.keys.json -- npx @cocal/google-calendar-mcpCursor
{
"mcpServers": {
"google-calendar-mcp": {
"command": "npx",
"args": ["@cocal/google-calendar-mcp"],
"env": {
"GOOGLE_OAUTH_CREDENTIALS": "/path/to/gcp-oauth.keys.json"
}
}
}
}VS Code
{
"servers": {
"google-calendar-mcp": {
"type": "stdio",
"command": "npx",
"args": ["@cocal/google-calendar-mcp"],
"env": {
"GOOGLE_OAUTH_CREDENTIALS": "/path/to/gcp-oauth.keys.json"
}
}
}
}Claude Desktop
{
"mcpServers": {
"google-calendar-mcp": {
"command": "npx",
"args": ["@cocal/google-calendar-mcp"],
"env": {
"GOOGLE_OAUTH_CREDENTIALS": "/path/to/gcp-oauth.keys.json"
}
}
}
}Codex
[mcp_servers.google-calendar-mcp]
command = "npx"
args = ["@cocal/google-calendar-mcp"]
env = { GOOGLE_OAUTH_CREDENTIALS = "/path/to/gcp-oauth.keys.json" }