Connect Cal.com to Claude Code

Make Claude create, reschedule, and manage bookings in Cal.com. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Cal.com to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Cal.com, you add a Cal.com MCP server: a small hosted service that exposes Cal.com's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Cal.com account. No API keys pasted into config files.

claude mcp add --transport http cal-com https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Cal.com once connected?

Full read-write Cal.com access lets Claude create a booking on the right event type, reschedule or cancel an existing one, add an attendee or guests to a booking, and adjust availability and event-type settings, once you approve. The back-and-forth that used to mean opening the dashboard happens where the schedule already lives.

Create a booking on a specific event type with the right attendees and time
Reschedule an existing booking to a new slot, keeping attendees intact
Cancel a booking and notify attendees after you approve
Update an event type's duration, location, or availability window
Add an attendee or guests to an existing booking
Find every booking matching a query and propose batched changes

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Cal.com access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Cal.com API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Cal.com changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Cal.com connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Cal.com connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Cal.com account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Cal.com's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Cal.com?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Cal.com account it signs in with. Revoking access is one click in Cal.com.

More on the Cal.com connector

Cal.com connector for claude.ai Calendly + Claude Code Acuity Scheduling + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us