The eClinicalWorks MCP server lets AI agents read and write clinical, scheduling, and billing data in eClinicalWorks and healow. Connect eClinicalWorks to Claude, ChatGPT, and Cursor. Built and maintained by Supergood, since eClinicalWorks doesn't ship an MCP server.
The eClinicalWorks MCP server is a connector that lets AI agents (Claude, ChatGPT, Cursor, and other MCP clients) read and write clinical, scheduling, and billing data in eClinicalWorks and healow through a standard protocol.
In short: eClinicalWorks is a cloud EHR and practice management platform used by ambulatory practices, FQHCs, hospitals, and specialty clinics, with the healow patient-engagement suite, an RCM service, and AI tooling like Sunoh.ai.
eClinicalWorks doesn't ship an official MCP server, and eClinicalWorks has a limited public API surface, so deeper integrations sit behind partnership and certification programs with no self-serve developer access. Supergood builds and maintains the connector by reverse-engineering eClinicalWorks's authenticated web and batch flows and exposing them as MCP tools an agent can call directly, plus a normalized REST API underneath.
Once connected, an agent can:
Connecting works like any other MCP server. The short version:
Supergood owns the auth piece (credentials, MFA, session refresh), so the connection doesn't drop. New to MCP? Our explainer covers what an MCP server is and how clients connect to one.
Supergood doesn't wait for eClinicalWorks to ship an API. We reverse-engineer the authenticated web and batch flows behind eClinicalWorks, normalize the responses, and wrap them as MCP tools, plus the underlying REST API if you'd rather call it from code.
Book a 30-minute call to confirm which eClinicalWorks modules and workflows you need and how authentication should work.
We deliver a hardened eClinicalWorks connector (MCP tools plus the underlying API) scoped to your workflows and entitlements.
Go live with continuous monitoring and automatic adjustments as eClinicalWorks changes.
- Verify eligibility for the day's schedule - Book and reschedule appointments across in-person and healow telehealth - Send intake forms and confirm contact details
- Pull the open encounter and the Sunoh.ai draft - Surface recent labs and medications for the visit - Flag notes that still need sign and lock
- Pull claims and remittances, post payments - Surface denials and prior-auth gaps - Reconcile patient balances and statements
- Pull HEDIS/HCC gaps for a panel - Surface care-plan items that are due - Feed registry reporting without manual exports
MCP transport
Remote MCP server over HTTPS; works with hosted MCP clients and with local MCP configs.
Authentication
Supergood provisions a dedicated eClinicalWorks account (managed email and phone) and handles MFA; you can also bring your own credentials. Session refresh is automatic.
Supported clients
Claude (Desktop, claude.ai, Claude Code), ChatGPT connectors, Cursor, and other MCP-compatible clients.
Tools exposed
8 tools covering the workflows listed above; the set is scoped to the modules you license.
Data freshness
Near real-time for clinical and scheduling reads; billing spans clearinghouse and ERA batch windows, which Supergood bridges.
Rate limits
Tuned to eClinicalWorks's tolerances; Supergood paces requests to avoid tripping security throttles.
Latency
Sub-second for most reads under normal load; writes reflect the underlying platform timing.
Session management
Automatic re-auth plus cookie/token rotation, with health checks.
Security
Encrypted transport, scoped access, and audit logging; respects eClinicalWorks role-based permissions.
Webhooks
Optional asynchronous delivery for long-running operations; polling otherwise.
Reliability
Retry logic, backoff, and idempotency keys to avoid duplicates.
Adaptation
Continuous monitoring for eClinicalWorks web and batch surfaces changes, with rapid connector updates.
No. eClinicalWorks doesn't publish an MCP server. Supergood builds and maintains one by reverse-engineering eClinicalWorks's authenticated flows and exposing them as MCP tools, plus the underlying REST API.
All of them, plus any MCP-compatible client. The same connector shows up in Claude (Desktop, claude.ai, Claude Code), ChatGPT connectors, and Cursor.
Supergood provisions a dedicated eClinicalWorks account with managed MFA, or uses credentials you supply. We keep the session alive through MFA prompts, token expiry, and re-auth, so the connection stays live.
Yes. Reads and writes hit eClinicalWorks's live system, not a nightly export. eClinicalWorks has a limited public API surface, with deeper integrations sitting behind partnership and certification programs and no self-serve developer access.
Both. The MCP tools are a layer on top of a normalized REST API for eClinicalWorks; you can call either, from an agent or from your own code.