The EHR with an MCP server built in.
Connect Claude Code, ChatGPT, Codex, or Cursor to your practice in ten minutes. Your agent reads the schedule, preps your charts, drafts the replies, books the follow-ups. You approve what matters and sign what's yours.
> prep my thursday
Thursday: 6 visits, first at 9:10. Two intakes with forms already in. Mr. R replied about rescheduling, draft ready for review. One lab result needs a look before the 2:40. Collections this week: $4,310, one card to retry.
Every EHR will have an MCP server. One already does.
In 2026, athenahealth announced a patient-facing MCP pilot. CharmHealth shipped one for enterprise integrators. Epic unveiled agent tooling for health-system IT. The EHRs solo practices actually run, SimplePractice, Osmind, TherapyNotes, shipped nothing: no MCP server, and in most cases no public API at all.
Eureka took the other road. Our MCP server is doctor-facing, in production today, and included with every practice. Your own API key, your own agent, your own chart.
| EHR | MCP server | Who can use it |
|---|---|---|
| Eureka | First-party, in production | Doctors, with their own API key |
| athenahealth | Patient-facing pilot (announced March 2026) | Patients |
| CharmHealth | Enterprise-oriented (announced Feb 2026) | Integrators |
| Epic | Agent tooling announced at HIMSS 2026 | Health-system IT teams |
| Healthie | MCP server over its API docs | Developers |
| SimplePractice | None, and no public API | No one |
| Osmind, TherapyNotes, Valant | None | No one |
Vendor status as of July 2026. Full sourcing and updates in our EHR MCP roundup.
What do you say to an EHR that listens?
These run today, against your real practice, from whichever agent you already use.
"Prep my Thursday"
A morning brief: schedule, chart context, forms in, messages waiting, money on the table.
"Book Mrs. K a 30-minute follow-up next Tuesday afternoon"
Slot found, visit booked. Her card is never touched and she isn't messaged unless you say so.
"Draft a reply to Mr. R about moving his Tuesday visit"
A reply in your voice, from his chart and history. You read it, then you send it.
"Who hasn't booked a follow-up 90 days after their last visit?"
The gap list, pulled from your real panel, ready for recall.
"Pull July collections and flag unpaid visits"
Your numbers, not a dashboard's version of them.
"Start a note for my 3pm and bring in her intake answers"
The chart opens ready. You walk in already caught up.
Promises we make to the doctor who automates.
Included, never gated.
Your MCP key comes with your practice. No enterprise tier, no pilot waitlist, no per-call pricing. Other vendors gate their agent access behind sales teams; yours arrives when your charts do.
If a tool is missing, we build it.
Your agent asks for something our server doesn't expose yet? Tell us. We ship new tools on request, usually within days. Customer demand is the roadmap, and it always has been.
Ten minutes to your first brief.
One command connects Claude Code. If anything takes longer than ten minutes, get on a call and we'll finish the setup with you, then wire your first three automations together. Free.
A safety floor that doesn't move.
Read-only mode is one deny pattern. New bookings never touch a patient's card by default. Prescribing never leaves the app. Your signature stays yours. These are design decisions, not settings.
Your panel, moved for you.
Switching EHRs is our specialty. We migrate your charts ourselves, readable, before you commit to anything.
From key to working agent in three steps.
Ask for your key.
Every Eureka doctor gets a personal API key, scoped to their own practice, revocable any time.
Add the server.
claude mcp add --transport http eureka https://api.eureka.md/mcp \ --header "Authorization: Bearer eur_your_key"ChatGPT, Codex, and Cursor setups are in the docs.
Say the thing.
"Prep my day." "Who's overdue?" "Draft the reply." Your agent picks the right tool from a plain request.
The EHR is the agent substrate.
Most "AI in healthcare" products are overlays: a bot bolted onto a chart that was never meant to be read by software, writing back through brittle integrations. Eureka is built the other way around. Every part of the practice, scheduling, notes, billing, messaging, forms, recalls, is exposed as typed tools an agent can call, with reads and writes registered separately.
We trust this architecture with our own product. Eureka's built-in assistant, the one drafting patient replies inside every practice, runs on the same MCP tools we hand you, locked to a read-only subset because patient-authored text deserves a prompt-injection boundary. Your agent gets the same rails.
Eureka signs a BAA with every practice. Connecting your own AI vendor to PHI is your call as the covered entity; our HIPAA notes cover what to check, and read-only mode narrows the blast radius while you decide.
Due diligence, answered
Is this real, today?
Yes. The server runs in production at api.eureka.md/mcp: 37 tools, resource URIs, and two built-in prompts. The technical reference documents every domain.
Which agents work with it?
Anything that speaks MCP over streamable HTTP: Claude Code, Claude Desktop, ChatGPT developer mode, Codex CLI, Cursor, or your own harness with a bearer header.
Do I need to know how to code?
No. Desktop clients connect through settings, and we'll do the setup with you on a call if you'd rather not touch a terminal. If you do live in one, you'll feel at home.
What does the EHR cost?
One share of collections with 80% take-home guaranteed. No setup fee, no charge while your calendar is empty, and the MCP server is included, never an add-on.
Bring your agent. We'll bring the practice.
A full EHR underneath: charts, e-prescribing, billing, scheduling, messaging. An MCP server on top, so the AI you already trust can finally do the work.