Connect Acuity Scheduling to Claude Code

Let Claude book, reschedule, and cancel appointments in Acuity Scheduling. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Acuity Scheduling to Claude Code?

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

claude mcp add --transport http acuity 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 Acuity Scheduling once connected?

Full read-write Acuity Scheduling access lets Claude book an appointment on the right appointment type, reschedule or cancel an existing one, block off time, and update intake details, once you approve. The back-and-forth that used to mean opening the Acuity dashboard happens where the schedule already lives.

Book an appointment on a specific appointment type with the right client and time
Reschedule an existing appointment to a new slot, keeping the client and intake details intact
Cancel an appointment and notify the client after you approve
Block off time on the calendar to protect focus or travel
Update an existing appointment's notes or intake form details after you approve
Find every appointment 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 Acuity Scheduling 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 Acuity Scheduling API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Acuity Scheduling 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 Acuity Scheduling 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 Acuity Scheduling 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 Acuity Scheduling 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 Acuity Scheduling'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 Acuity Scheduling?

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

More on the Acuity Scheduling connector

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