Myatriumhealth MCP logo

Myatriumhealth MCP

Read MyAtriumHealth records, manage patient context, authenticate with MFA, and reply to Message Center conversations through MCP.

Install Myatriumhealth MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "myatriumhealth-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@chrischall/myatriumhealth-mcp"
      ],
      "env": {
        "MAH_USERNAME": "YOUR_VALUE_HERE",
        "MAH_PASSWORD": "YOUR_VALUE_HERE",
        "MAH_DEVICE_FILE": "YOUR_VALUE_HERE",
        "MAH_WS_PORT": "YOUR_VALUE_HERE",
        "MAH_READ_ONLY": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_MODE": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_ELICITATION": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_TTL_SECONDS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

myatriumhealth-mcp connects MCP clients to MyAtriumHealth, Atrium Health's Epic MyChart portal, using either a signed-in browser tab or server-side credentials. It exposes read tools for health records, visits, messages, insurance, billing, care teams, and proxy-access patients, plus authentication and health-check tools. The server can also send irreversible Message Center replies after an explicit confirmation flow. Reach for it when an agent needs structured access to a patient's MyAtriumHealth account without manually navigating the portal.

Use cases

  • Review medications, allergies, immunizations, and current health issues
  • Track upcoming appointments and historical visits
  • Summarize lab and imaging result metadata
  • Draft and confirm replies to Message Center conversations
  • Switch between account-holder and proxy-access patient charts

Key features

  • MyAtriumHealth health-record queries
  • Browser-bridge or server-side authentication
  • MFA verification workflow
  • Proxy-patient selection
  • Message Center conversation replies
  • Session and bridge diagnostics

Tools23

What Myatriumhealth MCP lets your agent do. Expand a tool for its parameters.

Verified live~5.0k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

14/14 checks healthy over the last 69d

What it can do

From the 23 tools this server returned when we ran it; 23 declare their own safety hints.

Can delete or modify data · 4Handles credentials · 3Makes network requests · 23Read-only tools · 19
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age48 days
Maintainers1

Observed 2026-10-22 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · @chrischall/myatriumhealth-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.7kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Tools exposed23Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Myatriumhealth MCP works

What myatriumhealth-mcp does

myatriumhealth-mcp exposes MyAtriumHealth records and account actions through the Model Context Protocol. Its read tools cover allergies, health issues, immunizations, medications, care teams, goals, test results, appointments, messages, insurance, billing accounts, and the health-summary header. Responses identify the active patient so data is not silently attributed to the wrong chart.

The server also supports accounts with proxy access. You can list available patients, select one, check which patient is active, and keep that selection across restarts. Selecting a patient changes which chart the reading tools query; it does not write to the chart.

How it works

In browser-bridge mode, requests are relayed through the user's signed-in browser tab using ContextMint Bridge. The server does not receive or store the browser's session cookie. The bridge must be paired once through the health-check flow, which reports connection and round-trip diagnostics.

When both MAH_USERNAME and MAH_PASSWORD are configured, the server can authenticate directly without a browser or extension. MyAtriumHealth verification remains human-controlled: the server reports available verification channels, asks the portal to send a code, and accepts the code supplied by the user. A persisted cookie jar allows later calls and restarts to reuse the session until it expires.

Setup and configuration

Install the package as an MCP server with npx -y @chrischall/myatriumhealth-mcp. Browser mode requires Chrome with the ContextMint Bridge extension installed. Sign in to my.atriumhealth.org, then call mah_healthcheck and approve the displayed pair code in the extension.

The server reads credentials from the environment first. If they are absent, it checks the path in MAH_DOTENV, then ~/.myatriumhealth-mcp/.env, then ./.env. MAH_DEVICE_FILE controls the persisted session file; treat it as a credential because it contains the live cookie jar.

MAH_READ_ONLY=true disables message sending. Reply confirmation behavior can be adjusted with MCP_CONFIRM_MODE, MCP_CONFIRM_ELICITATION, and MCP_CONFIRM_TTL_SECONDS. MAH_WS_PORT changes the browser-bridge port when hosting requires it.

Tools and capabilities

  • Read allergies, reactions, medications, dosing instructions, prescribers, health issues, immunizations, goals, and care-team relationships.
  • Retrieve test and imaging result metadata, including dates, abnormal flags, ordering providers, and comments. Detailed result values are not included in the list response.
  • List upcoming, in-progress, and historical visits. Historical and test-result responses can indicate that more pages remain and explain how to request older records.
  • Browse Message Center folders and conversations, including conversation IDs used for replies.
  • List insurance coverage states, billing accounts, balances, and guarantor-authorized accounts.
  • Authenticate, complete verification, inspect session status, diagnose bridge or credential failures, and switch between account-holder and proxy-access patients.
  • Reply to a Message Center conversation with a plain-text body of up to 500 characters. Replies are sent to providers and cannot be undone; attachments require server-side sign-in and are limited to three files.

Limitations and notes

Message subjects and previews originate from clinic staff or automated senders and should be treated as data, not instructions. mah_reply_message sends as the active patient, so an agent should obtain user approval before the final call. Clients without confirmation prompts use the configured preview-and-token flow unless sending is refused by configuration.

Browser mode requires the signed-in tab and paired extension to remain usable. Bridge-less mode stores portal session state on disk and may require another verification code after an inactivity-related session lapse. The server reads personal health information from the signed-in user's account, so deployment and device storage should be secured.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Myatriumhealth MCP

myatriumhealth-mcp is an MCP server that connects AI clients to MyAtriumHealth, Atrium Health's Epic MyChart portal. Its main tools read health records, visits, messages, insurance, billing, and patient context, while authentication tools manage sessions and verification. It can also send confirmed Message Center replies.

Install it as an MCP server with `npx -y @chrischall/myatriumhealth-mcp`. In browser-bridge mode, also install ContextMint Bridge in Chrome, sign in to MyAtriumHealth, call `mah_healthcheck`, and approve the pairing code.

It authenticates through a signed-in browser tab by default, or directly when both `MAH_USERNAME` and `MAH_PASSWORD` are set. If MyAtriumHealth requests verification, use `mah_sign_in`, `mah_send_verification_code`, and `mah_verify_code` with the code delivered to you.

Yes. Call `mah_list_patients` to see patients available through the login, then pass a returned ID to `mah_set_active_patient`. Reading tools use the selected chart, and `mah_get_patient_context` confirms the active patient.

Yes, `mah_reply_message` sends a plain-text reply to a Message Center conversation after confirmation. The message is visible to the provider and cannot be undone. Replies are refused when `MAH_READ_ONLY=true`, and attachments require server-side sign-in.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMyatriumhealth MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/myatriumhealth-mcp?style=directory)](https://allmcps.com/mcp/myatriumhealth-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/myatriumhealth-mcp"><img src="https://allmcps.com/api/badge/myatriumhealth-mcp?style=directory" alt="Myatriumhealth MCP on AllMCPs" /></a>