Connect Calendly to Claude Code

Let Claude create event types and booking links in Calendly. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Calendly to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Calendly, you add a Calendly MCP server: a small hosted service that exposes Calendly'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 Calendly account. No API keys pasted into config files.

claude mcp add --transport http calendly 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 Calendly once connected?

Full read-write Calendly access lets Claude create and adjust event types, generate single-use scheduling links for a specific invitee, surface the reschedule link or cancel a meeting, and pull the right availability into a reply. The coordination that used to mean clicking through the dashboard happens where you are already working.

Create a new event type with the duration and availability you specify
Generate a single-use scheduling link to send to a specific invitee
Cancel a scheduled event after you confirm
Surface the reschedule link for an existing booking to send to the invitee
Look up your upcoming events and surface conflicts or gaps
Pull current availability into a draft email or message

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 Calendly 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 Calendly API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Calendly 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 Calendly 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 Calendly 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 Calendly 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 Calendly'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 Calendly?

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 Calendly account it signs in with. Revoking access is one click in Calendly.

More on the Calendly connector

Calendly connector for claude.ai Cal.com + 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