# CharmHealth MCP connector

The CharmHealth connector brings appointments, encounters, conditions, care plans, care teams, coverages and diagnostic reports into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, with each person signed in as themselves and every call logged.

Source: https://elaichi.ai/connectors/charmhealth/

## Facts

| | |
| --- | --- |
| Application | CharmHealth |
| Category | Healthcare |
| AI tools | 60 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once CharmHealth is connected

- Show me today's appointments and any open conditions for each patient.
- List care plans updated this week with their care teams.
- Pull the latest diagnostic reports for patients seen yesterday.

## Connect CharmHealth in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick CharmHealth.
2. Optionally set Share with, then press Connect.
3. Supply your own CharmHealth app, then approve. CharmHealth needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which CharmHealth tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## CharmHealth MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## CharmHealth MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## CharmHealth MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## CharmHealth MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## CharmHealth MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect CharmHealth to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a CharmHealth tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with CharmHealth through Elaichi

### Prepare tomorrow's schedule before the doors open

Front desk. Pull tomorrow's appointments, check which patients have recorded allergies or active conditions, and have a short brief ready for each room before the first patient arrives.

### Review a patient's chart before the visit

Clinical. Ask for a patient's conditions, allergy intolerances, current care plan and most recent diagnostic reports in one go, instead of opening each section of CharmHealth by hand.

### Keep care teams and care plans in view

Care coordination. List the care plans updated this week, see who sits on each care team, and spot patients whose plan has not been touched in a while.

### Check coverage before the claim goes out

Billing. Look up a patient's coverages alongside their recent encounters so the billing team can confirm the payer on file before submitting.

### Find the document when an auditor asks

Compliance. Search document references and CCDA documents for a patient, and start or retrieve a bulk export when a records request comes in.

### Confirm allergies and devices at intake

Nursing. Bring up a patient's allergy intolerances and recorded devices at check-in so nothing is missed before medication or a procedure.

## Elaichi vs Zapier MCP vs Composio for CharmHealth

All three can connect CharmHealth to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over CharmHealth tools | Allow or restrict single CharmHealth tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per CharmHealth call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect CharmHealth to Claude?

First connect CharmHealth in Elaichi. CharmHealth asks for an OAuth application registered inside CharmHealth itself, so one administrator creates that application once and pastes its client ID and secret into Elaichi, after which everyone else just signs in to CharmHealth with their own login. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in and CharmHealth is ready.

### Does CharmHealth work with ChatGPT and Cursor as well as Claude?

Yes. Once CharmHealth is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect CharmHealth once and every client sees it.

### What can an AI agent actually do with my CharmHealth data?

An agent can look up and list what is in CharmHealth: appointments, encounters, conditions, allergy intolerances, care plans, care teams, coverages, devices, diagnostic reports, document references and CCDA documents. It can also start, check and remove a bulk export. Ask for something specific, like today's appointments or a patient's current care plan, and it finds the right records; short concrete asks work better than long sentences.

### Does connecting CharmHealth give the AI access to every patient record?

No. Every call into CharmHealth runs as the person who signed in, so the agent sees only the patients, charts and documents that person can already open in CharmHealth. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what CharmHealth itself allows.

### Can my team share one CharmHealth connection?

Yes. One administrator connects CharmHealth and shares the connection with a team, and nobody else ever handles the client ID or secret. Each teammate still signs in to CharmHealth as themselves, so the audit log names the actual person who looked up a chart or started an export.

### Can I stop an agent from deleting or changing things in CharmHealth?

Yes. Most of what this connector does is read records, but actions such as starting or deleting a bulk export in CharmHealth can be restricted per action, for a role or for one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a CharmHealth connection when someone leaves?

Offboarding a person in Elaichi ends their CharmHealth access through every client at once. A connection shared with a team keeps working for everyone else. If you want CharmHealth gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the CharmHealth MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. CharmHealth is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for CharmHealth?

Yes. Both let Claude, ChatGPT or Cursor use CharmHealth. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every CharmHealth call.

### How is Elaichi different from Composio for CharmHealth?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to CharmHealth: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 60 CharmHealth tools

Every tool below is callable through https://api.elaichi.ai/mcp once CharmHealth is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all CharmHealth allergy intolerances** (List). Fetches a bundle of AllergyIntolerance resources based on query parameters. (GET /api/ehr/v2/fhir/AllergyIntolerance). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth allergy intolerance by ID** (Get). Fetches a specific AllergyIntolerance resource. (GET /api/ehr/v2/fhir/AllergyIntolerance/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth appointments** (List). Fetches a bundle of Appointment resources based on query parameters. (GET /api/ehr/v2/fhir/Appointment). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth appointment by ID** (Get). Fetches a specific Appointment resource. (GET /api/ehr/v2/fhir/Appointment/{id}). The id is the FHIR resource id. Required: id.
- **CharmHealth bulk exports start** (Start). Start the bulk export for the given patients (GET /api/ehr/v2/fhir/Group/{group_id}/$export). Needs the backend (system scope) connection. The reply's diagnostics (and its content-location header) give the status URL with the job id (_jobid). Required: group_id.
- **Get single CharmHealth bulk export by ID** (Get). API URL: (GET /api/ehr/v2/fhir/$export-poll-status). The id is the job id (_jobid). 202 with an information OperationOutcome while the export runs; 200 with output file URLs (Binary) when done. Required: id.
- **Delete a CharmHealth bulk export by ID** (Delete). Deletes the Bulk Export Request, that was initiated. (DELETE /api/ehr/v2/fhir/$export-poll-status). The id is the job id (_jobid). Required: id.
- **List all CharmHealth capability statement** (List). Fetches the metadata for all resources (GET /api/ehr/v2/fhir/metadata). Public: no token needed.
- **List all CharmHealth care plans** (List). Fetches a bundle of CarePlan resources based on query parameters. (GET /api/ehr/v2/fhir/CarePlan). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth care plan by ID** (Get). Fetches a specific CarePlan resource. (GET /api/ehr/v2/fhir/CarePlan/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth care teams** (List). Fetches a bundle of CareTeam resources based on query parameters. (GET /api/ehr/v2/fhir/CareTeam). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth care team by ID** (Get). Fetches a specific CareTeam resource. (GET /api/ehr/v2/fhir/CareTeam/{id}). The id is the FHIR resource id. Required: id.
- **Get single CharmHealth ccda document by ID** (Get). Export medical records of a patient in HL7 CCDA format. (GET /api/ehr/v2/fhir/patients/{patient_id}/ccda). The id is the patient id. The reply is the CCDA XML document (returned as text). Sends the connection's API key (api_key header) when set. Required: id.
- **List all CharmHealth conditions** (List). Fetches a bundle of Condition resources based on query parameters. (GET /api/ehr/v2/fhir/Condition). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth condition by ID** (Get). Fetches a specific Condition resource. (GET /api/ehr/v2/fhir/Condition/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth coverages** (List). Fetches a bundle of Coverage resources based on query parameters. (GET /api/ehr/v2/fhir/Coverage). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth coverage by ID** (Get). Fetches a specific Coverage resource. (GET /api/ehr/v2/fhir/Coverage/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth devices** (List). Fetches a bundle of Device resources based on query parameters. (GET /api/ehr/v2/fhir/Device). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth device by ID** (Get). Fetches a specific Device resource (GET /api/ehr/v2/fhir/Device/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth diagnostic reports** (List). Fetches a bundle of DiagnosticReport resources based on query parameters. (GET /api/ehr/v2/fhir/DiagnosticReport). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth diagnostic report by ID** (Get). Fetches a specific DiagnosticReport resource. (GET /api/ehr/v2/fhir/DiagnosticReport/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth document references** (List). Fetches a bundle of DocumentReference resources based on query parameters. (GET /api/ehr/v2/fhir/DocumentReference). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth document reference by ID** (Get). Fetches a specific DocumentReference resource. (GET /api/ehr/v2/fhir/DocumentReference/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth encounters** (List). Fetches a bundle of Encounter resources based on query parameters. (GET /api/ehr/v2/fhir/Encounter). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth encounter by ID** (Get). Fetches a specific Encounter resource. (GET /api/ehr/v2/fhir/Encounter/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth family member histories** (List). Fetches a bundle of FamilyMemberHistory resources based on query parameters. (GET /api/ehr/v2/fhir/FamilyMemberHistory). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth family member history by ID** (Get). Fetches a specific FamilyMemberHistory resource. (GET /api/ehr/v2/fhir/FamilyMemberHistory/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth goals** (List). Fetches a bundle of Goal resources based on query parameters. (GET /api/ehr/v2/fhir/Goal). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth goal by ID** (Get). Fetches a specific Goal resource. (GET /api/ehr/v2/fhir/Goal/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth immunizations** (List). Fetches a bundle of Immunization resources based on query parameters. (GET /api/ehr/v2/fhir/Immunization). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth immunization by ID** (Get). Fetches a specific Immunization resource. (GET /api/ehr/v2/fhir/Immunization/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth locations** (List). Fetches a bundle of Location resources based on query parameters. (GET /api/ehr/v2/fhir/Location). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth location by ID** (Get). Fetches a specific Location resource. (GET /api/ehr/v2/fhir/Location/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth medication administrations** (List). Fetches a bundle of MedicationAdministration resources based on query parameters. (GET /api/ehr/v2/fhir/MedicationAdministration). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth medication administration by ID** (Get). Fetches a specific MedicationAdministration resource. (GET /api/ehr/v2/fhir/MedicationAdministration/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth medication dispenses** (List). Fetches a bundle of MedicationDispense resources based on query parameters. (GET /api/ehr/v2/fhir/MedicationDispense). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth medication dispense by ID** (Get). Fetches a specific MedicationDispense resource. (GET /api/ehr/v2/fhir/MedicationDispense/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth medication requests** (List). Fetches a bundle of MedicationRequest resources based on query parameters. (GET /api/ehr/v2/fhir/MedicationRequest). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth medication request by ID** (Get). Fetches a specific MedicationRequest resource. (GET /api/ehr/v2/fhir/MedicationRequest/{id}). The id is the FHIR resource id. Required: id.
- **Get single CharmHealth medication by ID** (Get). Fetches a specific Medication resource. (GET /api/ehr/v2/fhir/Medication/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth observations** (List). Fetches a bundle of Observation resources based on query parameters. (GET /api/ehr/v2/fhir/Observation). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth observation by ID** (Get). Fetches a specific Observation resource. (GET /api/ehr/v2/fhir/Observation/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth organizations** (List). Fetches a bundle of Organization resources based on query parameters. (GET /api/ehr/v2/fhir/Organization). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth organization by ID** (Get). Fetches a specific Organization resource. (GET /api/ehr/v2/fhir/Organization/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth patients** (List). Fetches a bundle of Patient resources based on query parameters. (GET /api/ehr/v2/fhir/Patient). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth patient by ID** (Get). Fetches a specific Patient resource. (GET /api/ehr/v2/fhir/Patient/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth practitioners** (List). Fetches a bundle of Practitioner resources based on query parameters. (GET /api/ehr/v2/fhir/Practitioner). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth practitioner by ID** (Get). Fetches a specific Practitioner resource. (GET /api/ehr/v2/fhir/Practitioner/{id}). The id is the FHIR resource id. Required: id.
- **List all CharmHealth procedures** (List). Fetches a bundle of Procedure resources based on query parameters. (GET /api/ehr/v2/fhir/Procedure). Returns the Bundle's entries' resources; the connector pages with page while the Bundle has a next link or more entries than seen (Bundle.total).
- **Get single CharmHealth procedure by ID** (Get). Fetches a specific Procedure resource. (GET /api/ehr/v2/fhir/Procedure/{id}). The id is the FHIR resource id. Required: id.
- ...and 10 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
