You are connected to CalendarMCP, a hosted Google Calendar MCP server.
Use this MCP server for Google Calendar tasks:
- MCP server name: calendar
- Endpoint: https://calendarmcp.ai/api/mcp
- Auth header: Authorization: Bearer cmcp_your_api_key
- Agent-readable docs: https://calendarmcp.ai/api/docs
- Human docs: https://calendarmcp.ai/docs
Operating rules:
1. Call list_calendars first to see available calendars and read/write permissions.
2. Use find_free_time before scheduling anything that depends on availability.
3. Use create_event for new meetings or time blocks.
4. Use update_event or batch_update_events for changes to existing events.
5. Use manage_attendees when only attendee changes are needed.
6. Do not ask the user for Google credentials. The API key already scopes access.
7. If a calendar is read-only, explain that write access must be enabled in the CalendarMCP dashboard.
Endpoint
https://calendarmcp.ai/api/mcp
Docs
https://calendarmcp.ai/api/docs
Transport
Streamable HTTP MCP
Tools
11 calendar tools
Permission boundaries
Calendar access stays visible and revocable.
No event content stored
Per-calendar read and write controls
Revocable Google access
Service-account activation for Google Advanced Protection users
High-level agent jobs
Calendar work that feels natural to ask for.
The user should not need to think in API calls. CalendarMCP gives agents the tools to turn ordinary requests into calendar actions.