Read, create, and manage events across Google Calendar — via Google's official remote MCP or a self-hosted community server.
Cal.com
Official Cal.com hosted MCP — AI agents book, reschedule, and query availability across 34 tools via OAuth 2.1, no local install.
Quick answer
What it does
Exposes 34 tools for the full Cal.com scheduling lifecycle: list and create event types, query real-time availability, book and reschedule appointments, cancel bookings, and manage schedules — all over OAuth 2.1 with no local setup.
Best for
- Agentic booking assistants
- Product-embedded scheduling workflows
- Demo and onboarding scheduling
- Self-hosted scheduling setups
Not for
- Raw calendar event management outside booking flows
- Bulk calendar analytics
Source: top-mcps.com/mcp/calcom-mcp — verified Sep 2026
Setup recipe
Pick your client, then follow the three steps.
- 1
Install
claude_desktop_config.jsonjson{ "mcpServers": { "calcom-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.cal.com/mcp" ] } } }Claude Desktop launches stdio servers, so mcp-remote bridges to the hosted endpoint and opens the sign-in in your browser. On Pro, Max, Team and Enterprise you can skip the file: Settings → Connectors → Add custom connector → https://mcp.cal.com/mcp. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
CLI or .mcp.jsonshellclaude mcp add --transport http calcom-mcp https://mcp.cal.com/mcpThen run /mcp inside Claude Code to finish the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
.cursor/mcp.jsonjson{ "mcpServers": { "calcom-mcp": { "url": "https://mcp.cal.com/mcp" } } }Global path: ~/.cursor/mcp.json. Cursor shows "Needs login" once it connects — click it to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
.vscode/mcp.jsonjsonc{ "servers": { "calcom-mcp": { "type": "http", "url": "https://mcp.cal.com/mcp" } } }VS Code uses the "servers" key. Run MCP: List Servers → Start Server and allow the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
~/.codeium/windsurf/mcp_config.jsonjson{ "mcpServers": { "calcom-mcp": { "serverUrl": "https://mcp.cal.com/mcp" } } }Windsurf uses "serverUrl" for hosted servers. Open via Cascade → hammer icon → Configure. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
cline_mcp_settings.jsonjson{ "mcpServers": { "calcom-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.cal.com/mcp" ] } } }Bridged through mcp-remote. Open via the Cline sidebar → MCP Servers → Edit. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
~/.continue/config.jsonjson{ "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "streamable-http", "url": "https://mcp.cal.com/mcp" } } ] } }Continue takes the hosted URL directly in the transport block. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
CLIshellcodex mcp add calcom-mcp --url https://mcp.cal.com/mcpCodex detects OAuth support and opens the browser to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
~/.config/zed/settings.jsonjsonc{ "context_servers": { "calcom-mcp": { "command": { "path": "npx", "args": [ "-y", "mcp-remote", "https://mcp.cal.com/mcp" ] } } } }Bridged through mcp-remote under "context_servers". Settings live-reload on save. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
ChatGPT → Settings → Connectors (remote URL)json{ "name": "Cal.com", "transport": "http", "url": "https://mcp.cal.com/mcp" }Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled.
- 2
Set required secrets
No credentials required — this MCP runs over stdio without authentication.
- 3
Try a minimum working prompt
Book a 30-minute call in the next 3 days
Check my Cal.com availability for 30-minute slots in the next 3 business days and book the first one that works for me at 10am or 2pm.Tested with: Claude Desktop, Cursor.
Tools & permissions
Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.
Security & scope
- Access scope
- Network
- Sandbox
- OAuth 2.1 scoped to the authenticated Cal.com account. The hosted MCP is Cal.com-operated — no user credentials touch your machine. The agent can only manage calendars, bookings, and availability that belong to the authorized account.
- Gotchas
- Booking creation is irreversible without an explicit cancellation tool call — the agent should confirm booking details with the user before calling create_booking.
- Availability queries respect the configured Cal.com schedule and buffer times; the agent cannot book outside the configured availability windows.
- Self-hosted instances require configuring the NEXTAUTH_URL and MCP_URL environment variables to expose the MCP endpoint.
Agent prompt pack
— copy into Claude, Cursor, or ChatGPT.Recommend the best MCP servers for [task: e.g. scheduling & calendar work] in [client: Claude]. Constraints: - Prefer tools that are [official | open-source | read-only] — pick what matters for my use case. - Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport]. - Return at most 3 picks, ranked. For each pick include: 1. One-sentence rationale. 2. The ready-to-paste install snippet for my client. 3. Any required secrets I need to create before installing. Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-scheduling-calendar
Compare Cal.com MCP vs [Google Calendar MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"]. Judge them on: - Setup time and complexity (what a new user hits first). - Auth model (none / API key / OAuth 2.1) and credential risk. - Transport (stdio / Streamable HTTP / SSE) and where the server runs. - Required secrets and the blast radius if they leak. - Operational risk in an unattended agent loop. - Which one is "good enough" for a weekend prototype vs. production. End with one sentence: which should I pick for my scenario, which is: [my scenario]. References: - https://top-mcps.com/mcp/calcom-mcp - top-mcps.com listing for Google Calendar
Install the Cal.com MCP server for my [client: Claude] at the default config path for that client. Use the exact install snippet published at https://top-mcps.com/mcp/calcom-mcp (fetch https://top-mcps.com/mcp/calcom-mcp.json for the canonical server.json if you can read URLs). Before finishing: 1. Create the required secrets (no secrets) and put them in the appropriate env block — do not hard-code them. 2. Restart or reload the client so it picks up the new server. 3. Verify the server is connected (green / running state) and at least one tool is listed. 4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry. Confirm when done and list the tools the server now exposes.
Frequently asked questions
What changed
— 2 updates tracked.Refreshed install snippets and fact sheet; verified for 2026.
Initial directory listing.
More Scheduling & Calendar MCPs
Other tools in the same category worth evaluating.
Official hosted MCP for booking-link scheduling — share availability without exposing the raw calendar.
Read and create events in Apple Calendar via CalDAV from any MCP client.
Compared with Cal.com
Side-by-side breakdowns for the choices people most often weigh against this MCP.
Exploring Top MCPs for Scheduling & Calendar? See all Scheduling & Calendar MCPs →