Connect Setmore to Claude Code

Make Claude book and reschedule appointments in Setmore. From the terminal, inside the sessions where you already work.

How do you connect Setmore to Claude Code?

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

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

Full read-write Setmore access lets Claude book a new appointment into an open slot, reschedule or cancel an existing one, add or update customer details, and assign the right staff member, all from where you already work. The booking changes that used to mean switching to the Setmore dashboard happen in the conversation.

Book a new appointment into an open slot for the right service and staff member
Reschedule an existing appointment to a different time after you confirm
Cancel an appointment and free the slot back up
Create or update a customer record with contact details and notes
List a staff member's upcoming appointments so you can plan the day
Look up open slots for a service and propose times to offer a client

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

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

More on the Setmore connector

Setmore connector for claude.ai Microsoft Bookings + Claude Code SavvyCal + Claude Code Chili Piper + 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