CalendarMCP

The hosted Google Calendar MCP server. Connect any AI agent to your Google Calendar in about two minutes. No self-hosting, no Docker, no credentials.json.

What this is

CalendarMCP is a hosted Model Context Protocol (MCP) server for Google Calendar. Connect your Google account once, get an API key, and any MCP-compatible client (Claude Desktop, Claude Code, Claude.ai, Cursor, OpenClaw, Continue, Cline, Windsurf, Goose, Zed, ChatGPT custom GPTs, n8n, etc.) can read and write your calendar.

This repo is the public docs, manifest, and client examples for the service. The hosted service is not open source. If you want a self-hosted alternative, the most popular OSS option is nspady/google-calendar-mcp and we recommend it for users who want OAuth tokens to never leave their machine.

What CalendarMCP gives you that self-hosted MCPs do not

• Zero setup. One Google OAuth click. No credentials.json, no Google Cloud Console, no Docker.
• HTTP transport. Works with Claude.ai, Claude Code, Cursor, and any hosted MCP client. Self-hosted stdio MCPs only work with Claude Desktop.
• Batch operations. batch_update_events updates up to 50 events in one concurrent call. Renaming a recurring meeting across a year is one prompt, not 50 clicks.
• Multi-account, one key. Connect any number of Google accounts (mix OAuth and service-account-shared calendars) under a single API key. Reading fans out across all of them, results merged and sorted.
• Google Advanced Protection support. The only hosted MCP that works for GAP users (via service-account sharing. OAuth is blocked for those accounts).
• Per-calendar Read/Write matrix. Tighten what each agent can touch from the dashboard without minting new keys.

Quick start

1. Visit calendarmcp.ai, sign in with Google, and copy your API key.
2. Add the MCP server to your client of choice. Configs below.
3. Talk to your agent: "What do I have on Tuesday?"

Client configs

Drop these into the right config file for your MCP client.

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "calendar": {
      "command": "npx",
      "args": [
        "@modelcontextprotocol/server-fetch",
        "https://calendarmcp.ai/api/mcp"
      ],
      "env": {
        "MCP_AUTH_HEADER": "Authorization: Bearer YOUR_CALENDARMCP_API_KEY"
      }
    }
  }
}

See examples/claude-desktop.json and our Claude Desktop integration guide.

Claude Code

claude mcp add calendar https://calendarmcp.ai/api/mcp \
  --transport http \
  --header "Authorization: Bearer YOUR_CALENDARMCP_API_KEY"

See examples/claude-code.sh and our Claude Code integration guide.

Cursor

~/.cursor/mcp.json:

{
  "mcpServers": {
    "calendar": {
      "url": "https://calendarmcp.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_CALENDARMCP_API_KEY"
      }
    }
  }
}

See examples/cursor.json and our Cursor integration guide.

OpenClaw

In your openclaw.json:

{
  "plugins": {
    "entries": {
      "mcp-calendarmcp": {
        "enabled": true,
        "config": {
          "url": "https://calendarmcp.ai/api/mcp",
          "authHeader": "Bearer YOUR_CALENDARMCP_API_KEY"
        }
      }
    }
 

... [View full README on GitHub](https://github.com/full-vibe/calendarmcp-public#readme)