# Google Calendar

> Read, create, and manage events across Google Calendar.

[Canonical HTML page](https://top-mcps.com/mcp/google-calendar) · [server.json](https://top-mcps.com/mcp/google-calendar.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

```json
{
  "mcpServers": {
    "google-calendar": {
      "command": "npx",
      "args": [
        "-y",
        "@gongrzhe/google-calendar-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "${GOOGLE_CLIENT_ID}",
        "GOOGLE_CLIENT_SECRET": "${GOOGLE_CLIENT_SECRET}"
      }
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
# export GOOGLE_CLIENT_ID=your_oauth_client_id
# export GOOGLE_CLIENT_SECRET=your_oauth_secret
claude mcp add google-calendar -- npx -y @gongrzhe/google-calendar-mcp
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

```json
{
  "mcpServers": {
    "google-calendar": {
      "command": "npx",
      "args": [
        "-y",
        "@gongrzhe/google-calendar-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "${GOOGLE_CLIENT_ID}",
        "GOOGLE_CLIENT_SECRET": "${GOOGLE_CLIENT_SECRET}"
      }
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

```jsonc
{
  "servers": {
    "google-calendar": {
      "command": "npx",
      "args": [
        "-y",
        "@gongrzhe/google-calendar-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "${GOOGLE_CLIENT_ID}",
        "GOOGLE_CLIENT_SECRET": "${GOOGLE_CLIENT_SECRET}"
      }
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "google-calendar": {
      "command": "npx",
      "args": [
        "-y",
        "@gongrzhe/google-calendar-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "${GOOGLE_CLIENT_ID}",
        "GOOGLE_CLIENT_SECRET": "${GOOGLE_CLIENT_SECRET}"
      }
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "google-calendar": {
      "command": "npx",
      "args": [
        "-y",
        "@gongrzhe/google-calendar-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "${GOOGLE_CLIENT_ID}",
        "GOOGLE_CLIENT_SECRET": "${GOOGLE_CLIENT_SECRET}"
      }
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@gongrzhe/google-calendar-mcp"
          ],
          "env": {
            "GOOGLE_CLIENT_ID": "${GOOGLE_CLIENT_ID}",
            "GOOGLE_CLIENT_SECRET": "${GOOGLE_CLIENT_SECRET}"
          }
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.google-calendar]
command = "npx"
args = [
  "-y",
  "@gongrzhe/google-calendar-mcp",
]
env = { GOOGLE_CLIENT_ID = "${GOOGLE_CLIENT_ID}", GOOGLE_CLIENT_SECRET = "${GOOGLE_CLIENT_SECRET}" }
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "google-calendar": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@gongrzhe/google-calendar-mcp"
        ]
      },
      "env": {
        "GOOGLE_CLIENT_ID": "${GOOGLE_CLIENT_ID}",
        "GOOGLE_CLIENT_SECRET": "${GOOGLE_CLIENT_SECRET}"
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Settings → Connectors → Developer mode`

Enable Developer mode (paid plans) and enter these values in the UI.

```json
{
  "name": "Google Calendar",
  "transport": "stdio",
  "command": "npx",
  "args": [
    "-y",
    "@gongrzhe/google-calendar-mcp"
  ],
  "env": {
    "GOOGLE_CLIENT_ID": "${GOOGLE_CLIENT_ID}",
    "GOOGLE_CLIENT_SECRET": "${GOOGLE_CLIENT_SECRET}"
  }
}
```

## At a glance

- **Maintainer:** Community (GongRzhe)
- **Transport:** stdio
- **Auth model:** OAuth 2.1
- **Required secrets:** GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET
- **Supported clients:** Claude, Cursor, Any MCP-compatible client, Google accounts
- **License:** MIT
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-04-19
- **Score:** 53/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/GongRzhe/Calendar-MCP-Server

## Security & scope

- **Access scope:** network
- **Sandbox:** OAuth 2.1 against the authenticated Google account; only calendars the user explicitly authorizes are accessible.
- **Gotchas:**
  - Time zones: the MCP uses the authenticated account time zone, not the prompt author's — be explicit about TZ if you operate across regions.
  - Recurrence rules on events are returned as RRULEs; the agent must parse these itself to reason about future instances.

## Quick answer

**What it does.** Exposes Google Calendar read/write over OAuth: list and search events, create and update meetings, query free-busy across calendars, manage attendees.

**Best for:**
- Scheduling assistants
- Find-a-slot flows
- Meeting-prep agents
- Calendar-aware briefings
- Automated reschedules

**Not for:**
- Bulk calendar exports
- Attendance analytics at scale

## Recipes

### Spot calendar conflicts on a given day

```
Show every event on my primary Google Calendar for next Tuesday in my local time zone. Flag any pairs that overlap, and suggest the first free 30-minute slot between 10:00 and 17:00.
```

_Tested with: Claude Desktop, Cursor_

## Description

The Google Calendar MCP connects AI agents to your calendar over OAuth 2.1. List events, schedule meetings, find free slots, and reschedule across multiple calendars — ideal for scheduling assistants and planning agents.

## Why it matters

Calendar is where time lives. An agent that can read and write it becomes a real scheduling assistant — finding slots, sending invites, rescheduling conflicts.

## Key features

- OAuth 2.1 with scoped calendars
- Free-busy queries
- Event CRUD with attendees
- Multiple-calendar support
- Respect for per-user ACLs

## FAQ

### How do I complete the OAuth flow?

First time you run the MCP it opens a browser window to google.com/auth. You approve the scopes you want the agent to have (read events, write events, etc.) and the refresh token is cached locally. Subsequent runs skip the browser.

### Which scopes does it request?

The minimum useful set is `calendar.readonly` plus `calendar.events` for writes. You can install with a narrower scope (read-only) first and add write later by re-running the auth flow.

### Can it manage multiple Google accounts?

One account per MCP server instance. If you need to manage work + personal, run two instances under different names in your MCP config — each with its own OAuth client and cached refresh token.

### Does it support Google Workspace calendars?

Yes. Workspace domain policies apply — if your admin restricts which apps can connect, your Google Cloud Console OAuth client must be approved on the Workspace side before the MCP can connect.

## Changelog

- **2026-04-19** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-02-25** — Initial directory listing.