eClinicalWorks MCP connector
The eClinicalWorks connector brings patients, encounters, conditions, medications and practitioners into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can ask questions of the practice's records under their own eClinicalWorks access.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
45 tools
How to connect
How to connect eClinicalWorks to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect eClinicalWorks once
-
Open Connections, choose Add connection, and pick eClinicalWorks.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own eClinicalWorks app, then approve. eClinicalWorks needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
eClinicalWorks 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.
eClinicalWorks 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 today. The plugin directory lives at chatgpt.com/plugins.
eClinicalWorks 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.
Connect eClinicalWorks 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.
Use cases
What teams do with eClinicalWorks through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Front desk
Pull up a patient before they arrive
Ask for a patient's record, the related persons on file and the location of their visit, so a check-in question is answered before the phone call ends.
-
Clinical
See allergies and medications before a visit
Ask what a patient is allergic to and which medication requests are open, and get a plain summary drawn from eClinicalWorks rather than clicking through tabs.
-
Care coordination
Review conditions across recent encounters
List a patient's conditions alongside their recent encounters to prepare a handoff note or a follow-up call in a few minutes.
-
Billing
Match an encounter to the right practitioner
Look up an encounter, the practitioner who handled it and the organization it belongs to before a claim goes out the door.
-
Quality
Check immunization records for a group
List immunizations and conditions across patients to answer a reporting question without exporting a spreadsheet from eClinicalWorks.
-
Practice management
Know who works where
List practitioners, their roles and the locations they cover when planning coverage or bringing on a new clinician.
Try asking
- “List the open medication requests for patient Maria Lopez.”
- “Which practitioners are assigned to the Riverside location?”
- “Summarize this patient's allergies and conditions before the 2pm visit.”
Compare
Elaichi vs Zapier MCP vs Composio for eClinicalWorks
All three can connect eClinicalWorks 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 eClinicalWorks tools | Allow or restrict single eClinicalWorks 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 eClinicalWorks 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 | $15 per user per month. | 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.
AI tools
eClinicalWorks tools for your AI agents
45 tools are ready to call through Elaichi's MCP endpoint the moment you connect eClinicalWorks, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting eClinicalWorks gets you
6 screens from the product, each doing one job for your eClinicalWorks account.
The agent
Ask in plain language, get live patient answers.
Three starter prompts pull conditions, allergies and encounters straight from eClinicalWorks.
- patients
- encounters
- conditions
- medication requests
Ask Elaichi to work across your apps.
List the open medication requests for patient Maria Lopez.
Which practitioners are assigned to the Riverside location?
Summarize this patient's allergies and conditions before the 2pm visit.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint serves Claude, ChatGPT and Cursor.
Connect eClinicalWorks once over OAuth and every MCP client works, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
45 eClinicalWorks tools, ready without any code.
Patients, encounters, conditions, immunizations and medication requests, cataloged with their resources and methods.
- Get single eClinicalWorks patient by ID
- List all eClinicalWorks patients
- Get single eClinicalWorks practitioner by ID
- List all eClinicalWorks practitioners
ElaichiToolsToolboxes
Every team gets its own eClinicalWorks toolbox.
Front desk, clinical and billing each see only the toolbox scoped to them.
- Front desk
- Clinical
- Pharmacy
- Billing
ElaichiToolboxesShared connections
Share one eClinicalWorks connection, never a credential.
The table shows who connected each account and which teams and members work through it.
- Front desk
- Clinical
- Billing
- Care coordination
ElaichiConnectionsAudit log
Every patient lookup is logged with a name.
When, who, what happened, type and resource, for every call into eClinicalWorks.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts the work, a person approves.
Each morning's encounters are fetched, grouped, drafted into a digest and sent once approved.
eClinicalWorks digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch patients
eClinicalWorks
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 Michael Brennan
Approve Deny -
Post the digest
eClinicalWorks
Queued
Collections and dashboards
eClinicalWorks health numbers, refreshed on a schedule.
Four metrics, 14 days of encounters created and a team breakdown, computed without a model.
eClinicalWorks health
Refreshed 4 minutes ago · every 15 minutes · from the patients collection
Patients
1,284 ↓ 12%
Encounters
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Patients created
Last 14 days
By team
Share of activity
Front desk 34%
Clinical 27%
Billing 21%
Care coordination 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect eClinicalWorks to Claude?
Connect eClinicalWorks in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. eClinicalWorks asks the practice to register an OAuth application on its side, so one administrator brings that client ID and secret into Elaichi once. After that, every person signs in with their own eClinicalWorks login and nobody else touches a secret.
Does eClinicalWorks work with ChatGPT and Cursor as well as Claude?
Yes. Once eClinicalWorks is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect eClinicalWorks once and every client sees it.
What can an AI agent actually do with my eClinicalWorks data?
An agent can look up patients, practitioners and their roles, organizations and locations, related persons, allergies, conditions, encounters, immunizations, medications, medication requests and medication administrations in eClinicalWorks, and answer questions about them in plain language. It reads these records; it does not edit charts. Short, concrete asks such as "list this patient's open medication requests" work better than long paragraphs.
Does connecting eClinicalWorks give the AI access to every patient chart?
No. Each person signs in to eClinicalWorks as themselves, so an agent sees only the patients, encounters and practice records that person could already open in eClinicalWorks. Elaichi can narrow that further with roles and restrictions, and it never widens it beyond what eClinicalWorks allows that person.
Can I stop an agent from deleting or changing things in eClinicalWorks?
Yes. Restrictions in Elaichi work per action, and a restricted action is left out of the AI client's list entirely, so it cannot be called no matter what the prompt says. The eClinicalWorks connector today only reads records such as patients, encounters and medication requests, and you can narrow even those reads to the parts a team needs.
What happens to an eClinicalWorks connection when someone leaves?
Offboarding a person in Elaichi ends their access to eClinicalWorks through every AI client at once. A shared eClinicalWorks connection keeps working for everyone else on the team. If you disconnect eClinicalWorks once in Elaichi, it is removed from Claude, ChatGPT, Cursor and every other client at the same time.
Does the eClinicalWorks MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. eClinicalWorks 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, 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 eClinicalWorks?
Yes. Both let Claude, ChatGPT or Cursor use eClinicalWorks. 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 eClinicalWorks call.
How is Elaichi different from Composio for eClinicalWorks?
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 eClinicalWorks: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put eClinicalWorks in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.