MinerU
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Google Calendar over MCP: calendars, events, recurrence and availability.
Skills that teach the AI this kind of work; they work alongside this one
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
A privacy-first app that strips AI watermarks from content you own.
Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
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
Download the maker’s .mcpb file
The .mcpb file comes straight from the maker; we do not change 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
A · Use an app that can connect Google Calendar MCP
Claude Code cannot connect Google Calendar MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Google Calendar MCP
Cursor cannot connect Google Calendar MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Google Calendar MCP
VS Code cannot connect Google Calendar MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Google Calendar MCP
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
mcpb: …/google-calendar-mcp_5.1.1.mcpbBased 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
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account mmedum, which owns the repo
Code last changed today
Uses Apache-2.0
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/mmedum-google-calendar-mcp)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.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed today, and the latest version (5.1.1) reached the registry 16 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Puter MCP, XcodeBuildMCP, Vexa, Atlassian Rovo MCP Server, Anki MCP Server
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 enables AI tools to interact with Puter: manage files, websites, workers, and more
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Atlassian’s official server lets AI search and manage Jira work and Confluence pages. Connects to Atlassian’s cloud with OAuth sign-in.
MCP server for Anki flashcards: adaptive review, notes, media, and deck management via AnkiConnect.
| This one Google Calendar MCP | Puter MCP | XcodeBuildMCP | Vexa | Atlassian Rovo MCP Server | Anki MCP Server | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Installs on your computer |
| Needs a key | No | No | No | Yes | No | No |
| Add with + in Claude | No | No | No | No | Yes | No |
| Basic checks | 3/3 | 4/4 | 3/3 | 2/4 | 4/4 | 3/3 |
| License | Apache-2.0 | AGPL-3.0 | MIT | Apache-2.0 | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
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.
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:
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.dry_run.Non-goals:
list_changes hands back a sync token instead.Calendar tooling often gets these wrong. This server is built around getting them right, and a test enforces each:
The design and the decisions behind it are in docs/architecture.md.
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.
You need your own Google Cloud project and OAuth client. Nothing deployer-specific is baked into this repository.
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.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.
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.
{
"mcpServers": { "google-calendar": { "command": "google-calendar-mcp", "env": { "GCAL_CLIENT_SECRET": "/path/to/client_secret.json" } } } }
Every setting is in docs/configuration.md.
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.
| Tool | What it does |
|---|---|
list_calendars | Every calendar this account can see, with ids, time zones and your access level. Start here. |
get_calendar | One calendar in full, including who it is shared with and its default reminders. |
list_events | The 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_events | Free-text search across a window, over titles, descriptions, locations and guests. |
get_event | One event, with its guests and their responses, what guests may do, your reminders, and the files attached to it. |
list_instances | The occurrences of one repeating event, with the dates that were moved or removed. |
list_changes | What 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_availability | When 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_settings | The account's time zone, week start and color palette. |
create_event | Create 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_all | An out-of-office or focus-time event that declines every meeting it overlaps, the accepted ones too. Behind its own flag. |
update_event | Change 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_event | Cancel an event, or one occurrence of a repeating one. |
move_event | Move an event to another calendar, which changes who organizes it. |
respond_to_event | Answer an invitation: accepted, declined or tentative. |
create_calendar | Create a calendar of your own. |
manage_calendar | Rename or re-zone a calendar, set your own color and name for it, or add and remove it from your list. |
list_sharing | Who can see a calendar, and what each of them can see. |
share_calendar | Give a person or a group inside your organization access below owner, or change the access they have. |
unshare_calendar | Take somebody's access away. |
publish_calendar | Publish a calendar to the internet, or open it to a whole domain. Gated. |
widen_calendar_access | Share with somebody outside your organization, or make somebody an owner. Gated. |
delete_calendar | Delete a calendar and every event on it. Gated. |
clear_calendar | Delete 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:
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.instance, series or this_and_following. "Move the standup to 10:30" is three different operations and the API makes them look like one.[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.
For clients that attach context rather than call tools, the same content is published as resources:
| URI | What it carries |
|---|---|
gcal://calendars | The 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.
check_availability answers over a window, and a window is one interval — so "next week, 09:00 to 17:00" cannot be asked for