
Zenoti
com.jamesrosingmdPublished by jamesrosingmd.comv1.1.0Updated Oct 25, 2026
MCP server for Zenoti spa/wellness/medspa — guests, appointments, bookings, invoices
Overview
Local MCP server for the Zenoti spa and medspa platform, letting an assistant look up guests, appointments, services and invoices and perform bookings and front
- What you can do
- Look up centers, services, therapists and employee schedules, and search, create, read or update guest profiles with notes, memberships and packages. List and inspect appointments, check guests in or out, mark no-shows, progress, cancel or reschedule bookings. Run the booking flow: create a draft, reserve a slot and confirm it, returning the invoice. Read invoices and record cash or card payments, close invoices, email receipts and confirm visits. Pull sales and collections reports and read or submit forms and guest feedback.
- When to use it
- Useful when an assistant should help run front-desk work for a Zenoti practice: answering questions about guests, schedules and invoices, or carrying out bookings, check-ins and payments through the Zenoti API.
- Requirements
- Runs locally as a Node.js npm package (zenoti-mcp-server) over stdio, desktop client only. Needs a Zenoti API key in ZENOTI_API_KEY from a backend app created in Zenoti Admin. ZENOTI_API_URL is optional (defaults to the Zenoti API) and ZENOTI_CENTER_ID is recommended as a default center. Network access to the Zenoti API is required.
Installation
In SourceWeft
- Open Zenoti in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Zenoti MCP Server
A Model Context Protocol (MCP) server for the Zenoti spa/wellness/medspa management platform. Exposes appointments, guests, service booking, invoices, catalog, and forms as tools an AI agent can call.
Hosted version available
Do not want to manage credentials, hosting, and updates yourself? DOCK is the managed version of this server: encrypted per-practice auth, audit logs, draft-first write actions, and a workflow library. Founding practices lock lifetime pricing: Front Desk $49/mo (Zenoti), Billing Desk $99/mo (Tebra, BAA included), Full Practice $129/mo (both). https://dockhq.vercel.app
Installation
Or run from source:
Configuration
Claude Desktop / Claude Code config:
The server starts even without credentials and returns a readable configuration error on each tool call, so a misconfigured client shows the problem instead of crash-looping.
Tools
Catalog
Guests
Appointments
Booking flow
zenoti-availability-slots— creates a booking draft for guest+service+date and returnsbooking_idplus open slotszenoti-booking-reserve— hold a chosen slot (holds are short-lived)zenoti-booking-confirm— finalize; the response includes the invoice
Invoices
Reports
Forms & feedback
Zenoti API gotchas this server handles
- Three identifiers in one workflow. Check-in/no-show/feedback take
appointment_group_id; details/progress/forms takeappointment_id; cancel and payments takeinvoice_id. Tool schemas name the exact one required. - Guest updates replace the whole object. The update tool fetches the current profile and merges your changes; a naive partial
PUTwould erase fields. - Rate limit is 60 calls/minute (org-wide). The HTTP layer honors
Retry-Afteron 429. Reads also retry on 5xx/network failures/timeouts; writes retry only on 429 (a rate-limit rejection was never processed, so retrying can't duplicate a booking — any other write failure surfaces immediately). - Pagination caps at
size=100; larger values are rejected by Zenoti with a 422. - Webhooks have no subscription API — they are configured in the Zenoti web UI (Admin → Webhooks) and require the Zenoti API package. This server intentionally has no webhook tool.
- Undocumented numeric enums. Gender and appointment-progress codes aren't in Zenoti's public docs; the mappings used here are documented in the tool descriptions and can be overridden (
progress_code).
Development
The e2e suite spawns the real server over stdio via the MCP SDK client and asserts every tool's method, path, query, and body against Zenoti's documented endpoints.
License
MIT
Source: README.md at commit e66d943
Tools
0Version history
1- v1.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts