Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Google Calendar MCP

by mmedumversion 5.1.1i★ 0iRuns on your computerRepository ↗
Registry nameio.github.mmedum/google-calendar-mcp

How to install

What it does

Google Calendar over MCP: calendars, events, recurrence and availability.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Docs, sheets & office work

Use together with

Skills that teach the AI this kind of work; they work alongside this one

MinerU

Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.

by opendatalab★ 83,9191 skills

Skill · How-to guideNo license stated

watermarks-remover

A privacy-first app that strips AI watermarks from content you own.

by guillaumemeyer★ 27,7231 skills

Skill · How-to guide

obsidian-skills

Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.

by kepano★ 53,104 (whole repo)5 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score12/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Passed 3/3 checks · Runs on your computer

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone

  1. Download the maker’s installer

    Download the maker’s .mcpb file

    The .mcpb file comes straight from the maker; we do not change it

  2. Double-click the file, then click Install in the Claude desktop app

  3. Try it

    Use Google Calendar MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Google Calendar MCP or shows a Google Calendar MCP tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Google Calendar MCP yet

Google Calendar MCP runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Google Calendar MCP

  • No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone

B · Others in Docs, sheets & office work that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Claude Code cannot connect Google Calendar MCP yet

The maker only provides an installer for the Claude desktop app

What you can do instead

A · Use an app that can connect Google Calendar MCP

  • No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone

Cursor cannot connect Google Calendar MCP yet

The maker only provides an installer for the Claude desktop app

What you can do instead

A · Use an app that can connect Google Calendar MCP

  • No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone

VS Code cannot connect Google Calendar MCP yet

The maker only provides an installer for the Claude desktop app

What you can do instead

A · Use an app that can connect Google Calendar MCP

  • No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Google Calendar MCP💬 Discussion →

At a glance

Downloads per weeki
Not on npm/PyPI
Licencei
Apache-2.0
Connection
Runs on your computer
Latest versioni
5.1.1
Published to registryi
Nov 3, 2026
Code last changedi
Nov 19, 2026
Maker
mmedum
Packages
mcpb: …/google-calendar-mcp_5.1.1.mcpb
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account mmedum, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed today

  • ✓ Pass

    Has a licence

    Uses Apache-2.0

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

Not checked: only npm and PyPI packages with a version can be checked

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/mmedum-google-calendar-mcp.svg)](https://mcp.popnx.com/en/servers/mmedum-google-calendar-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Docs, sheets & office worki

  • More stars than 0% of the other 4110 servers in this category
  • Published to the registry more recently than 68% of the other 4110 servers in this category
  • Basic checks equal to or better than 99% of the other 4110 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Google Calendar MCP safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed today, and the latest version (5.1.1) reached the registry 16 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.

What can I use instead?

In the same category: Puter MCP, XcodeBuildMCP, Vexa, Atlassian Rovo MCP Server, Anki MCP Server

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Puter MCP

Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more

by HeyPuterWidely used★ 44.2KUpdated 5 months ago

Runs in the cloud✓ service owner · puter.com

XcodeBuildMCP

XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.

by getsentryWidely used↓ 130.5K/wk shared package★ 6.6KUpdated 4 months ago

Runs on your computer✓ service owner · xcodebuildmcp.com

Vexa

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

by Vexa-aiWidely used★ 3KUpdated 2 months ago

Runs in the cloud✓ service owner · vexa.ai

Atlassian Rovo MCP Server

Atlassian’s official server lets AI search and manage Jira work and Confluence pages. Connects to Atlassian’s cloud with OAuth sign-in.

by atlassianGrowing★ 1.2KUpdated 2 months ago

Runs in the cloud✓ service owner · atlassian.com

Anki MCP Server

MCP server for Anki flashcards: adaptive review, notes, media, and deck management via AnkiConnect.

by ankimcpGrowing↓ 1.1K/wk★ 567Updated last month

Runs on your computer✓ service owner · ankimcp.ai
Compared with similar ones
This one
Google Calendar MCP
Puter MCPXcodeBuildMCPVexaAtlassian Rovo MCP ServerAnki MCP Server
Runs whereInstalls on your computerRuns in the cloud, nothing to installInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installInstalls on your computer
Needs a keyNoNoNoYesNoNo
Add with + in ClaudeNoNoNoNoYesNo
Basic checks3/34/43/32/44/43/3
LicenseApache-2.0AGPL-3.0MITApache-2.0Apache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

google-calendar-mcp

An MCP server for Google Calendar. One binary, stdio, per-user OAuth against your own Google account.

It answers when — calendars, the events on them, and who is free. What a meeting produces (a recording, a notes document, an attachment) belongs to servers built on the Meet, Docs and Drive APIs. get_event names the files attached to an event, with the Drive file id those servers take.

It is for one person who uses Google Calendar, on a Workspace or a personal Google account, and wants an assistant to read and change that calendar as them. You create your own OAuth client in Google Cloud once, and nothing is hosted.

Goals and non-goals

Goals:

  • Correct about time. An all-day event stays a date, every timed write carries an IANA zone, and every read states its window and zone.
  • Nobody emailed by surprise. notify is required on any write that can reach a guest, and scope on any write to a repeating event, with no default for either.
  • A write never overwrites what it did not see. Every change is a patch under the etag of the read that planned it.
  • Safe by default. What cannot be taken back, and every share beyond your organization, is registered only when you turn it on. Read-only mode removes every write, and the writes take dry_run.
  • Act as you, and log nothing about your calendar. Every call runs as the signed-in account, and the logs never carry event content or addresses.

Non-goals:

  • What a meeting produces. Recordings, notes documents and the files attached to an event belong to the Drive and Docs servers. Google Tasks is a separate API.
  • Push notifications. Google's watch methods need a public HTTPS endpoint, which a stdio server cannot offer. list_changes hands back a sync token instead.
  • A local cache or sync loop. The server keeps no copy of your calendar between calls.
  • Migration and administration. Importing events from another system and transferring a calendar's ownership as an administrator are out.
  • Parsing natural language into events. Google's quick-add hides which fields it set and in which zone it read the time; the model calling this server parses better.
  • A hosted service. It speaks stdio only, so Claude on the web and on mobile cannot reach it.
  • Asking you before a call. Your client approves each call; the server asks nothing.

What makes this one different

Calendar tooling often gets these wrong. This server is built around getting them right, and a test enforces each:

  • An all-day event is a date, not a time. It never becomes an instant, so it cannot land on the wrong day for anyone west of UTC. Every timed event carries a real IANA zone, not just an offset, because an offset cannot expand a repeating event across a daylight-saving change.
  • Every read says what it read. The absolute window, the time zone, where that zone came from, and whether the list was truncated. A schedule that does not say which Thursday it is showing can be read as any Thursday.
  • Availability is not a list of events. An event you cannot see the details of still makes someone busy, and an event marked "free" does not. A calendar that could not be read is reported as *unknown*, never folded into "free".

The design and the decisions behind it are in docs/architecture.md.

Install

go install github.com/mmedum/google-calendar-mcp/v5/cmd/google-calendar-mcp@latest

Or take a signed archive from the latest release. docs/release.md gives the commands that verify it.

Set up

You need your own Google Cloud project and OAuth client. Nothing deployer-specific is baked into this repository.

  1. Create a project and enable the Google Calendar API.
  2. Configure the OAuth consent screen and, on an External app, add the scopes docs/gcp-setup.md lists; an Internal app needs no list. A gate checks that file against the code, so it cannot fall behind what login asks for.
  3. Create an OAuth client of type Desktop app and download the JSON.
  4. Sign in:
google-calendar-mcp login --client-secret ~/path/to/client_secret.json

google-calendar-mcp doctor

doctor checks the client JSON, the stored token, the granted scopes and whether the API answers, and names what is missing.

Signing in over SSH

The OAuth callback reaches the loopback interface of the machine running login, while your browser is on your own machine. Forward the port first. Use --no-browser: it prints the authorization URL and the exact ssh -L line to run, with the port it actually picked.

Configure your MCP client

{

"mcpServers": { "google-calendar": { "command": "google-calendar-mcp", "env": { "GCAL_CLIENT_SECRET": "/path/to/client_secret.json" } } } }

Every setting is in docs/configuration.md.

Claude Desktop

Every release also carries a .mcpb bundle. Open it and Claude Desktop installs the server and asks for the settings a client's configuration would carry: your OAuth client JSON, which may be left empty to use the one login recorded, the profile, read-only and the switches. Deleting a calendar or every event on one, publishing it and sharing it outside your organization (enable_destructive), and an event that declines every meeting it overlaps (enable_decline_all) stay off unless you turn them on. Sharing inside your organization (sharing) stays on, as on a server you configure by hand, and read-only leaves every switch nothing to register. This server asks nobody before a call. Claude Desktop approves each tool, with Allow once or Always allow, and a tool you always allow then runs unasked, so leave a switch off unless you need its tools.

The bundle covers macOS, Windows and Linux on both architectures: macOS through a universal binary, Windows through amd64, and Linux through a small launcher that picks the binary at start. It does not log you in. Install the binary as well, run google-calendar-mcp login once, and the bundle uses the same login.

Tools

ToolWhat it does
list_calendarsEvery calendar this account can see, with ids, time zones and your access level. Start here.
get_calendarOne calendar in full, including who it is shared with and its default reminders.
list_eventsThe events on one or more calendars in a window, or only the kinds you name, such as out of office, or the event an invitation email is about.
search_eventsFree-text search across a window, over titles, descriptions, locations and guests.
get_eventOne event, with its guests and their responses, what guests may do, your reminders, and the files attached to it.
list_instancesThe occurrences of one repeating event, with the dates that were moved or removed.
list_changesWhat changed since you last looked, including deletions — which a list cannot report, because a deleted event simply stops matching. Hands back a sync token to pass in next time, or reads what changed since a moment you name.
check_availabilityWhen people are busy and when they are free, from Google's free/busy service rather than from a list of events. Takes an optional working-hours mask.
get_settingsThe account's time zone, week start and color palette.
create_eventCreate an event, one-off or repeating, with guests, optional guests, rooms, your reminders, its visibility, what guests may do, and a Google Meet link if you ask for one. Or a status event on your primary calendar: out of office, focus time or a working location.
create_event_declining_allAn out-of-office or focus-time event that declines every meeting it overlaps, the accepted ones too. Behind its own flag.
update_eventChange an event, including your reminders, its visibility and what guests may do, or add a Google Meet link. Only the fields you pass are touched.
cancel_eventCancel an event, or one occurrence of a repeating one.
move_eventMove an event to another calendar, which changes who organizes it.
respond_to_eventAnswer an invitation: accepted, declined or tentative.
create_calendarCreate a calendar of your own.
manage_calendarRename or re-zone a calendar, set your own color and name for it, or add and remove it from your list.
list_sharingWho can see a calendar, and what each of them can see.
share_calendarGive a person or a group inside your organization access below owner, or change the access they have.
unshare_calendarTake somebody's access away.
publish_calendarPublish a calendar to the internet, or open it to a whole domain. Gated.
widen_calendar_accessShare with somebody outside your organization, or make somebody an owner. Gated.
delete_calendarDelete a calendar and every event on it. Gated.
clear_calendarDelete every event on your primary calendar. Gated.

GCAL_READ_ONLY=true registers only the reads, the rows above create_event, and requests only read scopes, so the API itself refuses a write.

manage_calendar covers what the API splits across two resources and people do not: the calendar — its title, description, location and time zone — is what everybody it is shared with sees, while your subscription to it — the color, the name you give it, whether it is hidden, what you are emailed about — is yours alone. Unsubscribing removes it from your list; it deletes nothing and nobody else notices.

These rules run through every write:

  • `notify` is required whenever the write can reach another person, and there is no default in either direction. none is refused outright when a guest is outside your organization — such a guest may have no Google Calendar for the event to appear in, so email is the only way they can learn of it.
  • `scope` is required when the event repeats: instance, series or this_and_following. "Move the standup to 10:30" is three different operations and the API makes them look like one.
  • Every write is a patch under `If-Match`, so it is refused as [stale] rather than overwriting somebody who changed it first. Adding a guest reads the list and adds to it; it never replaces it.

dry_run: true on any of them reports what would change and how many guests would be emailed, without writing.

Above 200 guests Google stops propagating individual responses, so every result about such an event says that the RSVPs it lists are incomplete.

Resources

For clients that attach context rather than call tools, the same content is published as resources:

URIWhat it carries
gcal://calendarsThe calendar list, as list_calendars returns it.
gcal://calendars/{calendar_id}One calendar, as get_calendar returns it.
gcal://calendars/{calendar_id}/events/{event_id}One event, as get_event returns it.

They carry no handles and take no arguments, which is why there is no resource for a schedule: a window and a zone are not optional here, and a URI with nowhere to state them would have to invent both.

Working hours

check_availability answers over a window, and a window is one interval — so "next week, 09:00 to 17:00" cannot be asked for

Only the beginning is shown; read the rest in the repo