
CalendarMCP
ai.calendarmcp由 calendarmcp.ai 發布官方發布者v1.0.0更新於 Oct 25, 2026
Hosted Google Calendar MCP server for AI agents. No self-hosting or Google Cloud setup.
概覽
託管的 Google 日曆 MCP 伺服器,讓 AI 助理在已連結的 Google 帳戶中讀取、建立、更新與刪除日曆事件。
- 可以做什麼
- 跨一個或全部已連結日曆列出與讀取事件,包含事件詳細資料與日曆權限清單,並透過空閒/忙碌查詢在預訂前找出可用時段。建立事件(包含以自然語言快速新增),以及部分更新或刪除既有事件。管理參與者,將人員加入事件或從事件移除。一次並行呼叫可批次更新最多 50 個事件,適合重新命名重複會議。
- 適用情境
- 當你希望助理回答行程問題、尋找空閒時間,並在 Google 日曆中預訂或修改會議,又不想自行架設伺服器或設定 Google Cloud 憑證時使用。適合託管型 MCP 用戶端,以及擁有多個 Google 帳戶或啟用 Google 進階保護的使用者。
- 執行需求
- 透過 HTTP 存取的遠端 MCP 端點,不需要本機套件或 Docker。需要一個透過 OAuth 連結的 Google 帳戶(進階保護使用者可用服務帳戶共用),以及從服務商儀表板取得的 API 金鑰,以 bearer 權杖形式放在 Authorization 標頭中。需要能存取託管服務的網路;每個金鑰每分鐘 60 次請求的限制。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 CalendarMCP,將其新增到工作區。
- 連接 Authorization token 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/ai.calendarmcp%2Fserver/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"calendarmcp": {
"type": "http",
"url": "https://calendarmcp.ai/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
CalendarMCP
The hosted Google Calendar MCP server. Connect any AI agent to your Google Calendar in about two minutes. No self-hosting, no Docker, no
credentials.json.
What this is
CalendarMCP is a hosted Model Context Protocol (MCP) server for Google Calendar. Connect your Google account once, get an API key, and any MCP-compatible client (Claude Desktop, Claude Code, Claude.ai, Cursor, OpenClaw, Continue, Cline, Windsurf, Goose, Zed, ChatGPT custom GPTs, n8n, etc.) can read and write your calendar.
This repo is the public docs, manifest, and client examples for the service. The hosted service is not open source. If you want a self-hosted alternative, the most popular OSS option is nspady/google-calendar-mcp and we recommend it for users who want OAuth tokens to never leave their machine.
What CalendarMCP gives you that self-hosted MCPs do not
- Zero setup. One Google OAuth click. No
credentials.json, no Google Cloud Console, no Docker. - HTTP transport. Works with Claude.ai, Claude Code, Cursor, and any hosted MCP client. Self-hosted stdio MCPs only work with Claude Desktop.
- Batch operations.
batch_update_eventsupdates up to 50 events in one concurrent call. Renaming a recurring meeting across a year is one prompt, not 50 clicks. - Multi-account, one key. Connect any number of Google accounts (mix OAuth and service-account-shared calendars) under a single API key. Reading fans out across all of them, results merged and sorted.
- Google Advanced Protection support. The only hosted MCP that works for GAP users (via service-account sharing. OAuth is blocked for those accounts).
- Per-calendar Read/Write matrix. Tighten what each agent can touch from the dashboard without minting new keys.
Quick start
- Visit calendarmcp.ai, sign in with Google, and copy your API key.
- Add the MCP server to your client of choice. Configs below.
- Talk to your agent: "What do I have on Tuesday?"
Client configs
Drop these into the right config file for your MCP client.
Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
See examples/claude-desktop.json and our Claude Desktop integration guide.
Claude Code
See examples/claude-code.sh and our Claude Code integration guide.
Cursor
~/.cursor/mcp.json:
See examples/cursor.json and our Cursor integration guide.
OpenClaw
In your openclaw.json:
See examples/openclaw.json and our OpenClaw integration guide.
Other clients
See examples/ for Continue, Windsurf, Goose, n8n, and more.
Tools
CalendarMCP exposes 11 tools. The full machine-readable schema lives at https://calendarmcp.ai/api/docs.
Full reference: docs/tools.md.
Authentication
API keys are issued from the dashboard at calendarmcp.ai/dashboard. One key can hold any number of connected Google accounts. Per-calendar R/W scopes are enforced server-side.
Rate limit: 60 requests/minute per key. Free tier; pay-as-you-go pricing for higher limits coming soon.
Google Advanced Protection
If you have Google Advanced Protection enabled, OAuth into third-party calendar apps is blocked by Google policy. CalendarMCP supports a service-account sharing flow that works for GAP users. We're the only hosted MCP we know of that supports this.
See docs/google-advanced-protection.md.
Roadmap
- ✅ Google Calendar (live)
- ⏳ Microsoft Outlook Calendar (waitlist)
- ⏳ iCloud Calendar (waitlist)
- ⏳ CalDAV (any provider)
Pricing
Free tier with generous limits. Paid plans land soon for power users.
Comparison
Honest read: pick nspady if you only use Claude Desktop and want zero third parties. Pick CalendarMCP for everything else.
Contributing
This repo is docs and examples. PRs welcome for:
- New client config examples
- Doc improvements and clarifications
- Translations
Service issues (bugs, feature requests for the hosted product) → GitHub Issues.
License
Examples and docs in this repo: MIT (see LICENSE).
The hosted service is not open source.
Links
- calendarmcp.ai. The service
- Docs
- Blog
- Changelog
- Integrations
- Use cases
來源:README.md,提交 cb6a55d
工具
0版本歷史
1- v1.0.0最新Sep 16, 2026
評分
已滿足適用檢查項的 75%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具必需15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
請在儲存庫或註冊中心條目中宣告授權條款。
