Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect SavvyCal to Claude Code

Make Claude create scheduling links and cancel bookings in SavvyCal. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect SavvyCal to Claude Code?

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

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

Full read-write SavvyCal access lets Claude create a scheduling link with the duration and availability you set, generate a single-use link for a specific recipient, list your upcoming meetings, and cancel a booking once you approve. The coordination that used to mean opening the SavvyCal dashboard happens where you already work.

  • Create a scheduling link with the duration, availability, and meeting type you specify
  • Generate a single-use scheduling link to send to a specific recipient
  • Create a recurring scheduling link reused across multiple bookings
  • List your upcoming meetings and surface conflicts or open gaps
  • Cancel a scheduled meeting and notify attendees after you approve
  • Read availability so a link reflects the windows you actually keep open

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 SavvyCal 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 SavvyCal API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when SavvyCal 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 SavvyCal 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 SavvyCal 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 SavvyCal 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 SavvyCal'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 SavvyCal?
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 SavvyCal account it signs in with. Revoking access is one click in SavvyCal.

More on the SavvyCal connector

SavvyCal connector for claude.aiMicrosoft Bookings + Claude CodeChili Piper + Claude CodeYouCanBook.me + 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 connectorTalk to us