Zenoti

com.jamesrosingmdPublished by jamesrosingmd.comv1.1.0Updated Oct 25, 2026

MCP server for Zenoti spa/wellness/medspa — guests, appointments, bookings, invoices

Overview

AI-generated 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.
Before you install
The API key in ZENOTI_API_KEY grants access to practice data and should be kept secret. Many tools change real records: creating and updating guests, booking, cancelling, rescheduling, check-in and no-show, closing invoices, emailing guests and submitting feedback. Payment tools record cash payments and charge cards on file, moving real money. Guest personal data and appointment details are sent to the Zenoti API. The README also advertises a separate paid hosted service.

Installation

In SourceWeft

  1. Open Zenoti in the dashboard and add it to a workspace.
  2. 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

bash
npm install -g zenoti-mcp-server

Or run from source:

bash
git clone https://github.com/tacit-code/zenoti-mcp-server.gitcd zenoti-mcp-servernpm installnpm run build

Configuration

VariableRequiredDescription
ZENOTI_API_KEYyesAPI key from Zenoti Admin → Settings → Apps (create a backend app)
ZENOTI_API_URLnoBase URL, default https://api.zenoti.com (with or without /v1)
ZENOTI_CENTER_IDrecommendedDefault center GUID; tools accept center_id to override per call

Claude Desktop / Claude Code config:

json
{  "mcpServers": {    "zenoti": {      "command": "npx",      "args": ["-y", "zenoti-mcp-server"],      "env": {        "ZENOTI_API_KEY": "your_api_key",        "ZENOTI_CENTER_ID": "your_center_guid"      }    }  }}

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

ToolPurpose
zenoti-centers-listList organization centers (find center GUIDs)
zenoti-services-listServices of a center (compact by default, verbose for raw)
zenoti-services-getFull service details
zenoti-therapists-listTherapists of a center, optionally filtered to a service
zenoti-employee-schedulesWho is on shift for a date range (date-scoped staffing)

Guests

ToolPurpose
zenoti-guests-searchSearch by name/email/phone/code/tags (≥1 criterion required)
zenoti-guests-createCreate a guest profile
zenoti-guests-getGuest details by GUID
zenoti-guests-updateUpdate fields — does a safe read-merge-write (Zenoti replaces the whole object on update)
zenoti-guests-appointmentsAppointment history for a guest
zenoti-guests-notes-list / zenoti-guests-notes-addGuest notes and profile alerts
zenoti-guests-membershipsGuest's memberships (status, credits, dues)
zenoti-guests-packagesGuest's packages/series with remaining redemptions

Appointments

ToolPurpose
zenoti-appointments-listCenter appointments for a date range (compact by default)
zenoti-appointments-getAppointment details (appointment_id)
zenoti-appointments-checkin / zenoti-appointments-undo-checkinCheck-in state (appointment_group_id)
zenoti-appointments-noshowMark no-show (appointment_group_id)
zenoti-appointments-progressStart/open/complete service (appointment_id)
zenoti-appointments-cancelCancel a booking (by invoice_id)
zenoti-appointments-rescheduleStart a reschedule (creates a booking draft tied to the invoice)

Booking flow

  1. zenoti-availability-slots — creates a booking draft for guest+service+date and returns booking_id plus open slots
  2. zenoti-booking-reserve — hold a chosen slot (holds are short-lived)
  3. zenoti-booking-confirm — finalize; the response includes the invoice

Invoices

ToolPurpose
zenoti-invoices-getInvoice with line items, payments, and optional dues/fees
zenoti-invoices-pay-customRecord a cash/custom payment (financial action)
zenoti-invoices-pay-cardCharge the guest's card on file (financial action)
zenoti-invoices-closeClose a fully-paid invoice
zenoti-invoices-emailEmail the receipt/invoice to the guest
zenoti-invoices-confirm-visitConfirm (or undo-confirm) the visit — a scheduling status, despite living on the invoice

Reports

ToolPurpose
zenoti-reports-salesWhat was sold over a date range
zenoti-reports-collectionsMoney received over a date range

Forms & feedback

ToolPurpose
zenoti-forms-list / zenoti-forms-getForms and submitted form data of an appointment
zenoti-guest-forms-listForms on a guest profile
zenoti-feedback-submitInsert externally collected guest feedback

Zenoti API gotchas this server handles

  • Three identifiers in one workflow. Check-in/no-show/feedback take appointment_group_id; details/progress/forms take appointment_id; cancel and payments take invoice_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 PUT would erase fields.
  • Rate limit is 60 calls/minute (org-wide). The HTTP layer honors Retry-After on 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

bash
npm run dev        # run from source (tsx)npm test           # unit + end-to-end tests (mock Zenoti API; no real credentials needed)npm run typecheck  # tsc --noEmitnpm run build      # emit dist/

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

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  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