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.

Google Calendar

Name: Google Calendar
Availability: InStock
Author: Community (GongRzhe)

Read, create, and manage events across Google Calendar.

Score 53(?)Community (GongRzhe)MITVerified Apr 19, 2026Top MCPs for Scheduling & Calendar →

Install View on GitHub

Install Google Calendar

— pick your client, copy, paste.

claude_desktop_config.jsonjson

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

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

CLI or .mcp.jsonshell

# 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

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

.cursor/mcp.jsonjson

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

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

.vscode/mcp.jsonjsonc

{
  "servers": {
    "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 uses the "servers" key (not "mcpServers").

~/.codeium/windsurf/mcp_config.jsonjson

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

Open via Cascade → hammer icon → Configure.

cline_mcp_settings.jsonjson

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

Open via the Cline sidebar → MCP Servers → Edit.

~/.continue/config.jsonjson

{
  "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}"
          }
        }
      }
    ]
  }
}

Continue uses modelContextProtocolServers with a transport block.

~/.codex/config.tomlshell

# ~/.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}" }

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

~/.config/zed/settings.jsonjsonc

{
  "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}"
      }
    }
  }
}

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

ChatGPT → Settings → Connectors → Developer modejson

{
  "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}"
  }
}

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

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

Not for

Bulk calendar exports
Attendance analytics at scale

Setup recipe

1
Install
Copy the install snippet for your client from the Install section above.
2
Set required secrets
Set GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET in your shell environment before launching your MCP client.
3
Try a minimum working prompt
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.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

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.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.

Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.

Recommend the best MCP servers for [task: e.g. scheduling & calendar work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-scheduling-calendar

Compare Google Calendar against a real alternative. Swap the second MCP in [brackets] if you want a different match.

Compare Google Calendar MCP vs [Linear MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/google-calendar
- top-mcps.com listing for Linear

Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.

Install the Google Calendar MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/google-calendar (fetch https://top-mcps.com/mcp/google-calendar.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

Apr 19, 2026
Refreshed install snippets and fact sheet; verified for 2026.
Feb 25, 2025
Initial directory listing.

Exploring Top MCPs for Scheduling & Calendar? See all Scheduling & Calendar MCPs →