[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.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)

# ClinicSense API status Does ClinicSense have an API or MCP server?

> ClinicSense: no API, MCP server, Zapier app or webhooks found; the client list exports from the Clients screen (checked 20 Nov 2026). Cotlet API & MCP access score: 1 out of 5. What exists instead, with sources.

Source: https://cotlet.dev/api-status/clinicsense

ClinicSense: no API, MCP server or webhooks found on clinicsense.com or support.clinicsense.com (checked 20 November 2026), and no ClinicSense app on Zapier, Make or n8n. A practice can export its client list from the Clients screen, all clients or only those seen by one practitioner.

**Cotlet API & MCP access score: 1 out of 5.** A ClinicSense practice can download its client list. No documented way to read or change its schedule, client files or invoices from other software was found.

Checked 20 Nov 2026 ·[How Cotlet scores](#how-cotlet-scores)·[Report an inaccuracy](mailto:contact@cotlet.dev?subject=ClinicSense%20API%20status)

Cotlet publishes this page as an independent assessment. Cotlet is not affiliated with, endorsed by or sponsored by ClinicSense. ClinicSense is a trademark of its owner. If ClinicSense's own tools cover what you need, use them first.

ClinicSense API & MCP report

1/5

Cotlet API & MCP access score 1/10 points

Public API

0/3

MCP server

0/3

Zapier · Make · n8n

0/2

Webhooks

0/1

Data export

1/1

Checked

20 Nov 2026

[Report an inaccuracy](mailto:contact@cotlet.dev?subject=ClinicSense%20API%20status) [How we score](#how-cotlet-scores)

Public API

None

0 of 3

MCP server

None

0 of 3

Zapier · Make · n8n

None

0 of 2

Webhooks

None

0 of 1

Data export

Client list

1 of 1

On this page

1. [01 At a glance](#at-a-glance)
2. [02 Public API](#public-api)
3. [03 MCP server](#mcp-server)
4. [04 Zapier, Make, n8n](#automation)
5. [05 Export](#export)
6. [06 Routes](#routes)
7. [07 How Cotlet scores](#how-cotlet-scores)
8. [08 Sources](#sources)

01 · At a glance

## ClinicSense API & MCP access at a glance

__ClinicSense API & MCP access on 20 Nov 2026 1 of 10 points__
| Check | Points | Finding | Source |
| ------------------------- | ------ | --------------------------------------------------------------------------------------------------------------- | ------------------ |
| Public API for businesses | 0 / 3 | None found on clinicsense.com or support.clinicsense.com | [\[1\]](#source-1) |
| Official MCP server | 0 / 3 | No MCP server found on clinicsense.com or support.clinicsense.com, and no ClinicSense entry in the MCP Registry | [\[2\]](#source-2) |
| Zapier, Make, n8n | 0 / 2 | No ClinicSense app found on Zapier, Make or n8n | [\[3\]](#source-3) |
| Webhooks | 0 / 1 | None found on clinicsense.com or support.clinicsense.com | [\[1\]](#source-1) |
| Data export | 1 / 1 | The client list exports from the Clients screen, all clients or those of one practitioner | [\[4\]](#source-4) |

One more fact that earns no points: ClinicSense's Terms of Service, updated 23 March 2023, say "you may not share your account and log-in information with, or allow access to your account by, any third party," and "you will not permit any third party to have access to the ClinicSense Service using your account" ([ClinicSense Terms of Service](https://clinicsense.com/terms-of-service)).

02 · Public API

## Does ClinicSense have an API?

None found

ClinicSense: no API, developer docs or API keys found on clinicsense.com or support.clinicsense.com on 20 November 2026.

[ Source \[1\] · ClinicSense Help Guides, searched for API, MCP and webhooks, 20 Nov 2026 ](#source-1)

03 · MCP server

## Does ClinicSense have an MCP server?

None found

ClinicSense: no MCP server or ChatGPT or Claude connector found on clinicsense.com or support.clinicsense.com on 20 November 2026, and no ClinicSense entry in the official MCP Registry.

[ Source \[2\] · Official MCP Registry, search for "clinicsense", 20 Nov 2026: no ClinicSense entry ](#source-2)

04 · Zapier, Make, n8n

## Does ClinicSense work with Zapier, Make or n8n?

No app

No ClinicSense app was found on Zapier, Make or n8n on 20 November 2026.

[ Source \[3\] · zapier.com/apps/clinicsense returns 404; no ClinicSense app found on make.com or n8n.io, 20 Nov 2026 ](#source-3)

05 · Export

## Can I export my ClinicSense data?

Client list

ClinicSense's help says: "Go to Clients, then click Export Client List at the bottom left." You choose all clients or only those seen by a specific practitioner, then click Export.

[ Source \[4\] · ClinicSense Help: How to export a list of your clients ](#source-4)

06 · Routes

## How can I connect ClinicSense to ChatGPT or Claude today?

A ClinicSense practice has two routes today, and they do different jobs.

clinicsense.com Your ClinicSense practice account

1. Route 1  
### The ClinicSense app  
Schedule, client files and invoices, handled by hand.

  - Appointments: by hand
  - Client files and invoices: by hand
  - Ask in plain words: no
2. Route 2  
### Client list export  
All clients, or those of one practitioner, downloaded by hand.

  - Appointments: no
  - Client files and invoices: the client list
  - Ask in plain words: no

07 · How Cotlet scores

## How Cotlet scores API & MCP access

Cotlet scores one thing: how easily a business can connect its own software or AI agent to its own account. Five checks give up to 10 points, and the points give the Cotlet API & MCP access score, from 1 to 5.

Points to score

ClinicSense · 1 points
1. 1 0 or 1
2. 2 2 to 4
3. 3 5 or 6
4. 4 7 or 8
5. 5 9 or 10

Where the 10 points come from

1. API 0 of 3
2. MCP 0 of 3
3. Zapier, Make, n8n 0 of 2
4. Webhooks 0 of 1
5. Data export 1 of 1

__How Cotlet scores API & MCP access: the five checks__
| Check | Points | What earns them |
| ------------------------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Official API for the business account | 0 to 3 | 3: public and self-serve, reads and writes. 2: public, but read only or on a higher plan. 1: by partner approval or as a paid add-on. 0: none |
| Official MCP server | 0 to 3 | 3: reads and writes the business account. 2: works on the business account, read only or limited. 1: exists, but not for the business account, such as an app in ChatGPT for clients. 0: none |
| Zapier, Make, n8n | 0 to 2 | 2: an app on two or more of them, with actions. 1: an app on one, or triggers only. 0: none |
| Webhooks | 0 or 1 | 1: documented webhooks for business events |
| Data export | 0 or 1 | 1: an official export, such as CSV, a report download or a data add-on |

__How Cotlet scores API & MCP access: points to score__
| Points | Score |
| ------- | ---------- |
| 9 or 10 | 5 out of 5 |
| 7 or 8 | 4 out of 5 |
| 5 or 6 | 3 out of 5 |
| 2 to 4 | 2 out of 5 |
| 0 or 1 | 1 out of 5 |

Every score rests on the sources listed on the page and carries the date it was checked. A score changes when the facts change. Cotlet sells a cloud browser that connects AI agents to web apps such as ClinicSense, and says so on every page of this catalog.

08 · Sources

## Sources

1. \[1\]  
[ClinicSense Help Guides, searched for API, MCP and webhooks, 20 Nov 2026](https://support.clinicsense.com/hc/en-us)  
support.clinicsense.com Checked 20 Nov 2026
2. \[2\]  
[Official MCP Registry, search for "clinicsense", 20 Nov 2026: no ClinicSense entry](https://registry.modelcontextprotocol.io/v0/servers?search=clinicsense)  
registry.modelcontextprotocol.io Checked 20 Nov 2026
3. \[3\]  
zapier.com/apps/clinicsense returns 404; no ClinicSense app found on make.com or n8n.io, 20 Nov 2026  
zapier.com, make.com, n8n.io Checked 20 Nov 2026
4. \[4\]  
[ClinicSense Help: How to export a list of your clients](https://support.clinicsense.com/hc/en-us/articles/8474117517203-How-to-export-a-list-of-your-clients)  
support.clinicsense.com Checked 20 Nov 2026
5. \[5\]  
[ClinicSense Terms of Service, updated 23 Mar 2023](https://clinicsense.com/terms-of-service)  
clinicsense.com Checked 20 Nov 2026

## Something changed at ClinicSense?

Write to contact@cotlet.dev and we recheck this page.

[Report an inaccuracy](mailto:contact@cotlet.dev?subject=ClinicSense%20API%20status) [All API & MCP access scores](https://cotlet.dev/api-status.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.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.
