
Mewcp Google Calendar
io.github.AMMAR-62由 GitHub 帳號 AMMAR-62 發布v1.0.0更新於 Oct 24, 2026
Schedule smarter - create, search, and manage Google Calendar events through AI.
發布方自己的服務:MewCP
概覽
一個本機 MCP 伺服器,讓 AI 助理讀取、建立、更新、移動和刪除 Google 日曆活動與日曆。
- 可以做什麼
- 依時間範圍、文字和重複規則列出、搜尋並取得活動,包含重複活動執行個體與分頁;取得單一活動的詳細資料、參與者和回覆狀態;查詢多個日曆的忙碌時段以找出空檔;建立單次、全天、快速和重複活動,可設定參與者、提醒、Meet 連結和可見度;更新活動並管理參與者;在日曆之間移動活動;列出、取得和建立日曆;刪除活動、日曆或清空日曆中的所有活動。
- 適用情境
- 適合讓助理代替使用者安排、改期或查詢會議,在提議時間前檢查多個日曆的可用性,或讓工作流程自動化讀取日曆狀態以觸發以時間為基礎的動作。
- 執行需求
- 以本機程序方式執行(Docker 映像,streamable-http 傳輸),僅限桌面環境。README 的疑難排解提到 Authorization 承載權杖和 X-Mewcp-Credential-Id 標頭,以及需要 MewCP 帳戶並連接 Google 日曆 OAuth 憑證;但清單未宣告任何驗證或環境變數,實際設定需向提供者確認。需要存取 Google 日曆和提供者服務的網路。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Mewcp Google Calendar,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
Schedule smarter — create, search, and manage Google Calendar events through AI.
A Model Context Protocol (MCP) server that exposes Google Calendar's API for creating, reading, updating, and deleting events and calendars.
Overview
The Google Calendar MCP Server provides full calendar management directly from AI workflows:
- List, search, and retrieve events with rich filtering by time range, text, and recurrence
- Create single, all-day, quick, and recurring events with attendees, reminders, and Meet links
- Update events and manage attendees, then get before/after state in a single response
- Query free/busy blocks across multiple calendars to find open slots without conflicts
Perfect for:
- AI assistants that schedule, reschedule, and manage meetings on behalf of users
- Workflow automation that reads calendar state to trigger time-based actions
- Agents that coordinate availability and send invitations across teams
Tools
Events — Read
list_events — List events from a calendar
Lists events from a calendar within an optional time range. Returns events in start-time order. Recurring events are expanded into individual instances. Use ISO 8601 for time_min/time_max: 'YYYY-MM-DDTHH:MM:SSZ' (e.g. '2026-01-08T00:00:00Z'). Defaults to events from now onwards if time_min is not specified.
Inputs:
Output data schema:
get_event — Get a single event by ID
Gets full details of a specific event including attendees, RSVP statuses, recurrence rules, reminders, and conferencing info.
Inputs:
Output data schema:
search_events — Search events by text
Searches for events by text across titles, descriptions, and locations. Optionally bound the search to a time range with time_min/time_max (ISO 8601, e.g. '2026-01-08T00:00:00Z'). Without a time range the search spans all history — always use a time range for large calendars.
Inputs:
Output data schema:
get_upcoming_events — Get events in the next N days
Gets events starting from now through the next N days. Returns events in start-time order. Recurring events are expanded into individual instances.
Inputs:
Output data schema:
get_todays_events — Get all events for today
Gets all events scheduled for today in the given timezone. Pass the user's local timezone to get the correct day (e.g. 'America/New_York'). Defaults to UTC.
Inputs:
Output data schema:
list_event_instances — List instances of a recurring event
Lists all individual instances of a recurring event by its master event ID. Use this to see every occurrence of a recurring series — use get_event or list_events to find the master event ID first. Instances include recurringEventId (the master ID) and originalStartTime (the scheduled time per RRULE, which differs from start if the instance was rescheduled). Optionally filter by time range to see only upcoming or past occurrences.
Inputs:
Output data schema:
Events — Write
create_event — Create a new calendar event
Creates a new calendar event and optionally invites attendees. For timed events use ISO 8601 datetime: '2026-01-08T14:30:00' with a timezone. For all-day events set is_all_day=True and use date-only format: '2026-01-08' — for all-day events end_time is exclusive, so a single-day event on Jan 8 needs end_time='2026-01-09'. Returns the created event with its ID.
Inputs:
Output data schema:
create_quick_event — Create an event from natural language
Creates an event from a natural language text description. Google Calendar parses the text to extract title, date, time, and recurrence. Examples: 'Lunch with Sarah tomorrow at noon', 'Team standup every Monday at 9am'. Returns the created event. For complex events with attendees or custom fields, use create_event instead.
Inputs:
Output data schema:
create_recurring_event — Create a recurring event with an RRULE
Creates a recurring calendar event using an RRULE recurrence pattern. recurrence_rule must start with 'RRULE:' followed by RFC 5545 parameters. Examples: 'RRULE:FREQ=DAILY;COUNT=5', 'RRULE:FREQ=WEEKLY;BYDAY=MO,WE,FR', 'RRULE:FREQ=MONTHLY;BYMONTHDAY=15', 'RRULE:FREQ=YEARLY'. Returns the master recurring event — individual instances are expanded by Google Calendar.
Inputs:
Output data schema:
update_event — Update an existing event
Updates an existing calendar event. Only the fields you provide are changed — leave a field empty to keep its current value. Fetches the current event first, applies changes, then saves. Use ISO 8601 for times: 'YYYY-MM-DDTHH:MM:SS'. For recurring events: pass the master recurring event ID to change all instances, or a specific instance ID to change only that occurrence. WARNING: do not update individual instances one-by-one to change the whole series — update the master event instead. Modifying instances individually creates exceptions that clutter the calendar and trigger excessive notifications. To cancel a single instance without affecting the rest of the series, set status='cancelled'.
Inputs:
Output data schema:
add_attendees — Add attendees to an event
Adds new attendees to an existing event and sends them invitation emails. Skips emails that are already on the attendee list.
Inputs:
Output data schema:
Events — Delete
delete_event — Permanently delete an event
DESTRUCTIVE — REQUIRES EXPLICIT USER CONFIRMATION BEFORE CALLING. Permanently deletes a calendar event. This action is irreversible: the event, its attendees list, reminders, and all associated data are removed immediately and cannot be recovered. Attendees will receive cancellation emails (controlled by send_updates). For recurring events: deleting the master event ID removes the entire series and all its instances. Deleting a specific instance ID removes only that one occurrence. NEVER call this tool autonomously or as part of an automated flow. You MUST stop, tell the user the event title, date, and time that will be permanently deleted, and for recurring events clarify whether you are deleting one occurrence or the entire series, and wait for their explicit written confirmation before proceeding.
Inputs:
Output data schema:
move_event — Move an event to another calendar
DESTRUCTIVE — REQUIRES EXPLICIT USER CONFIRMATION BEFORE CALLING. Moves a default event from one calendar to another. Only events of type 'default' can be moved — birthday, focusTime, fromGmail, outOfOffice, and workingLocation events cannot be moved and will return an error. The event is removed from the source calendar and placed in the destination calendar — any calendar-specific settings, sharing permissions, or notification rules from the source will no longer apply. While technically reversible by moving back, this can disrupt other attendees and shared calendar visibility in ways that are hard to track down. NEVER call this tool autonomously. You MUST tell the user which event is being moved, from which calendar to which, and wait for their explicit confirmation.
Inputs:
Output data schema:
Calendars
list_calendars — List all calendars
Lists all calendars the user has access to. Returns calendar IDs, names, timezones, colors, and access roles. Use min_access_role to filter to calendars the user can write to.
Inputs:
Output data schema:
get_calendar — Get a single calendar
Gets full details of a specific calendar including its name, description, timezone, and color settings.
Inputs:
Output data schema:
create_calendar — Create a new calendar
Creates a new calendar owned by the user. Returns the created calendar with its ID, which is needed for all subsequent operations on that calendar.
Inputs:
Output data schema:
delete_calendar — Permanently delete a calendar
DESTRUCTIVE — REQUIRES EXPLICIT USER CONFIRMATION BEFORE CALLING. Permanently deletes an entire calendar and every event it contains. This action is irreversible: all events, recurring series, and history in the calendar are gone immediately with no way to recover them. NEVER call this tool autonomously or as part of an automated flow. You MUST stop, tell the user exactly which calendar will be deleted and that all its events will be permanently lost, and wait for their explicit written confirmation before proceeding.
Inputs:
Output data schema:
clear_calendar — Delete all events from a calendar
DESTRUCTIVE — REQUIRES EXPLICIT USER CONFIRMATION BEFORE CALLING. Permanently deletes ALL events from a calendar without deleting the calendar itself. This action is irreversible: every event in the calendar — past, present, and future — is removed immediately with no way to recover them. The calendar itself remains and can be used for new events. This is the only way to clear the primary calendar, which cannot be deleted. NEVER call this tool autonomously or as part of an automated flow. You MUST stop, tell the user exactly which calendar will be cleared and that every event in it will be permanently deleted, and wait for their explicit written confirmation before proceeding.
Inputs:
Output data schema:
Free/Busy
get_free_busy — Query busy blocks across calendars
Returns busy time blocks for one or more calendars within a time range. Use this to find when someone is available or to schedule without conflicts. Provide time_min and time_max in ISO 8601 format with timezone, e.g. '2026-01-08T09:00:00Z'. Returns a map of calendar ID → list of busy time blocks. Free time = gaps between the busy blocks within the requested range.
Inputs:
Output data schema:
API Parameters Reference
Response Envelope
Every tool returns the same top-level envelope. Only data varies per tool.
retriable—truewhen it is safe to retry (rate limit, network error, 503).falsefor validation and auth errors.retry_after_seconds— seconds to wait before retrying; present only whenretriableistrueand the upstream specifies a delay.
Date and Time Formats
All tools use ISO 8601 format for date and time values.
Timed events:
All-day events (use with is_all_day=true):
For all-day events, end_time is exclusive — a single-day event on Jan 8 needs end_time='2026-01-09'.
Recurrence Rules (RRULE)
create_recurring_event requires an RFC 5545 RRULE string starting with RRULE:.
Calendar ID
primary— the user's main Google Calendar (always valid)- All other calendars use a full ID from
list_calendars, e.g.[email protected]
list_calendars returns id for every calendar the user has access to.
Pagination
list_events, search_events, list_event_instances, and list_calendars support pagination via next_page_token.
When data.next_page_token is non-null in a response, pass it as page_token in the next call with the same parameters to retrieve the next page.
Troubleshooting
Missing or Invalid Headers
- Cause: OAuth token not provided in request headers or incorrect format
- Solution:
- Verify
Authorization: Bearer YOUR_TOKENandX-Mewcp-Credential-Id: CREDENTIAL-IDheaders are present - Check the OAuth token has not expired — reconnect in your MewCP account if needed
- Verify
Insufficient Credits
- Cause: API calls have exceeded your request limits
- Solution:
- Check credit usage in your Curious Layer dashboard
- Upgrade to a paid plan or add credits for higher limits
- Contact support for credit adjustments
Credential Not Connected
- Cause: No Google Calendar credential linked to your account
- Solution:
- Go to Credentials in your MewCP dashboard
- Connect your Google account (OAuth)
- Retry the request with the correct
X-Mewcp-Credential-Idheader
Malformed Request Payload
- Cause: JSON payload is invalid or missing required fields
- Solution:
- Validate JSON syntax before sending
- Ensure all required tool parameters are included
- Check parameter types match expected values (e.g.
time_minmust be ISO 8601)
Server Not Found
- Cause: Incorrect server name in the API endpoint
- Solution:
- Verify endpoint format:
{server-name}/mcp/{tool-name} - Use the correct server name from documentation
- Check available servers in your Curious Layer account
- Verify endpoint format:
Google Calendar API Error
- Cause: Upstream Google Calendar API returned an error
- Solution:
- Check Google Workspace Status for service issues
- Verify your Google account has the required calendar permissions
- Review the error message in the response for specific details
Resources
- Google Calendar API Documentation — Official API reference
- Google Calendar API Events Reference — Complete events endpoint reference
- FastMCP Docs — FastMCP specification
- FastMCP Credentials — FastMCP Credentials package for credential handling
來源:README.md,提交 f93fec9
工具
0版本歷史
1- v1.0.0最新Sep 16, 2026
評分
已滿足適用檢查項的 40%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
請在儲存庫或註冊中心條目中宣告授權條款。
