Local services & SaaS
Jane App
Schedule, Wait List, intake forms, balances and reports in your Jane clinic.
14 endpoints
Zanda publishes no public API documentation and no MCP server (checked 14 Nov 2026). Cotlet runs a hosted Zanda MCP server with 13 tools that ChatGPT and Claude use in your own practice account. No tool opens clinical notes, and messages to clients wait for your OK.
13 tools Read and write
Zanda publishes no public API documentation. Its integrations page announces a Zanda API for tailored integrations but gives no documentation or access route, and no Zanda MCP server or official ChatGPT or Claude connector was found.
| What you need | Zanda integrations | Report exports | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No | Upload files by hand | Hosted MCP server |
| Waitlists, forms and messages | Not covered | Read only | 13 tools, writes after your OK |
| Payments to accounting, lists to email | Xero and Mailchimp | Files to import | Reports and exports |
| Run from n8n or a script | Fixed pairs of apps | Parse the files yourself | REST, same key |
Checked 14 Nov 2026. Sources: Zanda integrations · Zanda all features · Zanda support · Zanda appointment scheduling · Zanda client management · Zanda online booking and client portal · Zanda online forms · Zanda SMS and email communication · Zanda reporting · Zanda Practice Operations Manual
Once, in a browser we host for you.
One address in its settings.
Find a freed slot, then approve the SMS.
Cotlet never sees or stores your password. No tool opens clinical notes, and messages to clients wait for your OK. Who can see your session
Log in to Zanda in a Cloud Browser. Open my.zandahealth.com, or your region's Zanda address, in your Cotlet Cloud Browser and log in with your own Zanda login.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
Zanda shares the address https://cotlet.dev/mcp/v1 with every other app you turn on, so one connector covers them all. Turned Zanda on after connecting? Refresh the connector and the 13 Zanda tools appear.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: view_reports One tool per practice workflow on Zanda's feature pages. Tools with an `action` read on `list`, `get` and `status`; the other actions write and ask first.
Client, group and personal appointments, and the waitlist that fills cancellations.
Returns appointments with client, service, practitioner, time, status and appointment flag, plus group appointments and personal appointments. It returns no clinical notes. Nothing changes, so it runs without asking.
MCP callzanda_read → view_calendar
REST endpointGET https://cotlet.dev/api/v1/zanda/calendars/view
| Name | Type | Description |
|---|---|---|
| date string | string | ISO date. Defaults to today. |
| range string | string | `day` or `week`. Defaults to `day`. |
| practitioner string | string | Optional practitioner. |
| location string | string | Optional location. |
{
"date": "2026-11-18",
"appointments": [
{
"time": "09:00",
"practitioner": "Practitioner A",
"client": "Example Client A",
"service": "Initial consultation",
"status": "confirmed",
"flag": "New client"
},
{
"time": "10:00",
"practitioner": "Practitioner A",
"client": "Example Client B",
"service": "Follow-up session",
"status": "unconfirmed"
}
]
} Zanda sends its automatic confirmations to the client and practitioner by SMS or email, so a booking or move reaches the client. A personal appointment blocks the practitioner's time without a client. Each change waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callzanda_write → manage_appointments
REST endpointPOST https://cotlet.dev/api/v1/zanda/appointments/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `book`, `move`, `cancel`. All three write. |
| kind string | string | For `book`: `client`, `group` or `personal`. Defaults to `client`. |
| appointment string | string | For `move` and `cancel`: the appointment, by client and time. |
| client string | string | For a client appointment: client name from manage_clients. |
| service string | string | Service. |
| practitioner string | string | Practitioner. |
| start string | string | For `book` and `move`: ISO date and time. |
| max_participants number | number | For a group appointment or class: the participant limit. |
| flag string | string | Optional appointment flag, as set up in your Zanda account. |
{
"action": "action"
} {
"action": "book",
"kind": "client",
"client": "Example Client C",
"service": "Initial consultation",
"practitioner": "Practitioner B",
"start": "2026-11-20T14:00",
"saved": true
} After a cancellation Zanda suggests waitlist clients and prompts an SMS. `offer` sends that SMS for the slot you name, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callzanda_write → manage_waitlist
REST endpointPOST https://cotlet.dev/api/v1/zanda/waitlist/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add`, `offer`. `list` only read. |
| client string | string | For `add` and `offer`: client name. |
| service string | string | For `add`: the service they are waiting for. |
| practitioner string | string | For `add`: optional practitioner. |
| slot string | string | For `offer`: the freed slot, ISO date and time. |
{
"action": "action"
} {
"waitlist": [
{
"client": "Example Client D",
"service": "Follow-up session",
"practitioner": "Practitioner A",
"added": "2026-11-11"
}
]
} Clients open the link, choose a location, practitioner, service and time, and book within your availability. Read only.
MCP callzanda_read → get_booking_link
REST endpointGET https://cotlet.dev/api/v1/zanda/booking-link
No parameters.
{
"booking_url": "https://booking.example.com/example-physio-clinic"
} Contact, insurance and referral details, merges and tasks. No clinical notes.
Returns basic details, contacts, insurance, referral details and appointment history. It does not open clinical notes, treatment plans or files. `create` and `update` change the client record, so they wait for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callzanda_write → manage_clients
REST endpointPOST https://cotlet.dev/api/v1/zanda/clients/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`. `list` and `get` only read. |
| client string | string | Client name, for `get` and `update`, or a search for `list`. |
| fields object | object | For `create` and `update`: name, address, date of birth, contact details, contacts (such as next of kin), insurance and referral details. |
{
"action": "action"
} {
"client": "Example Client C",
"date_of_birth": "1988-04-02",
"phone": "+61 400 000 000",
"referral": {
"type": "GP referral",
"valid_until": "2027-05-01"
},
"appointments": {
"past": 3,
"upcoming": 1
}
} Zanda moves the duplicate's appointments, invoices and notes to the profile you keep. The agent shows both profiles first and merges after your OK. By default you confirm each call; you can switch that off for this tool.
MCP callzanda_write → merge_clients
REST endpointPOST https://cotlet.dev/api/v1/zanda/clients/merge
| Name | Type | Description |
|---|---|---|
| keep string required | string | The client profile to keep. |
| merge string required | string | The duplicate profile to merge into it. |
{
"keep": "Example Client E (born 1990-07-15)",
"merge": "Example Client E (duplicate)"
} {
"kept": "Example Client E (born 1990-07-15)",
"merged": "Example Client E (duplicate)",
"moved": {
"appointments": 2,
"invoices": 2
},
"saved": true
} Tasks sit with Zanda's notes and task management. The agent writes a task as you give it and adds nothing clinical. By default you confirm each call; you can switch that off for this tool.
MCP callzanda_write → manage_tasks
REST endpointPOST https://cotlet.dev/api/v1/zanda/tasks/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `complete`. `list` only read. |
| task string | string | For `create` and `complete`: the task. |
| client string | string | Optional client the task is about. |
| due_date string | string | ISO date. |
{
"action": "action"
} {
"tasks": [
{
"task": "Request updated referral",
"client": "Example Client C",
"due_date": "2026-11-21",
"done": false
}
]
} Intake and consent forms through the client portal, reminders, one-off and bulk messages.
`status` returns form names, dates and, for scored forms, the total Zanda calculates; it does not return answers. A sent form reaches the client, so `send` waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callzanda_write → send_forms
REST endpointPOST https://cotlet.dev/api/v1/zanda/forms
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `status`, `send`. `status` only read. |
| client string required | string | Client name. |
| form string | string | For `send`: an intake, consent or scored form from your Zanda account. |
{
"action": "action",
"client": "client"
} {
"client": "Example Client C",
"forms": [
{
"form": "New client intake",
"status": "completed",
"date": "2026-11-12"
},
{
"form": "Telehealth consent",
"status": "outstanding"
}
]
} Zanda sends up to three SMS reminders per appointment, in the client's time zone, and clients can confirm by replying. A change affects every upcoming appointment, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callzanda_write → configure_reminders
REST endpointPOST https://cotlet.dev/api/v1/zanda/reminders/configure
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `set`. `get` only read. |
| sms_reminders number | number | For `set`: SMS reminders per appointment, up to three. |
| email boolean | boolean | For `set`: email reminders on or off. |
{
"action": "action"
} {
"sms_reminders": 2,
"email": true,
"saved": true
} Zanda's bulk messages suit holiday closures, practitioner availability and new services. The agent shows recipients and text before anything is sent. By default you confirm each call; you can switch that off for this tool.
MCP callzanda_write → send_message
REST endpointPOST https://cotlet.dev/api/v1/zanda/messages
| Name | Type | Description |
|---|---|---|
| channel string required | string | `sms` or `email`. |
| to string required | string | One client, or a group such as clients with appointments in a date range. |
| template string | string | A Zanda SMS or email template. |
| message string | string | Your own text instead of a template. |
{
"channel": "channel",
"to": "to"
} {
"channel": "sms",
"to": "Clients booked 22 to 24 December",
"recipients": 31,
"sent": true
} Practice reports and their exports, and the policies in your Practice Operations Manual.
Zanda has more than 27 reports, filtered by role, practitioner, date, service or status. This returns the rows of one report as your login sees them. Nothing changes.
MCP callzanda_read → view_reports
REST endpointGET https://cotlet.dev/api/v1/zanda/reports/view
| Name | Type | Description |
|---|---|---|
| report string required | string | `appointments`, `sales`, `activity`, `invoices_and_payments`, `client_retention`, `appointment_count`, `referrals` or `demographics`. |
| from string | string | ISO date. |
| to string | string | ISO date. |
| filter object | object | Optional: practitioner, service, location or appointment status. |
{
"report": "report"
} {
"report": "appointments",
"from": "2026-11-01",
"to": "2026-11-14",
"by_status": {
"attended": 142,
"cancelled": 11,
"did_not_attend": 6
}
} Returns a download link to the file Zanda produces. Nothing in Zanda changes, so it runs without asking.
MCP callzanda_read → export_report
REST endpointGET https://cotlet.dev/api/v1/zanda/reports/export
| Name | Type | Description |
|---|---|---|
| report string required | string | Same names as view_reports. |
| format string required | string | `csv`, `pdf` or `excel`. |
| from string | string | ISO date. |
| to string | string | ISO date. |
{
"report": "report",
"format": "format"
} {
"report": "invoices_and_payments",
"format": "csv",
"file": "invoices-and-payments-2026-11.csv",
"url": "https://files.example.com/export.csv"
} Zanda's Practice Operations Manual includes over 100 policies and procedures you configure. Your team works from them, so a new one waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callzanda_write → manage_procedures
REST endpointPOST https://cotlet.dev/api/v1/zanda/procedures/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` only read. |
| title string | string | For `create`: procedure title. |
| template string | string | For `create`: one of the manual's templates to start from. |
| text string | string | For `create`: your own text, as you give it. |
{
"action": "action"
} {
"title": "Handling third-party requests for client records",
"section": "Confidentiality & privacy",
"saved": true
} Your signed-in Zanda browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 13 Zanda tools. The session cookie stays in the Cloud Browser.
What your Zanda role allows. A practitioner's login gives the agent that practitioner's view.
Clinical notes, treatment plans, files, invoices, insurance claims, payments and your Zanda settings and roles.
You log in again yourself, in the same Cloud Browser, including Zanda's two-factor step.
Turn Zanda off for agents, reset the browser, or change your Zanda password.
Cotlet never sees or stores your password. Zanda's security and compliance cover data inside Zanda; Cotlet signs no BAA and makes no HIPAA claim, so whether client data may pass through an AI agent is your practice's decision. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Cotlet watches the apps it serves and updates the Zanda server when Zanda changes its pages, so your agent keeps working without a change on your side.
If Zanda opens its own API to your practice and it covers your job, you can use that instead; the Cotlet tools stay the same until you switch.
If Zanda signs you out, one click in the Cotlet console reopens the Cloud Browser so you can log in again.
| Action | How to put it right |
|---|---|
| Appointment moved or flagged wrongly | Call manage_appointments again with the earlier values |
| Reminder settings, client details, tasks | Call the same tool again with the earlier values |
| SMS, email or form already sent | With the client already: send a correction |
| Profiles merged | A merge moves records across: check both profiles before you approve |
All 9 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 4 read tools, the calendar, booking link, reports and exports, run at once.
{
"name": "merge_clients",
"arguments": {
"keep": "Example Client E (born 1990-07-15)",
"merge": "Example Client E (duplicate)"
}
} curl -X POST https://cotlet.dev/api/v1/zanda/clients/merge \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"keep":"Example Client E (born 1990-07-15)","merge":"Example Client E (duplicate)"}' {
"kept": "Example Client E (born 1990-07-15)",
"merged": "Example Client E (duplicate)",
"moved": {
"appointments": 2,
"invoices": 2
},
"saved": true
} The example merges a duplicate profile into the one you keep; Zanda moves its two appointments and two invoices across. A cron job or n8n flow can make the same call over REST at /api/v1/zanda with the same key and price, in JSON. Failed calls are free.
About $21 a monthfor a practice with three practitioners, 3,620 credits. Your Zanda plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| Morning cancellations and waitlist offers | 2 × 22 | 440 |
| Intake forms for tomorrow's new clients | 2 × 22 | 440 |
| Bookings and moves | 1 × 60 | 600 |
| Client detail lookups and updates | 1 × 40 | 400 |
| Weekly attendance report and export | 2 × 4 | 80 |
| Weekly referral expiry tasks | 3 × 4 | 120 |
| Closure and availability messages | 2 × 2 | 40 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 212 calls | 3,620 |
The smallest pack, 5,000 credits for $29, covers this month. Reminders Zanda sends by itself need no call.
Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
| Option | What it does | Where it stops |
|---|---|---|
| Xero integration | Exports payments, invoices and payees to Xero. | Accounting only. |
| Mailchimp integration | Exports your client list for email campaigns. | A list export; no bookings, forms or waitlist. |
| Calendar sync | Appointments to Google, Apple and Outlook calendars. | Read in a calendar; nothing an agent can act on. |
| BizzyAI and AI Scribe | Zanda's own AI features inside Zanda. | Not ChatGPT, Claude or your scripts. |
If your job is accounting or a newsletter list, Zanda's own Xero and Mailchimp integrations are the right route. Cotlet fits when you want ChatGPT, Claude or a script to work the front desk in Zanda from your own login, with nothing to host.
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Zanda tools.
Sign up free at https://cotlet.dev/signup?app=zanda, turn on Zanda under Integrations in the console and log in at https://my.zandahealth.com/ or your region's Zanda address in your Cloud Browser. Then connect your AI agent and ask for today's calendar. The trial needs no card.
Zanda publishes no public API documentation (checked 14 Nov 2026). Its integrations page announces a Zanda API for tailored integrations but gives no documentation or access route, and no Zanda MCP server or official ChatGPT or Claude connector was found. Cotlet does not need one: it works in your own signed-in Zanda account.
No. No tool on this page opens clinical notes, session notes, treatment plans or files. The client tools return contact, insurance, referral and appointment details, and form status without answers.
No. Zanda's security and compliance cover data inside Zanda. Cotlet signs no BAA and makes no HIPAA claim, so whether client data may pass through an AI agent is your practice's decision.
The one whose work the agent should do. Zanda gives each user role-based access, and the agent sees exactly what that role sees.
Only in how it is called. Both carry the same 13 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with Zanda.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy