Epic MCP connector
The Epic connector brings appointments, allergies, care plans, care teams, accounts, claims and patient communications into Claude, ChatGPT, Cursor and the Elaichi Agent, where each person works inside their own Epic access with every call logged.
-
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.
143 tools
How to connect
How to connect Epic to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Epic once
-
Open Connections, choose Add connection, and pick Epic.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Epic app, then approve. Epic 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.
Epic 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.
Epic 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.
Epic 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 Epic 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 Epic through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Scheduling
See the day's appointments at a glance
Ask for today's Epic appointments, pull up a single visit to confirm the time and provider, and answer a patient's phone call without clicking through the schedule.
-
Nursing
Check allergies before a visit starts
Review a patient's recorded allergy intolerances in Epic before they are roomed, and record a newly reported allergy so it is on the chart before the clinician walks in.
-
Patient safety
Review adverse events across the unit
List the adverse events recorded in Epic this week, open any one of them for the detail, and prepare the summary for the safety huddle.
-
Care coordination
Find out who is on a care team
Search Epic care teams for a patient, read the current care plan, and know exactly who to call about a discharge or a follow-up.
-
Revenue cycle
Look up an account or a claim
Pull a patient account or a specific claim from Epic to answer a billing question while the caller is still on the line.
-
Health information
Log a communication to the record
Record a call, a letter or a message as an Epic communication so the patient record shows what was said and when, and list past communications when a question comes back.
Try asking
- “List today's appointments and flag any patient with a documented allergy.”
- “Who is on the care team for the patient on account 48213?”
- “Summarize the adverse events recorded this week.”
Compare
Elaichi vs Zapier MCP vs Composio for Epic
All three can connect Epic 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 Epic tools | Allow or restrict single Epic 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 Epic 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
Epic tools for your AI agents
143 tools are ready to call through Elaichi's MCP endpoint the moment you connect Epic, 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 Epic gets you
6 screens from the product, each doing one job for your Epic account.
The agent
Ask Epic a question, get a live answer.
Appointments, allergies and care plans answered in plain language from current Epic records.
- appointments
- care plans
- allergy intolerances
- communications
Ask Elaichi to work across your apps.
List today's appointments and flag any patient with a documented allergy.
Who is on the care team for the patient on account 48213?
Summarize the adverse events recorded this week.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Epic endpoint for every AI client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
143 Epic tools, ready without writing code.
Appointments, allergies, care teams, claims and communications covered, with no custom code to maintain.
- Get single Epic account by ID
- List all Epic accounts
- Get single Epic adverse event by ID
- List all Epic adverse events
ElaichiToolsToolboxes
Every team gets its own Epic toolbox.
Scheduling, nursing and billing each work from a toolbox scoped to their job.
- Scheduling
- Nursing
- Care coordination
- Revenue cycle
ElaichiToolboxesShared connections
Share Epic access, never share a credential.
One person connects Epic, teams work through it, and nobody else sees a secret.
- Front desk
- Nursing
- Care coordination
- Revenue cycle
ElaichiConnectionsAudit log
Every Epic call is on the record.
Who touched which appointment, allergy or claim, and when, in an append-only log.
- 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 real Epic work.
Appointments are fetched, grouped and drafted into a digest a person approves before posting.
Epic digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch appointments
Epic
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
Epic
Queued
Collections and dashboards
Epic health numbers, computed with no model.
Four metrics, 14 days of records created and a team breakdown, refreshed on a schedule.
Epic health
Refreshed 4 minutes ago · every 15 minutes · from the appointments collection
Appointments
1,284 ↓ 12%
Care plans
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Appointments created
Last 14 days
By team
Share of activity
Front desk 34%
Nursing 27%
Care coordination 21%
Revenue cycle 18%
FAQ
Frequently asked questions
How do I connect Epic to Claude?
First, register an OAuth application inside Epic and bring its client ID and secret into Elaichi once, when you connect Epic. After that, each person signs in through Epic's own login page and never handles the secret themselves. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude asks you to sign in to Elaichi and Epic is ready to use.
Does Epic work with ChatGPT and Cursor as well as Claude?
Yes. Once Epic 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 Epic once and every client uses that one connection.
What can an AI agent actually do with my Epic data?
It can list and open appointments, allergy intolerances, adverse events, care plans, care teams, accounts, claims, documents and communications in Epic, and it can record a new allergy, a new communication or a body structure note. The AI client does not see a list of every Epic action; it searches for the right one and runs it, so short concrete asks like "list today's appointments" work better than long sentences. Anything you ask for runs inside your own Epic access.
Does connecting Epic give the AI access to every patient chart?
No. Every call to Epic runs as the person who signed in, so the AI sees only the patients, departments and records that person could already open in Epic. Elaichi can narrow that further by hiding actions or whole areas, but it never widens what Epic itself allows.
Can I stop an agent from changing things in Epic?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Epic appointments and care plans while blocking the creation of allergies or communications. A restricted action is left out of the AI client's list entirely and cannot be called, whatever the prompt says.
What happens to an Epic connection when someone leaves?
Offboarding that person in Elaichi ends their Epic access through every AI client at once. A shared Epic connection keeps working for everyone else on the team. If you ever want to remove Epic completely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the Epic MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Epic 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 Epic?
Yes. Both let Claude, ChatGPT or Cursor use Epic. 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 Epic call.
How is Elaichi different from Composio for Epic?
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 Epic: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Epic 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.