Skip to content
Custom Connectors

Full read-write Claude connector for Zenoti

Make Claude book services and manage guests in Zenoti

Your front desk lives in Zenoti, and Claude can work there too: finding guests, checking schedules, and booking services on request. Every booking, cancellation, or membership change waits for your approval before it happens.

Zenoti is an enterprise management platform for spas, salons, and medspas, covering appointments, guest profiles, memberships, packages, and point of sale across multi-location brands. Teams want Claude to look up guests, check schedules, book services, and manage memberships without clicking through the Zenoti interface.

What is a Zenoti MCP server?

A Zenoti MCP server is a small hosted service that exposes Zenoti's data and actions to Claude over the Model Context Protocol, so Claude can operate industry-specific platforms inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.

What can Zenoti's current connector do today?

Today, Zenoti does not ship a first-party Claude or MCP connector, so reaching it from Claude means a custom integration against the Zenoti API, and hand-wired access tends to stay read-leaning. A purpose-built Zenoti connector adds scoped write actions like creating service bookings and updating guest records, with approval on anything that touches a schedule or a sale.

What does full read-write Zenoti access unlock?

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

Can Claude look up a guest's history in Zenoti?

Yes, Claude can search guests by name or phone through the Zenoti API and pull their appointment history, membership status, and package balances. That turns questions like 'when was her last facial and what did she book' into a ten-second answer instead of a trip through the Zenoti interface.

Can Claude book an appointment in Zenoti?

Yes, Claude can run the whole flow: find the guest, check open slots for the service and provider, and create the booking. The connector shows you the exact slot, service, and price before anything is confirmed, and the booking only goes through after you approve it in the conversation.

Can Claude manage memberships and gift cards in Zenoti?

Yes, Claude can freeze or unfreeze a guest's membership and prepare gift card sales with custom amounts, both supported directly by the Zenoti API. These are gated actions: Claude stages the change, you review it, and it only executes on your approval, so nothing touches a guest's billing without a human sign-off.

How a Zenoti connector works

We build a small MCP server that talks to the Zenoti API using an API key generated inside your own account, so the connector never exceeds the permissions your account already has. Read tools like guest search and schedule lookups are separated from write tools like creating bookings. Anything that changes a schedule, alters a membership, or prepares a sale is gated behind your approval. You connect it to Claude once and every conversation can use it.

Frequently asked questions

Does Zenoti have a Claude or MCP connector?
Not a first-party one. Zenoti publishes a documented REST API at docs.zenoti.com, but there is no official Zenoti connector in the Claude connector directory today. A custom MCP connector closes that gap: it wraps the endpoints your team actually uses, appointments, guests, memberships, and sales, and exposes them to Claude as clean tools with read and write separated and approval required on changes.
Can Claude book appointments in Zenoti?
Yes, with a custom connector. The Zenoti API supports the full booking flow: search the guest, retrieve available slots for a service and provider, and create the service booking. The connector runs each step as a separate tool, shows you exactly what will be booked, and only confirms after you approve. Cancellations and reschedules are gated the same way, so nothing changes on the book without a human decision.
Is it safe to give Claude access to Zenoti guest data?
The connector authenticates with an API key from your own Zenoti account, so it inherits your permissions and nothing more. Read tools and write tools are built separately, which means you can deploy a read-only version first if you prefer. Every destructive or guest-facing action, like canceling a booking or changing a membership, requires explicit approval in the conversation before it executes.

Using Claude Code?

The same connector works in the terminal: connect Zenoti to 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.