[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Jane App API and MCP server: Let your AI agent run your clinic's front desk. > Jane has no public API and no MCP server (checked 27 Oct 2026). Its Jane Developer Platform is for approved Technology Partners, and Jane says clinics cannot build their own integrations. Cotlet runs 14 Jane tools hosted, over MCP for agents and REST for scripts. Read Jane appointments, wait lists and administrative reports through MCP or REST. Connect your staff account to an agent or a private reporting script. [MCP setup](https://cotlet.dev/integrations/jane-app-api-mcp-server.md#connect) [REST API guide](https://cotlet.dev/integrations/jane-app-api-mcp-server.md#rest-api) - Free 7-day trial, no card - Unofficial, not affiliated with Jane - Page: https://cotlet.dev/integrations/jane-app-api-mcp-server ## What can you automate in Jane App? - Fill cancellations from the Wait List - Resend unfinished intake forms - Send Pay Balance emails - Recall patients who have not rebooked - Notify the Wait List about an opening - Report new and returning patients ## Does Jane App have an MCP server or an API? - The partner API reads patients, appointments, treatments and staff and writes chart records. It has no endpoints for the Wait List, intake forms, invoices or reports. - Jane's partner rules say "Posting directly into Jane's calendars is not supported", and Jane is "not looking to work with AI scheduling" tools for now. - Zapier and n8n have no Jane app (both pages answer 404). Jane announced a partner marketplace without a date. | What you need | Partner API | By hand in Jane | Cotlet | |---|---|---|---| | Read the Schedule and patients | Approved partners only | Yes | Yes | | Book from the Wait List | No | Yes, slot by slot | Yes, after your OK | | Resend intake forms | No | Yes, patient by patient | Yes, after your OK | | Balances and Pay Balance emails | No | Yes | Yes, after your OK | | Runs while the front desk is busy | Your own code, if approved | No | Yes, also on a schedule | Checked 27 Oct 2026. Sources: [Jane blog: Jane Integrations, our program and how to work with us](https://jane.app/blog/jane-integrations-our-program-our-partners-and-how-to-work-with-us), [Jane Developer Platform API Quick Start Guide](https://developers.jane.app/), [Jane Developer Platform API reference index](https://developers.jane.app/llms.txt), [Jane Guide: Using Wait List Notifications](https://jane.app/guide/using-wait-list-notifications) ## How does Cotlet connect to Jane App? 1. **Sign in to Jane App.** Use your own account in its Cotlet Cloud Browser. 2. **Choose MCP or REST.** Connect your agent or create a Cotlet API key. 3. **Run your workflow.** Ask your agent or send an HTTP request. We never keep your Jane password or ask you to turn off two-factor, and nothing reaches a patient until you approve it. ## Connect Jane App to your agent or workflow Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide. 1. **Enable Jane for agents.** Sign up, sign in to your clinic at yourclinic.janeapp.com/admin in its Cloud Browser, then press Enable for agents. 2. **Paste the Cotlet address.** Add https://cotlet.dev/mcp/v1 as an MCP server or connector in your agent. 3. **Approve the connection.** Chat apps ask you to sign in to Cotlet. Editors, n8n and scripts use an API key from the console. One address serves every app you enable, Jane included. Enable Jane after connecting and the connector needs a refresh before its tools appear. 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" ``` ChatGPT: ``` Settings > Apps & Connectors > Create MCP server URL: https://cotlet.dev/mcp/v1/connect Authentication: OAuth ``` 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, Tool: jane_app_read ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: jane_app_write ``` ## How to use the Jane App REST API ### Create your Cotlet API key Sign in to Jane App in its Cotlet Cloud Browser and enable the app for agents. Use your clinic staff login; clinic-wide reports require Full Access or the relevant Administrative / All Billing permissions. Create a Cotlet API key with access to Jane App and its read operations. Store it as `COTLET_API_KEY` in your environment or automation platform's credential store. ### Make your first Jane App API request cURL: list_appointments: ``` curl "https://cotlet.dev/api/v1/jane-app/appointments?from=2026-11-02&to=2026-11-02" \ -H "Authorization: Bearer $COTLET_API_KEY" ``` ### Read appointment reports and follow the cursor A successful REST call puts the tool output in `result`. This illustrative response excerpt omits call IDs, messages and credit details. Illustrative response excerpt: ``` { "status": "success", "app": "jane-app", "tool": "list_appointments", "result": { "appointments": [ { "appointment_id": "apt_48230", "patient_id": "pt_10988", "patient": "Sam Rivera", "staff_member": "Dana Lee", "treatment": "Physiotherapy Initial 60 min", "start": "2026-11-02T13:00:00-07:00", "state": "Booked Online" } ], "next_cursor": null } } ``` Replace the dates with your reporting day and read `result.appointments`. Pass `result.next_cursor` unchanged as `cursor` until null, preserving dates, state, staff and location filters. There is no page-size input. The report includes cancellations and reschedules in its default state selection; compare time, practitioner and state as well as IDs. Patient profiles omit chart notes, and intake-form reads return status rather than answers. Accounts Receivable does not subtract account credit; preserve that distinction in administrative reports. ### Jane App workflows for agents and automations | Tool | Connect through | Example workflow | |---|---|---| | n8n | HTTP Request | Combine appointments and intake-form statuses into a private administrative preparation list without reading answers. | | Make | HTTP > Make a request | Read wait lists and appointments to prepare a staff-reviewed slot shortlist without booking or contacting patients. | | Python or Node.js | REST API | Read Accounts Receivable into an administrative aging report that retains the account-credit distinction. | Send `Authorization: Bearer ` in request headers. You configure the schedule, destination and record comparisons. Cotlet reads Jane App; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template. Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports. The [API and MCP reference](https://cotlet.dev/integrations/jane-app-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals. ## Jane App API endpoints and MCP tools ### Schedule and Wait List The Wait List comes longest-waiting first. Front Desk and Limited access see only their own Wait List; Wait List Notifications need the Thrive or Legacy plan. - **List appointments** (`list_appointments`, read): Appointments in a date range with patient, practitioner, treatment and state. - **List Wait List** (`list_wait_list`, read): Clients on each practitioner's Wait List with requested treatment, availability and notes. - **Add to Wait List** (`add_to_wait_list`, write): Put a patient on a practitioner's Wait List with a treatment and availability. - **Book appointment** (`book_appointment`, write, asks first): Book a patient into an open slot, from the Wait List or directly. - **Send Wait List notification** (`send_wait_list_notification`, write, asks first): Notify the eligible Wait List clients about an opening at once. ### Patients and intake forms Profiles, form status and contact details. Chart notes and form answers are never returned. - **Search patients** (`search_patients`, read): Patients matching a name, email or phone number. - **Get patient** (`get_patient`, read): One patient profile: contact details, upcoming appointments, last visit and balance owing. - **List intake forms** (`list_intake_forms`, read): A patient's online intake forms with their status: not started, in progress or completed. - **Email intake form** (`email_intake_form`, write, asks first): Email a patient an intake form from their profile. ### Billing, recall and reports Clinic-wide reports need Full Access or Administrative / All Billing access. Pay Balance emails need Jane Payments, automatic reminder emails the Thrive plan. - **Get accounts receivable** (`get_accounts_receivable`, read): Patients and insurers with money owing, with the amount by age. - **Send Pay Balance email** (`send_pay_balance_email`, write, asks first): Email a patient a request to pay their balance online. - **List unscheduled patients** (`list_unscheduled_patients`, read): Patients with no future booking, with their last visit and return visit reminder status. - **Add return visit reminder** (`add_return_visit_reminder`, write, asks first): Add a return visit reminder to a patient's last appointment. - **Get retention report** (`get_retention_report`, read): New patients, returning patients, total visits and percent returning per practitioner. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/jane-app-api-mcp-server#tools ## Who can see my Jane App session, and how do I revoke it? - **What we store.** Your signed-in Jane staff profile, encrypted with AES-256-GCM, in Finland. Not the password. - **What your agent gets.** The 14 Jane tools. Never the cookie or your password. - **What the session sees.** What your staff access sees in Jane: Schedule, patients, billing, reports. - **What no tool touches.** Chart notes, form answers, settings, payouts, password and two-factor. - **If Jane asks to verify.** A two-factor code goes to you. You type it in; we never ask you to turn it off. - **How to cut access.** Disable for agents, reset the browser, or sign out of Jane. Jane holds patient health information. Jane signs a HIPAA Business Associate Agreement with clinics on request (Jane terms, checked 27 Oct 2026); that agreement is between your clinic and Jane, and Cotlet is not part of it. Check an agent on patient records with whoever handles privacy at your clinic first. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). There is no SOC 2 report or third-party pentest yet. ## Is it against Jane's terms? Account safety > harvest, scrape or otherwise collect (including through use of any robot, spider, crawler, program, or other technology or device) information about others from our Services, including names and email addresses, without Jane's prior written consent > > [Jane Terms of Use, Acceptable Use](https://jane.app/terms) An agent reading patient lists in your account can fall under that clause. Jane's integrations post of 1 Apr 2026 adds that using an unofficial connector "is a decision each clinic makes, but we do not recommend this approach", and warns about tools that share credentials or need two-factor off. We found no public case of a Jane account closed for using a third-party tool (checked 27 Oct 2026). Read the terms and decide for your clinic. How we keep your account looking like you: - Your own Jane staff login, signed in by you - Two-factor stays on; the code goes to you - A real Chrome in one Cloud Browser with its own IP and cookies - Bookings and patient emails go out only after your OK - If Jane objects, we pause the Jane tools for everyone within 24 h > Give the agent the staff access the job needs. Front Desk access keeps it to one practitioner's Wait List and reports. ## What happens when Jane App changes? - **12 h** between tests of the Jane reads - **$0** for a call to a Jane tool paused for repair Jane ships product updates every month and posts them on its blog. When a screen moves or a report gains a column, the fix happens on our side and your prompts keep working. [status.cotlet.dev](https://status.cotlet.dev) watches the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads the Schedule.** Cancelled and no-show slots for today and tomorrow. 2. **Matches the Wait List.** Clients whose days and times fit, longest wait first. 3. **Waits for your OK.** Each booking shows up in your Cotlet console first. 4. **Reports the day.** Who was booked, who stays on the Wait List. | Action | Undo | |---|---| | Add to the Wait List | Remove the entry in Jane; nobody is told | | Book an appointment | Cancel it in Jane, but the patient already has the confirmation email | | Wait List notification | Cannot be unsent; release the spot in Jane | | Intake form or Pay Balance email | Cannot be unsent | | Return visit reminder | Delete it before the reminder date | 5 of 14 tools ask first: book_appointment, send_wait_list_notification, email_intake_form, send_pay_balance_email, add_return_visit_reminder. Each reaches a patient or money. Reads and new Wait List entries reach nobody, so they run at once. Switch the wait off per tool for a scheduled run. > A booking pulls in the intake forms set for that treatment, so a new patient gets them with the confirmation. MCP call: ``` { "name": "book_appointment", "arguments": { "patient_id": "pt_11873", "staff_member": "Dana Lee", "treatment": "Physiotherapy Follow-up 30 min", "start": "2026-10-28T10:00:00-07:00", "wait_list_entry_id": "wl_2207" } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/jane-app/patients/pt_11873/appointments \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"staff_member":"Dana Lee","treatment":"Physiotherapy Follow-up 30 min","start":"2026-10-28T10:00:00-07:00","wait_list_entry_id":"wl_2207"}' ``` Tool output: ``` { "appointment_id": "apt_48251", "patient_id": "pt_11873", "staff_member": "Dana Lee", "treatment": "Physiotherapy Follow-up 30 min", "start": "2026-10-28T10:00:00-07:00", "state": "Booked", "removed_from_wait_list": true } ``` Scripts and cron jobs reach the same tools over REST at `/api/v1/jane-app`, with the same key and price. A slot that overlaps another appointment fails, and a failed call costs nothing. The tools table lists the REST path of each tool. ## How much does the Jane App MCP server cost? **About $32 a month** for daily Wait List and intake form passes plus weekly billing and recall in a three-practitioner clinic, 5,560 credits. Your Jane plan stays as it is. | Job | Calls | Credits | |---|---|---| | Fill cancellations from the Wait List | 3 × 22 | 660 | | Resend unfinished intake forms | 11 × 22 | 2,420 | | Pay Balance emails, weekly | 11 × 4 | 440 | | Recall unscheduled patients, weekly | 13 × 4 | 520 | | Retention report, monthly | 2 × 1 | 20 | | Cloud Browser, 30 days | | 1,500 | | Total | | 5,560 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - Works on the Jane plan you already pay for The month is our example: 22 working days, eight intake form checks a day, five overdue balances and six recalls a week. Jane publishes no clinic size. Jane's own plans are CAD $59, $79 and $99 a month on jane.app/pricing (checked 27 Oct 2026), billed by Jane. Dollars at the $29 pack rate. ## Jane App MCP server on GitHub or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | [pp-janeapp in printing-press-library](https://github.com/mvanhorn/printing-press-library) | CLI, skill and MCP server for Jane's patient online booking: your own appointments and open times across clinics. Apache-2.0. | Patient side only, signed in with a patient password. No Schedule, Wait List or billing. Jane folder last changed 17 Aug 2026. | | [JaneApp Reports Scraper](https://github.com/tomjwc/JaneApp---Reports-Scraper) | A script that starts every report download for a signed-in Jane user. | 1 star, last push 29 Aug 2026. Downloads only, no MCP server. | | [Integuru](https://www.integuru.com/platform-api-guides/jane-app) | Builds an unofficial HTTP API for Jane App from the web app's own requests, for software companies. | You buy and run an integration project; no ready MCP server for a clinic. | | Jane partner program | The official API for approved Technology Partners, through an intake form. | Not for single clinics or single-use tools, and no calendar writes. | For a clinic owner who wants an agent on the front desk work, the realistic choice today is Cotlet or doing it by hand. The GitHub tools above serve patients or download reports. Cotlet works in your own staff session, hosts the server and repairs it when Jane changes. ## Who runs Cotlet Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), working since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Jane tools go to contact@cotlet.dev. ## Jane App API and MCP: questions ### Can I use the Jane App API without an AI agent? Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST. ### How do I get access? Create a free account at https://cotlet.dev, open Jane App under Integrations in the console and sign in to your clinic in its Cloud Browser. The trial starts with your first app, no card asked. ### Is this an official Jane integration? No. Jane lists its approved partners on its Integrations page and says it does not recommend unofficial connectors, because it cannot verify them (checked 27 Oct 2026). Cotlet does not ask you to share your password or turn off two-factor authentication: you sign in to Jane yourself in your own Cloud Browser. Whether to connect an unofficial tool is the clinic's decision. ### Does Jane's Business Associate Agreement cover Cotlet? No. Jane's terms say Jane signs its standard BAA with a subscriber subject to HIPAA on request, and that agreement is between you and Jane. Before an agent reads patient records through any outside tool, check it with whoever handles privacy compliance at your clinic. ### Which Jane plan and access do I need? The tools work on the plan you have, with two plan limits from Jane: Wait List Notifications and automatic return visit reminder emails are Thrive and Legacy features. Your staff access counts too: clinic-wide reports and every practitioner's Wait List need Full Access or Administrative / All Billing access, and Pay Balance emails need Jane Payments. ### Does Jane have webhooks? Only for approved partners: the Jane Developer Platform registers webhook subscriptions per partner (checked 27 Oct 2026). Run your agent on a schedule instead, for example a morning list_appointments and list_wait_list pass. ### Does it work on the Balance plan? Yes, within Jane's own limits: Balance has one practitioner profile and 20 appointments a month. Wait List Notifications and automatic return visit reminder emails need Thrive. ### Can the agent read chart notes? No. No tool returns chart notes or intake form answers. get_patient returns contact details, appointments, reminders and the balance owing. ### Is the MCP server different from the REST API? Only the way in. Both have the same 14 tools, inputs and answers, one API key and one price. Agents use MCP; scripts, cron jobs and HTTP steps use REST. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.