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.
- Connects over OAuth
- Free 14-day trial
- No credit card
Show me today's appointments and any open conditions for each patient.
Working in CharmHealth with Elaichi
-
List all CharmHealth allergy intolerances
-
Get single CharmHealth allergy intolerance by ID
-
List all CharmHealth appointments
How to connect CharmHealth to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
CharmHealth MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
CharmHealth MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with CharmHealth through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in CharmHealth is logged.
-
Front desk
Prepare tomorrow's schedule before the doors open
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.
-
Clinical
Review a patient's chart before the visit
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.
-
Care coordination
Keep care teams and care plans in view
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.
-
Billing
Check coverage before the claim goes out
Look up a patient's coverages alongside their recent encounters so the billing team can confirm the payer on file before submitting.
-
Compliance
Find the document when an auditor asks
Search document references and CCDA documents for a patient, and start or retrieve a bulk export when a records request comes in.
-
Nursing
Confirm allergies and devices at intake
Bring up a patient's allergy intolerances and recorded devices at check-in so nothing is missed before medication or a procedure.
Try asking
- “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.”
What connecting CharmHealth gets you
6 screens from Elaichi, each doing one job for your CharmHealth account.
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask in plain language, get live CharmHealth answers.
Appointments, conditions, care plans and diagnostic reports, answered from the record as it stands now.
Copy the endpoint
AI apps
One endpoint brings CharmHealth to every client.
Claude, ChatGPT and Cursor reach CharmHealth through one governed endpoint, no SDK, no shared key.
Tool catalog
60 CharmHealth tools, ready without writing code.
Appointments, encounters, conditions, care plans and more, cataloged and callable with no custom code.
Toolboxes
Every team gets its own CharmHealth toolbox.
Front desk sees appointments, clinicians see care plans, billing sees coverages, each in a scoped toolbox.
Shared connections
Share CharmHealth access without sharing a credential.
One person connects CharmHealth, shares it with teams, and nobody else ever sees the secret.
Audit log
Every CharmHealth call is logged with a name.
When, who, what happened and which record, kept in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
CharmHealth digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch appointments
CharmHealth
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
CharmHealth
Queued
Workflows
A schedule starts the work, a person approves.
Appointments are fetched, grouped and drafted into a digest, approved, then sent back to CharmHealth.
CharmHealth health
Refreshed 4 minutes ago · every 15 minutes · from the appointments collection
Appointments
1,284 ↓ 12%
Encounters
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Appointments created
Last 14 days
By team
Share of activity
Primary care 34%
Front desk 27%
Billing 21%
Care coordination 18%
Collections and dashboards
CharmHealth numbers refresh themselves, no prompt needed.
Four metrics, a 14 day chart of encounters and a team breakdown, computed without a model.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
CharmHealth tools for your AI agents
60 tools are ready to call through Elaichi's MCP endpoint the moment you connect CharmHealth, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
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 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.
Put CharmHealth in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot