Zanda MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Zanda MCP Server find a cancellation tomorrow and offer it to the waitlist"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Zanda MCP server through Cotlet.dev
Connect Zanda to ChatGPT, Claude, Codex and Claude Code through Cotlet.dev. Ask your agent to handle the front desk in your own signed-in practice account: calendars, waitlists, intake forms, client messages and reports.
Unofficial integration, not affiliated with Zanda. Cotlet.dev hosts the connection through your Cloud Browser. This repository includes an optional Python stdio MCP bridge.
Connect your practice
Open https://my.zandahealth.com/ or your region's Zanda address in your Cotlet.dev Cloud Browser and sign in yourself. Enable Zanda for agents.
Connect your agent below. Refresh the connector if you enabled Zanda after connecting.
ChatGPT
Open Settings > Apps & Connectors > Create. Set the MCP server URL to https://cotlet.dev/mcp/v1/connect and choose OAuth.
Claude
Open Settings > Connectors > Add custom connector and enter https://cotlet.dev/mcp/v1/connect.
Codex
Create a Cotlet.dev API key in the console and set COTLET_API_KEY in your environment:
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"Claude Code
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"Related MCP server: bookings-mcp
Practice workflows
Examples from the Zanda integration reference:
Find a cancellation and offer the slot to a client on the waitlist after approval.
Check outstanding intake forms before a first visit, then approve sending a form.
Count attendance per practitioner and export the report.
Prepare a closure message, review recipients and approve sending it.
Compare duplicate client profiles before approving a merge.
Find referrals nearing expiry and create follow-up tasks.
The live reference describes 13 hosted capabilities, grouped under zanda_read and zanda_write:
Capability | Access | Purpose |
| read | Calendar by day or week, practitioner or location |
| write | Book, move or cancel client, group or personal appointments |
| write | List entries, add a client or offer a freed slot |
| read | Get the client portal booking URL |
| write | Find clients, read details, create or update records |
| write | Merge a duplicate into the profile you keep |
| write | List, create or complete practice tasks |
| write | Read form status or send a form through the portal |
| write | Read or change automatic appointment reminders |
| write | Send SMS or email to one client or a group |
| read | Read practice reports and filters |
| read | Export to CSV, PDF or Excel |
| write | List or create Practice Operations Manual procedures |
Four capabilities are read and nine are write. Where supported, list, get and status actions only read. Writes ask for confirmation by default, configurable per tool. Review recipients, appointment details and both profiles before approving changes. A merge moves appointments, invoices and notes between profiles; these tools do not open clinical notes, treatment plans or files. Form status returns names, dates and calculated totals rather than answers.
Bookings and moves can trigger Zanda's automatic confirmations. Reminder changes affect upcoming appointments. Review message text before sending; an already-sent message needs a correction sent to the client. The practice's existing Zanda role controls what its login can see.
Optional local stdio bridge
Python 3.10 or newer, with no runtime dependencies. Clone this repository and configure a client supporting stdio:
{"mcpServers":{"zanda":{"command":"python3","args":["/absolute/path/to/zanda-mcp/zanda_agent.py"],"env":{"COTLET_API_KEY":"your-cotlet-key"}}}}The bridge exposes seven browser helpers: zanda_guide, zanda_status, zanda_open, zanda_read, zanda_click, zanda_type and zanda_close. These forward to shared Cotlet.dev browser tools and are separate from the 13 hosted workflow capabilities above. Call the guide first and close the browser when finished. Discovery works without a key; tool execution requires your Cotlet.dev key and connected practice account.
python3 zanda_agent.py connect
python3 zanda_agent.py guide
python3 zanda_agent.py status
python3 zanda_agent.py serveYou can build the included Dockerfile and pass COTLET_API_KEY through the environment.
Reference and access
Licensed under Elastic License 2.0. See LICENSE.
Available Tools
7 toolszanda_clickB
Click a numbered element on the current Zanda page.
Inputs: element (required).
zanda_closeA
Close the Zanda browser session when the work is done, so credits stop running.
Inputs: no named parameters.
zanda_guideA
How to work in Zanda (practice calendars, waitlists, forms, messages and reports): its screens and the sign-in link. Call this first.
Inputs: task.
zanda_openA
Open a Zanda page in your signed-in Cloud Browser (default https://my.zandahealth.com) to work with practice calendars, waitlists, forms, messages and reports.
Inputs: url.
zanda_readA
Read the current Zanda page: its text and numbered buttons, links and fields.
Inputs: element.
zanda_statusA
Check that your Cotlet.dev account and Zanda are ready: account, credits and Zanda connection.
Inputs: no named parameters.
zanda_typeC
Type text into a numbered field on the current Zanda page.
Inputs: text (required), element (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool maps to a distinct step in a browser-automation workflow: guide, status check, open, read, click, type, and close. There is no meaningful overlap between reading a page, clicking an element, typing into a field, or opening/closing the session.
All tools use the same predictable zanda_ prefix followed by a short lowercase verb or noun. The convention is consistent throughout and each name clearly reflects its action.
Seven tools is well-scoped for a browser-automation wrapper: one orientation tool, one readiness check, and five lifecycle operations for opening, inspecting, interacting with, and closing a session. No tool feels redundant.
The surface covers the core lifecycle: check status, open a page, read it, click/type, and close. Minor gaps exist for richer browser interactions such as selecting dropdown options, scrolling, waiting for page loads, or pressing keys, though many of these can be approximated through click and type.
Maintenance
Related MCP Connectors
Work with roles, tasks and delegated agent work within current workspace permissions. Setup: In a remote MCP client that supports Streamable HTTP and OAuth, add https://platform.samuelz.com/api/v1/mcp/operator?toolset=agent. Sign in to Samuelz and select your authorized workspace. An active workspace membership and the relevant module permissions are required. Review the requested permissions before authorizing. Existing approval requirements continue to apply.
Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close.
Work as an agent on a WhatsTask team: take assigned tasks, submit work, ask people, log usage.
Jane App MCP server for ChatGPT, Claude and any AI agent: list appointments, read the Wait List, book a Wait List client, email an intake form, read accounts receivable, send a Pay Balance email, list unscheduled patients and add a return visit reminder in your own Jane App account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Jane App yourself; Cotlet does not store your password and you need no Jane App API key. About the official Jane App API: Jane has an API, but only for approved Technology Partners (checked 27 Oct 2026). Jane says it is not launching an open, public API and that clinics cannot build their own integrations. Setup and FAQ: https://cotlet.dev/integrations/jane-app-api-mcp-server
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables an agent to observe and operate desktop apps and browsers through an accessibility-tree-first view, with clicking, typing, scrolling, dragging and waiting tools. Screenshot handling, coordinate mapping and fail-closed safety rules (risk confirmation, deny-listed apps, stale-observation refusal) are enforced inside the server.9Apache 2.0
- AlicenseAqualityCmaintenanceEnables AI agents to browse customers, bookings, and availability while any booking creation or cancellation stays gated behind a human-approved, single-use token cryptographically bound to the exact arguments. Runs over stdio or Streamable HTTP and enforces the read/write separation in host code with a full audit trail.7MIT
- AlicenseAqualityBmaintenanceEnables AI agents to read and change jobs, job status, customers, quotes with line items, invoices, quote and invoice email, payments, and Scheduler bookings in an account by reusing the user's own signed-in Chrome session, with no official API keys needed. Ships read-only hints and confirmation prompts for tools that reach other people, and can be run over stdio or streamable HTTP.222143 PyPI6Elastic 2.0
- AlicenseNot gradedqualityCmaintenanceEnables a desktop AI agent to read from and write to a single Halaxy practice account, turning intake material like referral PDFs, emails and form photos into patient, referrer and referral records, and checking availability and booking appointments. Every write is gated by a prepare/approve/commit flow with duplicate checks, masking and read-only mode.1MIT