Zenoti
Let your coding agent read and act on Zenoti guest, appointment, booking, and invoice data for a spa, wellness, or medspa business.
Overview
com.jamesrosingmd/zenoti is a MCP server for the Build phase that connects coding agents to Zenoti guests, appointments, bookings, and invoices.
What is this MCP server?
- Stdio npm package (zenoti-mcp-server v1.0.0) for local Claude Code, Cursor, and Codex MCP configs
- Four required secrets/config: ZENOTI_API_KEY, ZENOTI_API_URL, ZENOTI_CENTER_ID, ZENOTI_ORG_ID
- Surfaces guests, appointments, bookings, and invoices for spa, wellness, and medspa workflows
- Targets operators already on Zenoti Org Settings → API credentials
- MCP integration layer—not a replacement for Zenoti’s native scheduling UI
- Package version 1.0.0, registry npm, identifier zenoti-mcp-server
- Transport type stdio
- 4 required environment variables (1 secret API key)
What problem does it solve?
Spa and medspa operators waste time switching between Zenoti and chat-based assistants when agents cannot call the booking API safely.
Who is it for?
Solo founders or tiny teams already on Zenoti who want agent-driven guest lookup, scheduling context, or invoice questions inside Claude Code or Cursor.
Skip if: Generic SaaS builders with no Zenoti contract, or anyone who only needs marketing site copy without live PMS data.
What do I get? / Deliverables
After you configure API key, URL, center, and org IDs, your agent can query and act on live Zenoti operational data from the IDE.
- Agent-callable access to Zenoti guests, appointments, bookings, and invoices
- Repeatable stdio MCP config you can commit beside other dev tooling
- Foundation for custom medspa ops automations without custom OAuth scaffolding
Recommended MCP Servers
Journey fit
Zenoti wiring belongs in Build because you connect a production booking and billing API into the product or internal ops stack, not in early ideation. Integrations is the canonical shelf for third-party API MCP servers that expose CRUD and operational endpoints to the agent.
How it compares
Zenoti API MCP bridge, not an agent skill or marketplace bundle.
Common Questions / FAQ
Who is com.jamesrosingmd/zenoti for?
It is for Zenoti customers—spa, wellness, and medspa operators—who want MCP-aware agents to work with guests, appointments, bookings, and invoices.
When should I use com.jamesrosingmd/zenoti?
Use it during Build when you are integrating live center data into automations, support bots, or internal tools that must stay in sync with Zenoti.
How do I add com.jamesrosingmd/zenoti to my agent?
Install zenoti-mcp-server from npm, set ZENOTI_API_KEY, ZENOTI_API_URL, ZENOTI_CENTER_ID, and ZENOTI_ORG_ID, then register the stdio server in your Claude Code, Cursor, or Codex MCP config.