Back to MCP Servers

HealthEx MCP Server

Provider-hosted MCP server that gives AI agents secure, patient-consented access to unified personal health records via TEFCA, FHIR R4, and C-CDA.

Healthcare & Life Sciences by HealthEx OAuth2 active
Overview

HealthEx is a unified health records platform that aggregates a patient's medical history from across the US healthcare system and exposes it to AI agents through a hosted MCP server. The company operates as an Information Access Services (IAS) Provider on the federal TEFCA interoperability network, allowing patients to pull records from more than 50,000 provider organizations including Epic, Athena, MEDITECH, and eClinicalWorks portals. Records are normalized into FHIR R4 resources, C-CDA R2.1 documents, and clinical notes.

The MCP server lets connected AI assistants retrieve only the specific portions of a record needed for each question (a lab trend, a medication list, a visit note) rather than ingesting an entire file. It exposes structured tools for conditions, medications, labs, vitals, procedures, immunizations, visits, and allergies, plus a semantic search tool that runs natural language queries across the full record. Patients grant granular, category-level consent and can revoke access at any time.

HealthEx is the first health-data MCP integration officially supported by Anthropic, available to Claude Pro and Max users through the Claude connector directory. Authentication uses OAuth 2.0 Authorization Code Flow with PKCE and dynamic client registration (RFC 7591), so the same endpoint works for Claude, ChatGPT Apps, and any other OAuth 2.0 compatible AI agent. HealthEx-connected sessions are excluded from model training and not stored in Claude's long-term memory.

Tools

Tool Description
get_health_summary Retrieve a comprehensive current health snapshot including age, date of birth, gender, active conditions, current medications with dosages, allergies with reactions, and most recent vital signs.
get_conditions List medical conditions with start and end dates.
get_medications Detailed medication information including dosing instructions, prescribing provider, indication, start date, pharmacy, and refill history.
get_allergies Allergy and intolerance information including allergen, clinical status, verification status, criticality, onset, and documented reactions.
get_labs Laboratory test results including test name, value with units, reference range, date performed, ordering provider, and abnormal flags.
get_vitals Vital sign measurements including blood pressure, heart rate, temperature, respiratory rate, oxygen saturation, weight, height, and BMI.
get_procedures Medical procedures including surgeries, diagnostic procedures, biopsies, and interventions.
get_immunizations Complete vaccination history including vaccine name, date administered, dose number, series status, and administering provider.
get_visits Clinical visit history including visit date, type, provider, location, chief complaint, and diagnoses addressed.
search_clinical_notes Keyword or phrase search across clinical notes, or retrieve notes for a specific encounter.
search Semantic natural language search across all patient health record categories with relevance ranking.
update_records Requests a background refresh of health records from connected provider locations.
check_records_status Returns the current sync status of health records. Read-only.
Setup Guide

HealthEx is a provider-hosted MCP server. There is nothing to install or self-host. Patients authorize the connection through HealthEx, and AI clients connect to the hosted endpoint over OAuth 2.0.

Prerequisites

  • A HealthEx account (sign up at healthex.io)
  • CLEAR biometric identity verification with a valid US government ID
  • Provider portal logins (Epic MyChart, Athena, MEDITECH, eClinicalWorks, etc.) for the records you want to pull
  • An MCP client that supports OAuth 2.0 with PKCE and dynamic client registration

Option 1: Claude (recommended)

The fastest path is the official HealthEx connector in Claude's directory (available to Claude Pro and Max users):

  1. Visit the HealthEx connector at https://claude.ai/directory and select HealthEx
  2. Complete CLEAR identity verification
  3. Approve consent (valid up to 1 year)
  4. Connect your provider portals
  5. Wait for the initial record sync (10 to 30 minutes), then use Claude normally

Option 2: Custom MCP client

Connect any OAuth 2.0 compatible MCP client directly to the hosted endpoint:

{
  "mcpServers": {
    "healthex": {
      "url": "https://api.healthex.io/mcp",
      "transport": "http",
      "auth": {
        "type": "oauth2",
        "discovery": "https://api.healthex.io/.well-known/oauth-authorization-server"
      }
    }
  }
}

Register your client dynamically via RFC 7591:

curl -X POST https://api.healthex.io/oauth/register \
  -H "Content-Type: application/json" \
  -d '{
    "client_name": "Your AI Agent",
    "redirect_uris": ["https://your-app.com/callback"],
    "token_endpoint_auth_method": "none",
    "grant_types": ["authorization_code", "refresh_token"]
  }'

Then run the standard OAuth Authorization Code flow with PKCE. Use the resulting bearer token to call tools/list and tools/call on the /mcp endpoint. The full integration guide is at https://docs.healthex.io/mcp-server/.

Use Cases
  • Ask Claude to summarize your full medical history into a one-page health snapshot before a new doctor visit
  • Get plain-language explanations of recent lab results with reference ranges and trends over time
  • Generate a complete, current medication list with dosages and prescribing providers for a specialist appointment
  • Track chronic condition metrics (A1c, blood pressure, cholesterol) across years and across multiple provider systems
  • Search free-text clinical notes for mentions of a specific symptom, diagnosis, or recommendation across all past visits
Example Prompts
  • "Summarize my current health status: active conditions, medications, allergies, and most recent vitals."
  • "Show my A1c values over the last 5 years and tell me if the trend is improving."
  • "What vaccines am I missing for an adult my age, based on my immunization history?"
  • "Search my clinical notes for any mention of sleep apnea or CPAP."
  • "List every medication I am currently taking, with dosage and prescribing doctor, formatted for a new specialist."
Pros
  • Officially partnered with Anthropic and available as a first-party Claude connector
  • Aggregates records from 50,000+ provider organizations via the federal TEFCA network, not just one EHR vendor
  • Granular, category-level patient consent with revocation, and data excluded from model training
  • Granular tools (labs, vitals, medications, conditions, notes) plus semantic search avoid loading entire records into context
Limitations
  • US-only: relies on TEFCA and US provider portals, not available for international records
  • Setup is heavy compared to typical MCP servers (CLEAR identity verification, government ID, provider portal logins, 10 to 30 minute initial sync)
  • Records do not auto-refresh continuously; users must call update_records or trigger a manual refresh
  • No write capabilities: read-only access to records, cannot push data back to EHRs
Alternatives
  • Innovaccer Healthcare MCP (open-source spec extending MCP for healthcare): https://github.com/innovaccer/Healthcare-MCP
  • Direct FHIR MCP servers (community implementations that wrap a single EHR's FHIR API such as Epic or Cerner)
  • Apple Health export plus a generic file-reading MCP, for patients who only need device and self-reported data