English Français العربية

Google Calendar

Official registry Productivity

Allow AI systems to list, create, update, and manage Google Calendar events.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package google-cal-mcp
Claude Code 
claude mcp add google-calendar -e 'GOOGLE_ACCESS_TOKEN=<your google_access_token>' -- npx -y google-cal-mcp@1.1.3
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "google-calendar": {
            "command": "npx",
            "args": [
                "-y",
                "google-cal-mcp@1.1.3"
            ],
            "env": {
                "GOOGLE_ACCESS_TOKEN": "<your google_access_token>"
            }
        }
    }
}

Environment variables

  • GOOGLE_ACCESS_TOKEN required secret Google OAuth access token with Calendar scopes.
NPM package google-cal-mcp
Claude Code 
claude mcp add google-calendar -e 'MCP_TRANSPORT=<MCP_TRANSPORT>' -e 'GOOGLE_CLIENT_ID=<GOOGLE_CLIENT_ID>' -e 'GOOGLE_CLIENT_SECRET=<your google_client_secret>' -- npx -y google-cal-mcp@1.1.3
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "google-calendar": {
            "command": "npx",
            "args": [
                "-y",
                "google-cal-mcp@1.1.3"
            ],
            "env": {
                "MCP_TRANSPORT": "<MCP_TRANSPORT>",
                "GOOGLE_CLIENT_ID": "<GOOGLE_CLIENT_ID>",
                "GOOGLE_CLIENT_SECRET": "<your google_client_secret>"
            }
        }
    }
}

Environment variables

  • MCP_TRANSPORT required Transport type.
  • GOOGLE_CLIENT_ID required Google OAuth client ID.
  • GOOGLE_CLIENT_SECRET required secret Google OAuth client secret.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. google-cal-mcp
  2. Use Cases
  3. Setup
  4. Architecture
  5. Tools
  6. Calendar API Scopes
  7. Contributing
  8. Releases

google-cal-mcp

MCP server for Google Calendar - list, create, update, and manage calendar events.

Use Cases

Schedule meetings: "Set up a 30-min sync with Sarah next week" → finds a free slot, creates the event with a Meet link, and sends the invite.

RSVP to invites: "Accept the team offsite but decline the vendor demo" → responds to pending invitations automatically.

Find availability: "When am I free this Thursday afternoon?" → queries your calendar and returns open slots.

Reschedule events: "Move my 1:1 with Alex to Friday at 2pm" → updates the event and notifies attendees.

Daily briefing: "What's on my calendar today?" → lists all events with times, locations, and attendees.

Block focus time: "Block 2 hours tomorrow morning for deep work" → creates a calendar event to protect your time.

(These are just examples - any workflow that needs calendar access can use this.)

Setup

1. Create Google OAuth credentials
  1. Go to Google Cloud Console
  2. Create a new project (or use existing)
  3. Enable the Google Calendar API
  4. Go to APIs & Services → OAuth consent screen, set up consent screen
  5. Go to APIs & Services → Credentials → Create Credentials → OAuth client ID
  6. Choose Web application
  7. Add http://localhost:3000/callback to Authorized redirect URIs
  8. Note your Client ID and Client Secret
2. Run the server
GOOGLE_CLIENT_ID='your-client-id' \
GOOGLE_CLIENT_SECRET='your-client-secret' \
MCP_TRANSPORT=http \
npm start

The server runs on http://localhost:3000 by default. Change with PORT=3001.

3. Add to your MCP client

With the server running, follow the instructions on install-mcp, which generates the right config for your MCP client (Claude Code, Claude Desktop, Cursor, Cline, VS Code, and more).

Architecture

This server acts as an OAuth proxy to Google:

graph LR
    A[MCP client] <--> B[google-cal-mcp] <--> C[Google OAuth/API]
  1. Server advertises itself as an OAuth authorization server via /.well-known/oauth-authorization-server
  2. /register returns the Google OAuth client credentials
  3. /authorize redirects to Google, encoding the client's callback URL in state
  4. /callback receives the code from Google and forwards to the client's callback
  5. /token proxies token requests to Google, injecting client credentials
  6. /mcp handles MCP requests, using the bearer token to call Calendar API

The server holds no tokens or state - it just proxies OAuth to Google.

Tools

ToolDescription
Calendars
calendars_listList all calendars the user has access to
calendarlist_insertSubscribe to a shared calendar
calendarlist_updateUpdate calendar settings (color, visibility, reminders)
calendarlist_deleteUnsubscribe from a calendar
Events
events_listList events in a time range with search/filter
event_getGet details of a specific event
event_createCreate a new event with attendees and Meet link
event_updateUpdate an existing event
event_deleteDelete an event
event_respondRSVP to an invitation (accept/decline/tentative)
event_moveMove event to a different calendar
event_instancesGet instances of a recurring event
Availability
freebusy_queryFind free/busy times for scheduling
Sharing
acl_listList who has access to a calendar
Colors
colors_getGet available color palette for calendars/events

Calendar API Scopes

  • calendar - Full access to calendars
  • calendar.events - Read/write events

Contributing

Pull requests are welcomed on GitHub! To get started:

  1. Install Git and Node.js
  2. Clone the repository
  3. Install dependencies with npm install
  4. Run npm run test to run tests
  5. Build with npm run build

Releases

Versions follow the semantic versioning spec.

To release:

  1. Use npm version <major | minor | patch> to bump the version
  2. Run git push --follow-tags to push with tags
  3. Wait for GitHub Actions to publish to the NPM registry.

Frequently asked questions

What is Google Calendar?

Allow AI systems to list, create, update, and manage Google Calendar events.

How do I install Google Calendar?

It runs on your machine. In Claude Code: claude mcp add google-calendar -e 'GOOGLE_ACCESS_TOKEN=<your google_access_token>' -- npx -y google-cal-mcp@1.1.3. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Google Calendar need an API key?

Yes. It expects GOOGLE_ACCESS_TOKEN, MCP_TRANSPORT, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, which you set in its configuration.

Is Google Calendar open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Google Calendar?

It is published by domdomegg. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.