Eight EHR-adjacent companies have some kind of MCP server or AI-agent story as of July 2026: athenahealth, CharmHealth, Elation Health, Epic, Healthie, Medplum, the Canvas Medical ecosystem, and Eureka. Most of what has shipped is a developer tool you need an engineer to use, or a patient-facing pilot. Eureka's is the one built for doctors themselves and already running in production for solo private practice. Below is a full comparison, plus a look at the EHRs most solo practices actually run, none of which has shipped anything yet.
We will update this page as vendors add or change their agent integrations. Last checked July 2026.
Which EHRs have shipped an MCP server or agent feature?
| Vendor | What shipped | When | Who can use it |
|---|---|---|---|
| athenahealth | Patient-facing MCP server, described by athenahealth as an industry first | March 2026, pilot stage | Patients |
| CharmHealth | Public MCP server | Feb 2026 | Developers, enterprise integrators |
| Elation Health | Claude built into Clinical Insights for chart summarization | Generally available since Jan 2026 | Doctors, inside Elation's own interface |
| Epic | "Agent Factory" agent-building tooling | Announced at HIMSS 2026 | Health-system developers and IT teams |
| Healthie | "Dev Assist," an MCP server over Healthie's API docs | No public launch date given | Developers building on Healthie's API |
| Medplum | Official AI/MCP documentation plus a community MCP server | Ongoing, open source | Developers |
| Canvas Medical (ecosystem) | Third-party MCP wrappers (Composio, Klavis) over Canvas's API; no first-party agent product from Canvas | Ongoing | Developers |
| Eureka | First-party MCP server, in production, about 37 tools across roughly 20 domains | Live now | Doctors, via a per-doctor API key |
Two rows need a footnote. Epic's Agent Factory is tooling for health-system developers to build agents on top of Epic, not a server a doctor connects to directly. Canvas Medical has no first-party agent product of its own: what exists are third-party wrappers over its public API, built by Composio and Klavis, aimed at developers rather than clinicians.
What about the EHRs solo practices actually use?
None of the software most solo practices run day to day has shipped an MCP server or AI-agent integration as of July 2026.
| EHR | MCP or agent integration | Notes |
|---|---|---|
| SimplePractice | None | No public API for individual practitioners, no webhooks, no MCP server. AI features are a scribe add-on and a beta "Care Aide." |
| Osmind | None | Lists an AI scribe as "coming soon." No MCP or agent integration shipped yet. |
| TherapyNotes | None | No public MCP or AI-agent integration. |
| Valant | None | No public MCP or AI-agent integration. |
| ICANotes | None | No public MCP or AI-agent integration. |
Without a public API, there is nothing for an outside AI tool to call: any AI feature these vendors add stays inside their own product.
How to read this list
The phrase "MCP server" covers three different situations depending on who is actually holding the keyboard.
Patient-facing means the agent is built for the patient to talk to. athenahealth's pilot falls here: it is not something a doctor's own tools connect to.
Developer-facing means a software engineer has to build something on top of the server before anyone benefits from it. CharmHealth, Healthie, Medplum, and the Canvas ecosystem all fall here. A solo doctor without an engineer on staff cannot use any of these directly.
Doctor-facing means the doctor interacts with the agent themselves, inside their own workflow. Elation's Claude integration qualifies, but only inside Elation's own chart view; it is a feature of that product, not an open server other AI tools can plug into. Eureka's MCP server is doctor-facing too, and it is open: each doctor gets their own API key and can point any MCP-compatible client, such as Claude, Codex, or Cursor, at their own practice's data.
Epic's Agent Factory lands closest to developer-facing: it is a kit for building agents inside a health system's IT stack, not something an individual doctor sets up on their own.
Where Eureka fits
Eureka's MCP server is first-party, doctor-facing, and in production today, built specifically for the solo-practice segment. It runs at https://api.eureka.md/mcp, authenticates with a per-doctor API key scoped to that doctor's own practice, and exposes about 37 tools across roughly 20 clinical and administrative domains: appointments, billing, notes, e-prescribing, and more. Read tools and write tools are separate, so a doctor can register a read-only agent with no path to it taking any action. Full detail on the tool surface and setup is in our MCP server reference; connecting Claude specifically is covered in connecting Claude to Eureka.
We make a related case elsewhere on this site: an EHR built to be the substrate an agent runs on differs from an agent bolted onto a legacy record as a separate layer. See why an AI-native EHR differs from an AI layer on a legacy one. The assistant that runs on Eureka's own data day to day, drafting patient replies and proposing reschedules or refills for a doctor to approve, is covered in AI agents for private practice.
If you're a Eureka doctor and want an API key for your own practice, ask in your practice Slack channel or reach out at eureka.md/support.