Zanda API and MCP server Let your AI agent keep the practice diary full.

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.

  • Free 7-day trial, no card
  • Unofficial, not affiliated with Zanda
Zanda logo Zanda Cloud Browser

13 tools Read and write

Practice admin

What can your AI agent do in Zanda? The front desk work of an allied health practice.

  • Offer freed slots to the waitlist

  • Chase intake forms before first visits

  • Count attendance per practitioner

  • Tell clients about a closure

  • Merge duplicate client profiles

  • Flag referrals about to expire

No API docs, no MCP

Does Zanda have an MCP server or an API? The official Zanda routes, checked 14 November 2026.

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.

  • Zanda's own integrations: Stripe payments, Xero exports, Physitrack, Google, Apple and Outlook calendars, Mailchimp list exports and Zoom telehealth.
  • Zanda has its own AI features, BizzyAI and an AI Scribe, inside Zanda.
  • Reports export to CSV, PDF or Excel from Zanda itself.
Zanda's own routes and Cotlet compared
What you need Zanda integrationsReport exportsCotlet
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

Set up once

How does the Zanda MCP server work? The Zanda MCP server by Cotlet: your agent works in your own Zanda account.

  1. 1Log in to Zanda

    Once, in a browser we host for you.

  2. 2Connect your AI agent

    One address in its settings.

  3. 3Hand it the front desk

    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

Any MCP client

How to connect Zanda to your AI agent

  1. 1

    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.

  2. 2

    Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.

  3. 3

    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.

ChatGPT
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Claude
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
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
Codex
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: view_reports
4 read, 9 write

All 13 Zanda MCP tools

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.

Calendar, bookings and waitlist4

Client, group and personal appointments, and the waitlist that fills cancellations.

  • view_calendar Read the Zanda calendar for a day or week, by practitioner or location. read

    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

    Parameters

    Parameters: view_calendar
    NameTypeDescription
    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.

    Example response

    {
      "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"
        }
      ]
    }
  • manage_appointments Book a client, group or personal appointment, move one, or cancel it. writeAsks first

    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

    Parameters

    Parameters: manage_appointments
    NameTypeDescription
    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.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "action": "book",
      "kind": "client",
      "client": "Example Client C",
      "service": "Initial consultation",
      "practitioner": "Practitioner B",
      "start": "2026-11-20T14:00",
      "saved": true
    }
  • manage_waitlist Read the waitlist, add a client to it, or offer a freed slot to someone on it. writeAsks first

    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

    Parameters

    Parameters: manage_waitlist
    NameTypeDescription
    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.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "waitlist": [
        {
          "client": "Example Client D",
          "service": "Follow-up session",
          "practitioner": "Practitioner A",
          "added": "2026-11-11"
        }
      ]
    }

Clients and tasks3

Contact, insurance and referral details, merges and tasks. No clinical notes.

  • manage_clients Find a client, read their details and appointment history, or add or update a client. writeAsks first

    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

    Parameters

    Parameters: manage_clients
    NameTypeDescription
    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.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "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
      }
    }
  • merge_clients Merge two profiles of the same client into one. writeAsks first

    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

    Parameters

    Parameters: merge_clients
    NameTypeDescription
    keep string required string The client profile to keep.
    merge string required string The duplicate profile to merge into it.

    Example input

    {
      "keep": "Example Client E (born 1990-07-15)",
      "merge": "Example Client E (duplicate)"
    }

    Example response

    {
      "kept": "Example Client E (born 1990-07-15)",
      "merged": "Example Client E (duplicate)",
      "moved": {
        "appointments": 2,
        "invoices": 2
      },
      "saved": true
    }
  • manage_tasks List your Zanda tasks, add one or mark it done. writeAsks first

    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

    Parameters

    Parameters: manage_tasks
    NameTypeDescription
    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.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "tasks": [
        {
          "task": "Request updated referral",
          "client": "Example Client C",
          "due_date": "2026-11-21",
          "done": false
        }
      ]
    }

Forms and messages3

Intake and consent forms through the client portal, reminders, one-off and bulk messages.

  • send_forms See which forms a client has outstanding or completed, or send a form through the client portal. writeAsks first

    `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

    Parameters

    Parameters: send_forms
    NameTypeDescription
    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.

    Example input

    {
      "action": "action",
      "client": "client"
    }

    Example response

    {
      "client": "Example Client C",
      "forms": [
        {
          "form": "New client intake",
          "status": "completed",
          "date": "2026-11-12"
        },
        {
          "form": "Telehealth consent",
          "status": "outstanding"
        }
      ]
    }
  • configure_reminders Read or change your automatic SMS and email appointment reminders. writeAsks first

    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

    Parameters

    Parameters: configure_reminders
    NameTypeDescription
    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.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "sms_reminders": 2,
      "email": true,
      "saved": true
    }
  • send_message Send an SMS or email to one client or a bulk message to many, from your Zanda templates or your own text. writeAsks first

    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

    Parameters

    Parameters: send_message
    NameTypeDescription
    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.

    Example input

    {
      "channel": "channel",
      "to": "to"
    }

    Example response

    {
      "channel": "sms",
      "to": "Clients booked 22 to 24 December",
      "recipients": 31,
      "sent": true
    }

Reports and procedures3

Practice reports and their exports, and the policies in your Practice Operations Manual.

  • view_reports Read a Zanda report such as Appointments, Sales, Activity, Invoices & Payments or Client Retention. read

    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

    Parameters

    Parameters: view_reports
    NameTypeDescription
    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.

    Example input

    {
      "report": "report"
    }

    Example response

    {
      "report": "appointments",
      "from": "2026-11-01",
      "to": "2026-11-14",
      "by_status": {
        "attended": 142,
        "cancelled": 11,
        "did_not_attend": 6
      }
    }
  • export_report Export a Zanda report to CSV, PDF or Excel. read

    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

    Parameters

    Parameters: export_report
    NameTypeDescription
    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.

    Example input

    {
      "report": "report",
      "format": "format"
    }

    Example response

    {
      "report": "invoices_and_payments",
      "format": "csv",
      "file": "invoices-and-payments-2026-11.csv",
      "url": "https://files.example.com/export.csv"
    }
  • manage_procedures List the policies and procedures in your Practice Operations Manual, or add one from a template. writeAsks first

    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

    Parameters

    Parameters: manage_procedures
    NameTypeDescription
    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.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "title": "Handling third-party requests for client records",
      "section": "Confidentiality & privacy",
      "saved": true
    }
Encrypted, revocable

Who can see my Zanda session, and how do I revoke it?

  • What we store

    Your signed-in Zanda browser profile, AES-256-GCM encrypted, in Finland. Never your password.

  • What your agent gets

    The 13 Zanda tools. The session cookie stays in the Cloud Browser.

  • What the session sees

    What your Zanda role allows. A practitioner's login gives the agent that practitioner's view.

  • What no tool touches

    Clinical notes, treatment plans, files, invoices, insurance claims, payments and your Zanda settings and roles.

  • If Zanda signs you out

    You log in again yourself, in the same Cloud Browser, including Zanda's two-factor step.

  • How to cut access

    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).

We keep it working

What happens when Zanda changes? The tools work through the same Zanda pages your front desk uses.

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.

9 tools ask first

Approvals, undo and mistakes No client is messaged, booked or merged until you say so.

  1. 01 Find the duplicates manage_clients lists both profiles.
  2. 02 Pick the one to keep The profile with more history.
  3. 03 Show you the merge Both profiles side by side, before anything moves.
  4. 04 Merge after your OK Zanda moves appointments, invoices and notes.
Fixing a Zanda write that went wrong
ActionHow to put it right
Appointment moved or flagged wronglyCall manage_appointments again with the earlier values
Reminder settings, client details, tasksCall the same tool again with the earlier values
SMS, email or form already sentWith the client already: send a correction
Profiles mergedA 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.

MCP call
{
  "name": "merge_clients",
  "arguments": {
    "keep": "Example Client E (born 1990-07-15)",
    "merge": "Example Client E (duplicate)"
  }
}
REST
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)"}'
Response
{
  "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.

Pay per call

How much does the Zanda MCP server cost?

About $21 a monthfor a practice with three practitioners, 3,620 credits. Your Zanda plan stays as it is.

Illustrative month, our assumption: successful calls for this workload
JobCallsCredits
Morning cancellations and waitlist offers2 × 22440
Intake forms for tomorrow's new clients2 × 22440
Bookings and moves1 × 60600
Client detail lookups and updates1 × 40400
Weekly attendance report and export2 × 480
Weekly referral expiry tasks3 × 4120
Closure and availability messages2 × 240
Cloud Browser, 30 days1,500
Total212 calls3,620

The smallest pack, 5,000 credits for $29, covers this month. Reminders Zanda sends by itself need no call.

  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Your Zanda plan applies as it is

Credit packs are one-time purchases, not a subscription. The month above is an example built from our own assumptions, not measured customer usage.

Cotlet credit packs: price, credits and calls at 10 credits each
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.

Other options

Zanda MCP server: other ways to connect What each route does for an allied health practice, and where it stops.

Other ways to work with Zanda, checked 14 Nov 2026
OptionWhat it doesWhere it stops
Xero integrationExports payments, invoices and payees to Xero.Accounting only.
Mailchimp integrationExports your client list for email campaigns.A list export; no bookings, forms or waitlist.
Calendar syncAppointments to Google, Apple and Outlook calendars.Read in a calendar; nothing an agent can act on.
BizzyAI and AI ScribeZanda'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.

EU company, since 2019

Who runs Cotlet A company you can look up.

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.

Zanda MCP server: questions

How do I get access?

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.

Does Zanda have an API?

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.

Does the agent read clinical notes?

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.

Is Cotlet covered by Zanda's privacy setup?

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.

Which Zanda login should I use?

The one whose work the agent should do. Zanda gives each user role-based access, and the agent sees exactly what that role sees.

Is the MCP server different from the REST API?

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.

Is Cotlet affiliated with Zanda?

No. Cotlet is independent and not affiliated with Zanda.

Hand your Zanda front desk to your agent.

Free 7-day trial with 2,000 credits, no card needed.