Claude + Cal.com: What the Integration Can (and Can't) Do in 2026
Cal.com ships its own official MCP server, so connecting it to Claude is genuinely easy — but there’s no one-click entry in Anthropic’s connector directory. You add it yourself as a custom connector pointing at mcp.cal.com, and once it’s live Claude can create bookings, spin up event types, read your availability, and reschedule or cancel meetings from a chat. Because Cal.com is open-source and API-first, you also have a clean REST route and a couple of community servers if you’d rather self-host.
Here’s each route, when to pick it, and what to use when you want Cal.com work that happens without you at the keyboard.
Route 1: The official Cal.com MCP server (recommended)
Cal.com maintains its own MCP server — the repo is calcom/cal-mcp and the docs live at cal.com/docs/mcp-server. The hosted endpoint is https://mcp.cal.com/mcp, using Streamable HTTP transport with OAuth 2.1, so your client walks you through authorization and you never paste an API key.
It exposes 34 tools across 8 categories: user profile, event types, bookings, schedules, availability, conferencing, routing forms, and organizations. In practice that means Claude can check your open slots, book or cancel a meeting, create a new event type, and edit your working hours — all in one conversation.
To connect it in Claude:
- Open Claude, go to Settings → Connectors.
- Click Add custom connector.
- Name it
Cal.com, set the MCP Server URL tohttps://mcp.cal.com/mcp. - Complete the OAuth prompt when Claude asks.
This works on Claude web, desktop, and mobile for plans that support custom connectors. Everyday wins: “what’s my availability Thursday afternoon,” “book a 30-minute intro with this person,” “create a 15-minute event type with a 4-hour notice window.”
Route 2: Run the MCP server locally (stdio)
If you’d rather keep everything on your machine or you’re building against a self-hosted Cal.com instance, run the server locally. You need Node.js 18+ and a Cal.com API key from Settings → Developer → API Keys. Point your client at:
npx @calcom/cal-mcp@latestwith CAL_API_KEY set in the environment. This uses stdio transport instead of HTTP — more control for development, but it only runs while that process (and your machine) is up.
Route 3: The Cal.com API v2 directly
Cal.com is API-first, so the underlying REST layer is fully documented at cal.com/docs/api-reference/v2. The base URL is https://api.cal.com/v2 (or your self-hosted domain), auth is via the Authorization header with a key generated under Settings → Security (test keys prefixed cal_, live keys cal_live_). Cal.com recommends OAuth credentials for anything you’re shipping to real users. The rate limit on an API key is 120 requests/minute by default.
Endpoints cover bookings, event types, schedules, slots, calendars, and webhooks. Point Claude Code at these docs and it can scaffold a booking script or a webhook handler for you. There’s also a community project, bcharleson/calcom-cli, an agent-native CLI and MCP server wrapping the v2 API — useful if you want a broader tool surface than the official server exposes.
The limits that actually matter
- No directory connector. Unlike Calendly, Cal.com isn’t a one-click entry in Anthropic’s connector directory — you add it as a custom connector. Minor, but worth knowing.
- No event triggers. Nothing about a booking reaches Claude. It won’t notice a new booking, prep you before a call, or react to a cancellation — it acts on your prompt or on a clock, and Cal.com moves on neither.
- Laptop-bound if you self-host. The local stdio route only runs while your machine is on. The hosted server clears that, but it still only acts when something on the Claude side asks it to.
- It reacts, it doesn’t watch. Claude answers “what’s on my calendar tomorrow” beautifully, but it can’t sit on your Cal.com webhook and act when the world changes.
Claude + Cal.com is excellent for on-demand scheduling and API work; it’s not built for booking workflows that need to fire on their own.
If you want Cal.com work that runs on its own: Carly
Carly is an AI executive assistant that acts across your whole stack on real events, not just on prompts and timers.
- When a new booking lands, Carly can message the attendee a confirmation, add prep notes to the event, and drop a heads-up in Slack.
- When someone cancels, Carly can offer the freed slot to the next person on your waitlist and update your team automatically.
- Every morning, Carly can pull the day’s Cal.com bookings, gather context on each attendee, and email you a brief before your first call.
- No-code setup. There’s nothing to configure by hand — Carly interviews you about the workflow you want and builds it.
- Actually sends — Carly composes and sends real email through Gmail and Outlook, not just drafts.
- Connects to anything — 200+ native integrations, plus any tool with an API via your own key. Carly reaches Cal.com through your own Cal.com API key (paste it on the integrations page).
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited.
Claude vs Carly
| Claude + Cal.com | Carly | |
|---|---|---|
| Read/search Cal.com | Yes (34 MCP tools) | Yes (via your API key) |
| Act in a live session | Yes | Yes |
| Acts on triggers/schedules | No | Yes |
| Acts the moment a booking lands | No | Yes |
| Sends email | No (drafts only) | Yes — Gmail + Outlook |
| Reacts to new bookings/cancellations | No | Yes |
| Setup | Add custom connector | Interview, no code |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude is the best way to ask your Cal.com anything on demand; Carly is the way to make Cal.com work happen while you’re nowhere near it.
Frequently Asked Questions
Does Claude work with Cal.com?
Yes. Cal.com ships an official MCP server at https://mcp.cal.com/mcp. Add it in Claude as a custom connector, complete the OAuth prompt, and Claude can manage bookings, event types, and availability through 34 tools.
Is there an official Cal.com MCP server?
Yes — it’s the calcom/cal-mcp repo, hosted at mcp.cal.com with OAuth 2.1, and you can also run it locally with npx @calcom/cal-mcp using a Cal.com API key. That’s the recommended route over any third-party server.
Can claude.ai on the web access Cal.com?
Yes, if your plan supports custom connectors. The hosted mcp.cal.com server uses Streamable HTTP, so Claude web can reach it directly — no local install needed. The local npx route, by contrast, only works on the machine running it.
Can Claude book Cal.com meetings automatically?
Only when you ask, or when a scheduled task goes and looks. Claude has no way to fire on a new booking or a cancellation as it happens — for automatic, event-driven Cal.com actions you need something like Carly.
More: Claude connectors explained · Claude vs Carly · Claude + Calendly · Cal.com alternatives · Cal.com vs Calendly
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
