CalendarMCP works with every major MCP client. One API key, one endpoint, connect in 2 minutes.
https://calendarmcp.ai/api/mcpBearer authAnthropic's desktop app. Add CalendarMCP via mcp_servers config.
View setup guide →Claude's terminal-based coding agent. One command to add.
View setup guide →Use CalendarMCP as an OpenAI Actions endpoint in a custom GPT.
Setup docs →OpenAI's terminal coding agent. Pass MCP config via --mcp-config.
Setup docs →Workflow automation platform. Use the HTTP Request node with Bearer auth.
Setup docs →If your client isn't listed above, use these values. Any client that supports Streamable HTTP MCP or SSE MCP will work.
https://calendarmcp.ai/api/mcpAuthorization: Bearer cal_...Streamable HTTP or SSEIf your client supports Streamable HTTP MCP (the current standard), yes. The endpoint is https://calendarmcp.ai/api/mcp with a Bearer token header. SSE-based clients also work. Same URL, same auth.
SSE (Server-Sent Events) is the older MCP transport. Streamable HTTP is the current standard. CalendarMCP supports both at the same endpoint. Most clients released after mid-2025 use HTTP transport by default.
No. One API key works with all clients simultaneously. If you connect multiple clients, they all share the same calendar access and rate limit bucket.
Yes. From the dashboard you can add multiple Google connections under one API key. Each connection's calendars are available to your agent with per-calendar read/write permissions.
Not officially. CalendarMCP is a hosted service. The OAuth callback and token management are handled server-side, which is why setup is a 2-minute process instead of half a day.