Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Zenoti to Claude Code

Make Claude book services and manage guests in Zenoti. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Zenoti to Claude Code?

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

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

Full read-write means Claude can find a guest, check open slots, and book the service in one conversation. It can pull a center's appointment list for the day, freeze or unfreeze a membership when a guest asks, and prepare gift card sales, all with your approval on every change.

  • Search a guest by name or phone and pull their full appointment history
  • Check available slots and create a service booking at a center, after you approve
  • List a center's appointments for today and flag gaps or double-booked providers
  • Freeze or unfreeze a guest's membership, after you approve
  • Prepare a gift card sale with a custom amount for your review
  • Look up an employee's schedule and blockout times before proposing a booking

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

More on the Zenoti connector

Zenoti connector for claude.aiMindbody + Claude CodeVagaro + Claude CodeWellnessLiving + 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