Epic MCP
Related Servers
Alternatives to Epic MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to securely read and organize a patient's own health records from Epic MyChart via the FHIR API, including labs, documents, appointments, and attachments, using OAuth-based authorization.-
- AlicenseAqualityAmaintenanceEnables reading a patient's own Epic MyChart portal data — test results, medications, allergies, immunizations, health issues, goals, visits, messages, insurance, care team and billing — by relaying requests through the signed-in browser tab or signing in server-side with human-in-the-loop MFA. It also lets the active patient reply to Message Center conversations after an explicit confirmation step.24640 npm1MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to read a user's own lab results, imaging reports, visit summaries, and upcoming appointments from the beWell patient portal, with local sign-in and read-only access.6MIT
- -licenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to securely access Epic Healthcare Systems patient data through FHIR R4 API integration. Provides tools for searching patients, retrieving clinical summaries, vital signs, medications, and generating healthcare reports with HIPAA-compliant OAuth 2.0 authentication.-
- AlicenseAqualityBmaintenanceEnables AI assistants to securely read a user's own sundhed.dk health record data, including medications, lab results, vaccinations, and referrals, after MitID login via a local browser session.1223 npmMIT
- AlicenseBqualityBmaintenanceA local-first MCP server that enables AI agents to read user-authorized Google Health API v4 data from Fitbit, Pixel Watch, and partners via OAuth, with tokens never leaving the machine.26875 npm84MIT
TDQS
Scored across 7 tools
The auth lifecycle steps (login, complete_login, login_status, logout) are related but distinguishable via their descriptions, and the data tools (get_medications, get_patient) plus audit tool (get_access_log) are clearly separate. The main risk is an agent confusing login with complete_login when skimming names, though the descriptions resolve it.
All names use snake_case and are readable, with data tools following a get_noun pattern. Auth tools deviate (login, complete_login, login_status, logout) but the deviation is semantically sensible; login_status is the only name that doesn't fit a pure verb_noun shape.
Seven tools is well-scoped: four cover the necessary OAuth/MyChart sign-in lifecycle, two fetch patient data, and one provides an audit trail. Each tool has a clear reason to exist and nothing feels redundant.
The auth lifecycle and audit logging are complete, but for an Epic/MyChart patient-access server the data surface is very thin: only medications and basic demographics. Common FHIR resources such as lab results, conditions, allergies, immunizations, appointments, and messages are absent, so many plausible patient queries will dead-end.