All MCP Servers
Dev Tools & GitMCP RegistrynpmB · 79

Google Calendar MCP

io.github.A1-x-Tech · Updated

MCP server for the Google Calendar API: events, recurrence, invitations, availability, calendars.

At a glance

Google Calendar MCP is an MCP server in the Dev Tools & Git category. It runs locally over stdio via `npx -y @a1-x-tech/mcp-google-calendar`, and needs GOOGLE_CALENDAR_CLIENT_SECRET, GOOGLE_CALENDAR_REFRESH_TOKEN and GOOGLE_CALENDAR_ACCESS_TOKEN. It scores B (79/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 0GitHub stars

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install Google Calendar MCP in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install Google Calendar MCP in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add mcp-google-calendar -e 'GOOGLE_CALENDAR_CLIENT_SECRET=<GOOGLE_CALENDAR_CLIENT_SECRET>' -e 'GOOGLE_CALENDAR_REFRESH_TOKEN=<GOOGLE_CALENDAR_REFRESH_TOKEN>' -e 'GOOGLE_CALENDAR_ACCESS_TOKEN=<GOOGLE_CALENDAR_ACCESS_TOKEN>' -- npx -y @a1-x-tech/mcp-google-calendar
  2. Fill in your credentials

    Replace <GOOGLE_CALENDAR_CLIENT_SECRET>, <GOOGLE_CALENDAR_REFRESH_TOKEN>, <GOOGLE_CALENDAR_ACCESS_TOKEN> with your real values. Keep secrets out of any config file you commit.

  3. Verify it's connected

    bash
    claude mcp list
  4. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  5. Use it in a session

    Ask Claude to use the tools this server exposes. It discovers them automatically.

What does Google Calendar MCP need from you?

API key — Google OAuth2 client secret (refresh-token flow). Treat it as a secret.

  • GOOGLE_CALENDAR_CLIENT_IDoptionalEnvironment variable

    Google OAuth2 client id (refresh-token flow).

  • GOOGLE_CALENDAR_CLIENT_SECREToptionalsecretEnvironment variable

    Google OAuth2 client secret (refresh-token flow). Treat it as a secret.

  • GOOGLE_CALENDAR_REFRESH_TOKENoptionalsecretEnvironment variable

    Google OAuth2 refresh token, exchanged for access tokens automatically. Treat it as a secret.

  • GOOGLE_CALENDAR_ACCESS_TOKENoptionalsecretEnvironment variable

    Static OAuth2 access token (~1h lifetime) — alternative to the refresh-token trio, mostly for testing.

  • GOOGLE_CALENDAR_OAUTH_PORToptionalEnvironment variable

    Fixed port for the loopback listener of the in-chat login (127.0.0.1 + PKCE). Set it when the client runs over SSH port forwarding; otherwise a free port is picked per login.

  • GOOGLE_CALENDAR_API_BASEoptionalEnvironment variable

    API root override.

  • GOOGLE_CALENDAR_TIMEOUT_MSoptionalEnvironment variable

    Per-request timeout in milliseconds.

  • GOOGLE_CALENDAR_MAX_RETRIESoptionalEnvironment variable

    Retries on transient errors (429 always; 5xx/network for reads).

Pass secrets through your shell environment rather than committing them into a config file.

What tools does Google Calendar MCP expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

Read from the published package source — never executed. Parsed 11 of 11 source files.

This server can read and write files, make network requests and read your environment variables.

How it was published

  • No provenance attestation — there is nothing linking this published artifact to a specific source commit.
  • 1 npm maintainer — a single point of compromise · last published by gistrec.

Maintainer of this package and think something here is wrong? Tell us and we'll correct it.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
  • Downloads at launch — The package is fetched from its registry each run unless you pin a version.
  • Last commit 25 days ago — Actively maintained.
  • Repository created 2 months ago — Very new project with little track record yet.
  • 0 GitHub stars — Very little community usage so far.
  • 65 weekly downloads — Very few installs — you would be an early user.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 79

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%100%

    Last commit 25 days ago.

  • Adoption20%21%

    0 stars, 65 weekly downloads.

  • Transparency20%75%

    3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.

  • Provenance15%100%

    Package and registry entry point at the same repository.

  • Packaging15%100%

    Publishes a pinned version (1.0.0).

Documentation

Full README

Google Calendar MCP

English | Русский

A1 Google Calendar MCP lets an AI app manage Google Calendar in plain language. Review your week, schedule a meeting with guests and a Google Meet link, reschedule or cancel it, find a slot when everyone is free, and block Out of Office or Focus Time.

It uses the Google Calendar API with your Google account. It distinguishes a whole recurring series from a single occurrence and makes the limits of the Calendar API explicit instead of implying that every calendar task is possible.

  • 19 tools. Inspect calendars, events and free/busy, create and edit events, expand recurring series, and block Out of Office and Focus Time — plus six for connecting your Google account.
  • Sign in from the chat. No credentials file to hand-write: ask the assistant to connect, approve access in the browser, and the very next request works — no restart. The client secret travels as a file path, never through the conversation.
  • Nobody is emailed by accident. The Calendar API's default for invitations, changes and cancellations is silence; guests get email only when you ask for it via send_updates.
  • Writes are never replayed. After an ambiguous failure the server does not retry a write — a duplicated event could re-email every guest.
  • Minimal Google scopes. It uses calendar.events and calendar.readonly, without the broad calendar scope.

Start with a read-only question:

What's on my calendar this week? Point out any overlapping meetings.

Connect the server · Explore use cases · Open technical documentation


See it work in a minute

You: What does my Thursday look like, and when are Anna and I both free? Assistant: Shows Thursday's events and the free slots you share. Nothing changes. You: Book a 45-minute design review with Anna in the first shared slot, with a Google Meet link. Assistant: Shows the proposed time, guest list and Meet link, then asks for confirmation before creating the event. You: Confirm. Assistant: Creates the event. Nobody gets an email unless you ask it to send invitations.

Contents

  • Quick start
  • What you can ask it to do
  • How an event changes
  • What can change
  • Getting access
  • Configuration
  • Data, limits and background work
  • Technical documentation
  • Support

Quick start

Excerpt — the full document is on GitHub.

Maintain Google Calendar MCP? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![Google Calendar MCP on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-a1-x-tech-mcp-google-calendar)](https://mcp-skills-hub.vercel.app/mcps/io-github-a1-x-tech-mcp-google-calendar)

Catalog data refreshed . Something wrong? Report it.