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

# Heidi API and MCP server: Let your AI agent finish the notes after clinic.

> Heidi documents an API for partners: EHRs, practice systems and telehealth platforms, with access through the Heidi team. Heidi Connectors point the other way, at an MCP server your own EMR or PMS runs. No Heidi MCP server and no official ChatGPT or Claude connector was found.

Heidi's API is for partners such as EHRs and telehealth platforms, and Heidi runs no MCP server for ChatGPT or Claude (checked 16 Nov 2026). Cotlet runs a hosted Heidi MCP server with 7 tools that your agent uses in your own Heidi account. Every change to a note, letter or code waits for your OK.

- Free 7-day trial, no card
- Unofficial, not affiliated with Heidi
- Page: https://cotlet.dev/integrations/heidi-api-mcp-server

> Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Heidi. Heidi is a trademark of its owner. If Heidi's own integrations cover what you need, use them first.

## What can your AI agent do in Heidi?

- Go through today's sessions and notes
- Write a session up as a SOAP note
- Draft a referral letter or certificate
- Add ICD-10 and SNOMED codes before claims
- Ask Heidi Evidence a clinical question
- Keep snippets and terms consistent

## Does Heidi have an MCP server or an API?

- The Heidi developer documentation offers the Heidi API and Heidi Connectors, and says to contact the team for help.
- Heidi integrates with EMRs and practice systems such as Epic, Oracle Cerner, Cliniko and Halaxy.
- Heidi Desktop adds Dictate, which types into any app on your computer; it is outside the web account Cotlet works in.

| What you need | Heidi API | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No MCP server found | Copy and paste | Hosted MCP server |
| Start today with your own login | Partners, by contact | Your login | Your login, once |
| Notes, letters and billing codes | Endpoints not verified | One session at a time | 7 tools, writes after your OK |
| Run from n8n or a script | Inside a partner product | Manual only | REST, same key |

Checked 16 Nov 2026. Sources: [Heidi developer documentation](https://www.heidihealth.com/developers), [Heidi integrations](https://www.heidihealth.com/en-ie/integrations), [Heidi on the App Store](https://apps.apple.com/us/app/heidi-ai-care-partner/id6504471106), [Heidi Dictate](https://www.heidihealth.com/product/dictate), [Heidi customisation](https://www.heidihealth.com/product/customisation), [Heidi documents from one consultation](https://www.heidihealth.com/product/work-smart), [Heidi Coding](https://www.heidihealth.com/product/coding), [Heidi SOAP notes](https://www.heidihealth.com/solutions/soap-notes-software)

## How does the Heidi MCP server work?

1. **Sign in to Heidi.** Once, in a browser we host for you.
2. **Connect your AI agent.** One address in its settings.
3. **Hand it the write-ups.** Notes, letters and codes, each for your review.

Your agent works in your own signed-in Cloud Browser. Every note edit, document and code waits for your OK.

## How to connect Heidi to your AI agent

1. **Sign in to Heidi in a Cloud Browser.** Open scribe.heidihealth.com in your Cotlet Cloud Browser and sign in with your own Heidi account, by email, Google or Apple.
2. **Add the Cotlet address.** Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
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.

Heidi uses the shared address `https://cotlet.dev/mcp/v1` with every other app you turn on, so one connector covers them all. Turned Heidi on after connecting? Refresh the connector and the 7 Heidi 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: heidi_read
```

## All 7 Heidi MCP tools

One tool per Heidi workflow. The agent works with sessions Heidi has already captured; recording a consultation stays with you.

### Clinical notes

Start here: the session list is how the other tools find a note. Reading runs at once; edits and new SOAP notes wait for your OK.

- **Read clinical notes** (`get_clinical_notes`, read): List your Heidi sessions for a day, or read the note Heidi Scribe made from one.
- **Generate SOAP notes** (`generate_soap_note`, write, asks first): Have Heidi write the note of a session in the SOAP format.
- **Edit clinical notes** (`edit_clinical_note`, write, asks first): Change the text of one section of a Heidi note.

### Documents and billing codes

Letters and certificates from one consultation, and the ICD-10 or SNOMED codes for the note. Documents stay in Heidi as drafts; the agent never sends them.

- **Generate consult documents** (`generate_consult_documents`, write, asks first): Create a referral letter, medical certificate or other document from one consultation.
- **Add billing codes** (`add_billing_codes`, write, asks first): Read Heidi's ICD-10 and SNOMED code suggestions for a note, then add, confirm or replace codes.

### Evidence and customisation

Heidi Evidence answers with citations. Snippets and preferred terms shape every note you write next.

- **Search clinical evidence** (`search_clinical_evidence`, read): Ask Heidi Evidence a clinical question and get a summary with its citations.
- **Customise note templates** (`customise_note_templates`, write, asks first): List or add Heidi snippets and preferred terms, or replace a term across your notes.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/heidi-api-mcp-server#tools

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

- **What we store.** Your signed-in Heidi browser profile, AES-256-GCM encrypted, in Finland. Never your password.
- **What your agent gets.** The 7 Heidi tools. The session cookie stays in the Cloud Browser.
- **What the session sees.** The sessions, notes and documents your own Heidi account can open, and nothing more.
- **What no tool touches.** Recording consultations, your EMR connection, Heidi team members and your Heidi plan.
- **If Heidi signs you out.** You sign in again yourself, in the same Cloud Browser.
- **How to cut access.** Turn Heidi off for agents, reset the browser, or sign out of Heidi everywhere.

Cotlet never sees or stores your password: you sign in to Heidi yourself, by email, Google or Apple, and the agent only uses the session that sign-in leaves behind. Clinical notes hold patient health information. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)).

## Approvals, undo and mistakes

1. **Find the session.** get_clinical_notes lists the day.
2. **Ask Heidi for codes.** add_billing_codes with `suggest` only reads.
3. **Show you the codes.** Code, label and billable flag.
4. **Add after your OK.** add_billing_codes saves the ones you approve.

| Action | How to put it right |
|---|---|
| Note section edit | Call edit_clinical_note again with the earlier text |
| Billing code | Replace it with add_billing_codes, or remove it in the note |
| Snippet or preferred term | Change it back with customise_note_templates |
| Referral letter or certificate | A draft in Heidi until you send it: edit or delete it there |

All 5 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 2 read tools, notes and Heidi Evidence, run at once. AI-generated notes are drafts for the clinician to review, in Heidi and here.

MCP call:

```
{
  "name": "add_billing_codes",
  "arguments": {
    "session": "Knee pain review, 09:10",
    "action": "add",
    "codes": [
      {
        "system": "ICD-10",
        "code": "M25.561"
      }
    ]
  }
}
```

REST:

```
curl -X POST https://cotlet.dev/api/v1/heidi/billing-codes \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"session":"Knee pain review, 09:10","action":"add","codes":[{"system":"ICD-10","code":"M25.561"}]}'
```

Response:

```
{
  "session": "Knee pain review, 09:10",
  "codes": [
    {
      "system": "ICD-10",
      "code": "M25.561",
      "label": "Pain in right knee",
      "billable": true
    }
  ],
  "saved": true
}
```

The example adds one ICD-10 code, M25.561, to the knee pain review after you approved it. A script or n8n flow can make the same call over REST at `/api/v1/heidi` with the same key and price, in JSON. Failed calls are free.

## How much does the Heidi MCP server cost?

**About $29 a month** for one clinician over 20 clinic days, 5,000 credits. Your Heidi plan stays as it is.

| Job | Calls | Credits |
|---|---|---|
| Read the day's sessions and notes | 2 × 20 | 400 |
| SOAP notes for new patients | 5 × 20 | 1,000 |
| Edits to Plan sections | 2 × 20 | 400 |
| Referral letters and certificates | 2 × 20 | 400 |
| Billing codes on the day's notes | 5 × 20 | 1,000 |
| Heidi Evidence questions | 1 × 20 | 200 |
| Snippets and preferred terms | 10 × 1 | 100 |
| Cloud Browser, 30 days |  | 1,500 |
| Total | 350 calls | 5,000 |

The smallest pack, 5,000 credits for $29, covers this month. A clinic with several clinicians uses more calls.

- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Your Heidi plan and features apply as they are

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

## Heidi MCP server: other ways to connect

| Option | What it does | Where it stops |
|---|---|---|
| Heidi API | Scribe features inside a partner EHR or telehealth product. | For partners, through the Heidi team; you build and host the integration. |
| Heidi Connectors | Your EMR or PMS exposes an MCP server and Heidi works inside it. | Heidi calls your system; ChatGPT or Claude cannot call Heidi this way. |
| EMR integrations | Heidi connects to systems such as Epic, Oracle Cerner, Cliniko and Halaxy. | Links Heidi to your patient record, not a route for an AI agent. |
| By hand | Open each session in Heidi and work through it. | One session at a time, only while you are at the desk. |

If you build a clinical product and Heidi accepts you as a partner, its API is the vendor's own route. Cotlet fits a clinician or clinic that wants ChatGPT, Claude or a script working in its own Heidi account today, with nothing to host.

## Who runs Cotlet

Cotlet is built by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), working since 2019 and led by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Heidi tools go to contact@cotlet.dev.

## Heidi MCP server: questions

### How do I get access?

Sign up free at https://cotlet.dev/signup?app=heidi, turn on Heidi under Integrations in the console and sign in at https://scribe.heidihealth.com/ in your Cloud Browser. Then connect your AI agent and ask it about today's sessions. The trial needs no card.

### Does Heidi have an API?

Heidi's API is for partners: its developer documentation describes integrations for EHRs, practice systems and telehealth platforms, with access through the Heidi team (checked 16 Nov 2026). Heidi Connectors let your own EMR or PMS run a small MCP server for Heidi; no Heidi MCP server or official ChatGPT or Claude connector was found. Cotlet does not use that API: it works in your own signed-in Heidi account.

### How is this different from Heidi Connectors?

Heidi Connectors work the other way: your EMR or practice system exposes a small MCP server and Heidi works inside it. Cotlet lets ChatGPT, Claude or a script work inside your Heidi account.

### Can the agent record a consultation?

No. Recording stays with you in Heidi, on your own device. The agent works with sessions and notes that are already in your Heidi account.

### Is the MCP server different from the REST API?

Only in how it is called. Both carry the same 7 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.

### Is Cotlet affiliated with Heidi?

No. Cotlet is independent and not affiliated with Heidi or Heidi Health.

---

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.
