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.
教 AI 做这类工作的 Skill,可与本项一起使用
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
用 Google Calendar MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Google Calendar MCP,或回答中出现 Google Calendar MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Google Calendar MCP
Google Calendar MCP 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
Claude Code 暂时无法连接 Google Calendar MCP
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Google Calendar MCP 的应用
Cursor 暂时无法连接 Google Calendar MCP
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Google Calendar MCP 的应用
VS Code 暂时无法连接 Google Calendar MCP
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Google Calendar MCP 的应用
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 mmedum 验证,该账户拥有此仓库
代码最后更新于今天
使用 Apache-2.0
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/mmedum-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 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.
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
MCP server for Anki flashcards: adaptive review, notes, media, and deck management via AnkiConnect.
| 本项 Google Calendar MCP | Puter MCP | XcodeBuildMCP | Vexa | Atlassian Rovo MCP Server | Anki MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 需要安装在电脑上 |
| 需要密钥 | 否 | 否 | 否 | 是 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 3/3 | 4/4 | 3/3 | 2/4 | 4/4 | 3/3 |
| 许可证 | Apache-2.0 | AGPL-3.0 | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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