<- CalendarMCP

Client setup

MCP client integrations

One endpoint works across Claude, Cursor, coding agents, workflow tools, and any HTTP-capable MCP client.

Shared endpoint
https://calendarmcp.ai/api/mcp

Authenticate with an Authorization: Bearer header.

Supported clients

Choose the closest setup path

Get your API key ->
CD
Claude Desktop
HTTP transport

Anthropic desktop app. Add CalendarMCP through mcp_servers config.

View setup guide ->
CC
Claude Code
HTTP transport

Terminal-based coding agent. Register the endpoint with one command.

View setup guide ->
C
Claude.ai
HTTP transport

Claude web app. Add the server from Settings -> Connectors.

Setup docs ->
Cu
Cursor
HTTP transport

AI code editor. Add CalendarMCP to your MCP settings JSON.

View setup guide ->
OC
OpenClaw
HTTP transport

Personal AI assistant platform with plug-in HTTP MCP config.

View setup guide ->
He
Hermes Agent
HTTP transport

Nous Research agent with remote HTTP MCP support through ~/.hermes/config.yaml.

Setup docs ->
Ag
Google Antigravity
HTTP transport

Google agentic IDE. Add CalendarMCP through the MCP server raw config using serverUrl.

Setup docs ->
Co
Continue
HTTP transport

Open-source coding assistant for VS Code and JetBrains.

Setup docs ->
Cl
Cline
HTTP transport

Autonomous coding agent extension for VS Code.

Setup docs ->
Wi
Windsurf
HTTP transport

Codeium editor with MCP plugin support.

Setup docs ->
GP
ChatGPT
OpenAPI transport

Use CalendarMCP as an OpenAI Actions endpoint in a custom GPT.

Setup docs ->
Cx
Codex CLI
HTTP transport

OpenAI terminal coding agent. Pass MCP config via --mcp-config.

Setup docs ->
n8
n8n
HTTP transport

Workflow automation. Use HTTP Request with Bearer auth.

Setup docs ->
Go
Goose
HTTP transport

Block open-source AI agent. Add CalendarMCP as an MCP extension.

Setup docs ->
mh
mcphost
HTTP transport

CLI tool for running LLMs with MCP servers. Drop-in config.

Setup docs ->
Ze
Zed
HTTP transport

High-performance editor with MCP context-server support.

Setup docs ->

Generic setup

Any HTTP MCP client can use the same contract.

If your client is not listed, use these values. Streamable HTTP and SSE clients work at the same endpoint.

Endpoint
https://calendarmcp.ai/api/mcp
Auth header
Authorization: Bearer cmcp_...
Transport
Streamable HTTP or SSE

Frequently asked questions

Does it support my MCP client?

If your client supports Streamable HTTP MCP, yes. The endpoint is https://calendarmcp.ai/api/mcp with a Bearer token header. SSE-based clients also work.

What is the difference between SSE and HTTP MCP transport?

SSE is the older MCP transport. Streamable HTTP is the current standard. CalendarMCP supports both at the same endpoint.

Do I need a separate API key per client?

No. One API key works with all clients simultaneously. They share the same calendar access and rate-limit bucket.

Can I connect multiple Google accounts?

Yes. Add multiple Google connections under one API key, then control each calendar with per-calendar read/write permissions.

Is there a local version I can self-host?

Not officially. CalendarMCP is a hosted service. The OAuth callback and token management are handled server-side so setup stays short.