原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Google Calendar MCP

作者:mmedum版本 5.1.1i★ 0i在你的电脑上运行代码仓库 ↗
注册名称io.github.mmedum/google-calendar-mcp

安装方法

What it does

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

  • Connects 在你的电脑上运行
  • Account or key No key needed
  • Category 文档、表格与办公

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

MinerU

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

作者:opendatalab★ 83,9191 个 skill

Skill · 操作手册未注明许可证

watermarks-remover

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

作者:guillaumemeyer★ 27,7231 个 skill

Skill · 操作手册

obsidian-skills

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

作者:kepano★ 53,104 (whole repo)5 个 skill

Skill · 操作手册

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分12/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude,但需要先准备

不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

  1. 下载开发者的安装文件

    下载作者的 .mcpb 文件

    .mcpb 文件直接来自开发者,我们没有修改

  2. 双击文件,然后在电脑版 Claude 应用中点击 Install

  3. 试一试

    用 Google Calendar MCP 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Google Calendar MCP,或回答中出现 Google Calendar MCP 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 Google Calendar MCP

Google Calendar MCP 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器

你可以改用这些方式

A · 使用能连接 Google Calendar MCP 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

B · 文档、表格与办公 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 Google Calendar MCP

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 Google Calendar MCP 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

Cursor 暂时无法连接 Google Calendar MCP

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 Google Calendar MCP 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

VS Code 暂时无法连接 Google Calendar MCP

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 Google Calendar MCP 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Google Calendar MCP 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
许可证i
Apache-2.0
连接方式
在你的电脑上运行
最新版本i
5.1.1
发布到注册中心i
2026年11月3日
代码最后更新i
2026年11月19日
作者
mmedum
软件包
mcpb: …/google-calendar-mcp_5.1.1.mcpb
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

在你的电脑上运行,适用于

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

全部应用及其优缺点 →

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 mmedum 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于今天

  • ✓ 通过

    有许可证

    使用 Apache-2.0

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

已公开的漏洞(OSV.dev)

未检查:只能检查标明版本的 npm 和 PyPI 包

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

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

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“文档、表格与办公”中的其他服务器比较i

  • 星标数多于此分类中其他 4110 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 4110 个服务器的 68% 更新
  • 基础检查结果等于或优于此分类中其他 4110 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Google Calendar MCP 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于今天,最新版本(5.1.1)于16天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。

有什么可以替代它?

同一分类中有:Puter MCP, XcodeBuildMCP, Vexa, Atlassian Rovo MCP Server, Anki MCP Server

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Puter MCP

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

作者:HeyPuter广泛使用★ 4.4万5个月前更新

在云端运行✓ 服务方 · puter.com

XcodeBuildMCP

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

作者:getsentry广泛使用↓ 13万/周 共用包的下载量★ 65854个月前更新

在你的电脑上运行✓ 服务方 · xcodebuildmcp.com

Vexa

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

作者:Vexa-ai广泛使用★ 29942个月前更新

在云端运行✓ 服务方 · vexa.ai

Anki MCP Server

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

作者:ankimcp正在增长↓ 1136/周★ 567上个月更新

在你的电脑上运行✓ 服务方 · ankimcp.ai
与相似项目对比
本项
Google Calendar MCP
Puter MCPXcodeBuildMCPVexaAtlassian Rovo MCP ServerAnki MCP Server
运行位置需要安装在电脑上在云端运行,无需安装需要安装在电脑上在云端运行,无需安装在云端运行,无需安装需要安装在电脑上
需要密钥否否否是否否
可在 Claude 中按 + 添加否否否否是否
基础检查3/34/43/32/44/43/3
许可证Apache-2.0AGPL-3.0MITApache-2.0Apache-2.0MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

只显示了开头部分;其余内容请在仓库中阅读