Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words Sign in

Myatriumhealth MCP

by chrischallversion 1.5.1i★ 1iRuns on your computerRepository ↗
Registry nameio.github.chrischall/myatriumhealth-mcp

How to install

What it does

MyAtriumHealth (Epic MyChart) records via your signed-in browser tab

  • Connects Runs on your computer
  • Account or key Needs MAH_PASSWORD
  • Category Web & browsers

Use together with

Skills that teach the AI this kind of work; they work alongside this one

timesfm

TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.

by google-research★ 35,6381 skills

Skill · How-to guide

Shadowbroker

Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…

by BigBodyCobain★ 11,6051 skills

Skill · How-to guide

google-maps-scraper

scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place

by gosom★ 8,2361 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity23/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score35/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: 63 (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Myatriumhealth MCP. Follow https://mcp.popnx.com/i/chrischall-myatriumhealth-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Myatriumhealth MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Myatriumhealth MCP for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "myatriumhealth": { "command": "npx", "args": [ "-y", "@chrischall/myatriumhealth-mcp" ], "env": { "MAH_PASSWORD": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For MAH_PASSWORD, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Myatriumhealth MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Myatriumhealth MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  4. Paste these settings and save the file

    {
      "mcpServers": {
        "myatriumhealth": {
          "command": "npx",
          "args": [
            "-y",
            "@chrischall/myatriumhealth-mcp"
          ],
          "env": {
            "MAH_PASSWORD": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Quit Claude and open it again

  6. Try it

    Use Myatriumhealth MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Myatriumhealth MCP or shows a Myatriumhealth MCP tool in the answer, you are connected

7 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MAH_WS_PORT Override the fetchproxy WebSocket port (default 37149).
  • MAH_READ_ONLY true refuses mah_reply_message sends (previews still work). Default false.
  • MAH_USERNAME MyAtriumHealth username. Set with MAH_PASSWORD to enable bridge-less mode. Leave both empty to relay through your signed-in browser tab.
  • MAH_DOTENV Path to a .env file read first; failing that ~/.myatriumhealth-mcp/.env, then ./.env. A real MAH_USERNAME / MAH_PASSWORD in the environment always wins.
  • MAH_DEVICE_FILE Session state (0600), default ~/.myatriumhealth-mcp/device.json. Holds the live cookie jar as well as the device token — treat as a credential.
  • FETCHPROXY_WS_HOST Bind interface for the fetchproxy concentrator, a literal IP only (default 127.0.0.1). Keep on loopback; it exists for hosted deployments that run each MCP in its own network namespace.
  • FETCHPROXY_IDENTITY_DIR Absolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/).

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Myatriumhealth MCP yet

Myatriumhealth MCP runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Myatriumhealth MCP

  • You need a Myatriumhealth MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a Myatriumhealth MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a Myatriumhealth MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a Myatriumhealth MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

B · Others in Web & browsers that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a Myatriumhealth MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Myatriumhealth MCP for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user myatriumhealth --env MAH_PASSWORD=your-value -- npx -y @chrischall/myatriumhealth-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For MAH_PASSWORD, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Myatriumhealth MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Myatriumhealth MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  4. Paste this command and press Enter

    claude mcp add --scope user myatriumhealth --env MAH_PASSWORD=your-value -- npx -y @chrischall/myatriumhealth-mcp

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Type /mcp in Claude Code

    You should see Myatriumhealth MCP listed as connected

  6. Try it

    Use Myatriumhealth MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Myatriumhealth MCP or shows a Myatriumhealth MCP tool in the answer, you are connected

7 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MAH_WS_PORT Override the fetchproxy WebSocket port (default 37149).
  • MAH_READ_ONLY true refuses mah_reply_message sends (previews still work). Default false.
  • MAH_USERNAME MyAtriumHealth username. Set with MAH_PASSWORD to enable bridge-less mode. Leave both empty to relay through your signed-in browser tab.
  • MAH_DOTENV Path to a .env file read first; failing that ~/.myatriumhealth-mcp/.env, then ./.env. A real MAH_USERNAME / MAH_PASSWORD in the environment always wins.
  • MAH_DEVICE_FILE Session state (0600), default ~/.myatriumhealth-mcp/device.json. Holds the live cookie jar as well as the device token — treat as a credential.
  • FETCHPROXY_WS_HOST Bind interface for the fetchproxy concentrator, a literal IP only (default 127.0.0.1). Keep on loopback; it exists for hosted deployments that run each MCP in its own network namespace.
  • FETCHPROXY_IDENTITY_DIR Absolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/).

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Myatriumhealth MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Myatriumhealth MCP for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "myatriumhealth": { "command": "npx", "args": [ "-y", "@chrischall/myatriumhealth-mcp" ], "env": { "MAH_PASSWORD": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For MAH_PASSWORD, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Myatriumhealth MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Myatriumhealth MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  4. Fill in your key

    In the Myatriumhealth MCP settings, MAH_PASSWORD is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in Cursor in Agent mode

  6. Try it

    Use Myatriumhealth MCP and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Myatriumhealth MCP or shows a Myatriumhealth MCP tool in the answer, you are connected

7 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MAH_WS_PORT Override the fetchproxy WebSocket port (default 37149).
  • MAH_READ_ONLY true refuses mah_reply_message sends (previews still work). Default false.
  • MAH_USERNAME MyAtriumHealth username. Set with MAH_PASSWORD to enable bridge-less mode. Leave both empty to relay through your signed-in browser tab.
  • MAH_DOTENV Path to a .env file read first; failing that ~/.myatriumhealth-mcp/.env, then ./.env. A real MAH_USERNAME / MAH_PASSWORD in the environment always wins.
  • MAH_DEVICE_FILE Session state (0600), default ~/.myatriumhealth-mcp/device.json. Holds the live cookie jar as well as the device token — treat as a credential.
  • FETCHPROXY_WS_HOST Bind interface for the fetchproxy concentrator, a literal IP only (default 127.0.0.1). Keep on loopback; it exists for hosted deployments that run each MCP in its own network namespace.
  • FETCHPROXY_IDENTITY_DIR Absolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/).

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Myatriumhealth MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Myatriumhealth MCP for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "myatriumhealth": { "type": "stdio", "command": "npx", "args": [ "-y", "@chrischall/myatriumhealth-mcp" ], "env": { "MAH_PASSWORD": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For MAH_PASSWORD, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Myatriumhealth MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Myatriumhealth MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  4. Fill in your key

    In the Myatriumhealth MCP settings, MAH_PASSWORD is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in VS Code in Agent mode

  6. Try it

    Use Myatriumhealth MCP and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Myatriumhealth MCP or shows a Myatriumhealth MCP tool in the answer, you are connected

7 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • MAH_WS_PORT Override the fetchproxy WebSocket port (default 37149).
  • MAH_READ_ONLY true refuses mah_reply_message sends (previews still work). Default false.
  • MAH_USERNAME MyAtriumHealth username. Set with MAH_PASSWORD to enable bridge-less mode. Leave both empty to relay through your signed-in browser tab.
  • MAH_DOTENV Path to a .env file read first; failing that ~/.myatriumhealth-mcp/.env, then ./.env. A real MAH_USERNAME / MAH_PASSWORD in the environment always wins.
  • MAH_DEVICE_FILE Session state (0600), default ~/.myatriumhealth-mcp/device.json. Holds the live cookie jar as well as the device token — treat as a credential.
  • FETCHPROXY_WS_HOST Bind interface for the fetchproxy concentrator, a literal IP only (default 127.0.0.1). Keep on loopback; it exists for hosted deployments that run each MCP in its own network namespace.
  • FETCHPROXY_IDENTITY_DIR Absolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/).

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Myatriumhealth MCP💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user myatriumhealth --env MAH_PASSWORD=your-value -- npx -y @chrischall/myatriumhealth-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "myatriumhealth": {
      "command": "npx",
      "args": [
        "-y",
        "@chrischall/myatriumhealth-mcp"
      ],
      "env": {
        "MAH_PASSWORD": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "myatriumhealth": {
      "command": "npx",
      "args": [
        "-y",
        "@chrischall/myatriumhealth-mcp"
      ],
      "env": {
        "MAH_PASSWORD": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "myatriumhealth": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@chrischall/myatriumhealth-mcp"
      ],
      "env": {
        "MAH_PASSWORD": "your-value"
      }
    }
  }
}

Values you fill in

  • MAH_WS_PORT env
    Override the fetchproxy WebSocket port (default 37149).
  • MAH_READ_ONLY env
    true refuses mah_reply_message sends (previews still work). Default false.
  • MAH_USERNAME env
    MyAtriumHealth username. Set with MAH_PASSWORD to enable bridge-less mode. Leave both empty to relay through your signed-in browser tab.
  • MAH_PASSWORD secret required env
    Portal password. Both are required; setting only one falls back to the bridge (with a warning).
  • MAH_DOTENV env
    Path to a .env file read first; failing that ~/.myatriumhealth-mcp/.env, then ./.env. A real MAH_USERNAME / MAH_PASSWORD in the environment always wins.
  • MAH_DEVICE_FILE env
    Session state (0600), default ~/.myatriumhealth-mcp/device.json. Holds the live cookie jar as well as the device token — treat as a credential.
  • FETCHPROXY_WS_HOST env
    Bind interface for the fetchproxy concentrator, a literal IP only (default 127.0.0.1). Keep on loopback; it exists for hosted deployments that run each MCP in its own network namespace.
  • FETCHPROXY_IDENTITY_DIR env
    Absolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/).

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
928/wk
Connection
Runs on your computer
Latest versioni
1.5.1
Published to registryi
Nov 7, 2026
Code last changedi
Nov 19, 2026
Maker
chrischall
Packages
npm: @chrischall/myatriumhealth-mcp
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account chrischall, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed yesterday

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for @chrischall/myatriumhealth-mcp@1.5.1

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/chrischall-myatriumhealth-mcp.svg)](https://mcp.popnx.com/en/servers/chrischall-myatriumhealth-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Web & browsersi

  • More stars than 78% of the other 1650 servers in this category
  • Published to the registry more recently than 71% of the other 1650 servers in this category
  • Basic checks equal to or better than 99% of the other 1650 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Myatriumhealth MCP safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: MAH_PASSWORD

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed yesterday, and the latest version (1.5.1) reached the registry 13 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Browser Use, changedetection.io (official), Apify MCP Server, Pomerado, Actionbook

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Browser Use

Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.

by browser-useWidely used↓ 1.7M/wk★ 121.5KUpdated 30 days ago

Computer or cloud✓ service owner · browser-use.com

Apify MCP Server

Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡

by apifyWidely used★ 17KUpdated 3 days ago

Runs in the cloud✓ service owner · apify.com

Pomerado

Connect your agents to any website. The cheaper, faster and more reliable alternative to browser use

by PomeradoGrowing★ 1.8KUpdated 2 days ago

Runs in the cloud✓ service owner · pomerado.ai

Actionbook

Let your AI agent operate any website through a real, logged-in browser session.

by actionbookGrowing★ 1.6KUpdated 32 days ago

Runs in the cloud✓ service owner · actionbook.app
Compared with similar ones
This one
Myatriumhealth MCP
Browser Usechangedetection.io (official)Apify MCP ServerPomeradoActionbook
Runs whereInstalls on your computerCloud or install on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesYesNoYesNoNo
Add with + in ClaudeNoYesNoNoNoNo
Basic checks3/35/53/34/44/44/4
LicenseMITMITApache-2.0MITMITApache-2.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

myatriumhealth-mcp

MCP server for MyAtriumHealth — Atrium Health's Epic MyChart patient portal at my.atriumhealth.org. Reads test results, medications, allergies, immunizations, health issues, goals and visits.

This project was developed and is maintained by AI. Use at your own discretion.

It reads personal health information, and only ever from the signed-in user's own account.

Two ways to authenticate

ModeWhenCredentials held
Browser bridge (default)no credentials configurednone
Bridge-lessMAH_USERNAME + MAH_PASSWORD setyour portal password, on disk

Bridge-less logs in server-side — no browser, no extension — which is what makes hosting possible. Verification is human-in-the-loop: the portal challenges, mah_sign_in reports the channels your account allows, the portal sends a code to you, and mah_verify_code submits only what you provide. Nothing here bypasses the second factor.

When the session expires you do *not* reconnect the MCP or restart anything. The next tool call returns an actionable error naming the channels and your masked destinations; you pick one, the portal texts or emails you, and mah_verify_code resumes the session in place. A pending challenge is remembered, so further tool calls report it rather than re-submitting your password each time.

Where credentials are read from. A real MAH_USERNAME / MAH_PASSWORD in the environment always wins. Failing that the server reads the first .env it finds, in this order: MAH_DOTENV, then ~/.myatriumhealth-mcp/.env, then ./.env.

The middle one exists because MCP clients launch the server from whatever directory they happen to be in, so a .env sitting in a checkout is invisible to it — and the failure is quiet: with no credentials the server falls back to the browser bridge, binds a port and waits for a signed-in tab. If you meant to run bridge-less and see the bridge start, that is what happened; the startup line now says so.

How the session persists. After one verification the cookie jar is stored (0600, bound to the account) and reused, so restarts resume the existing session rather than signing in again — no browser and no further codes until the session lapses.

How long that lasts, measured rather than assumed. Every one of the ten cookies MyChart sets is a *session* cookie — none carries an expires or max-age — so the lifetime is the server's alone and cannot be read from the jar. A jar left idle for 219 minutes no longer authenticated: the next call fell through to a fresh sign-in and was challenged for a code immediately.

What that does and does not establish: it bounds an idle session, and says nothing about an active one. The measurement cannot tell an idle timeout from an absolute one, and portals of this kind usually expire on inactivity — so a session in steady use may outlive 3.6h comfortably, while one left alone will not. Plan re-verification around gaps in use, not around wall-clock age.

Why the jar is written back mid-session. Every response's Set-Cookie is absorbed, and the jar is re-persisted whenever a value actually changed (transport-server.ts after each request; a no-op write when nothing rotated). That is not bookkeeping: if the portal refreshes its ticket as a session is used, the refreshed one only survives a process restart by reaching disk. On a scale-to-zero host — where the child exits between tool calls — that write-back is the whole reason an extended session is still there on the next call, rather than the copy frozen at sign-in.

Two things none of this changes: a lapse still costs one code rather than a reconnect, and detection alone sends nothing — only mah_sign_in asks the portal to send anything.

What does NOT work, measured rather than assumed: the RememberDeviceId this

portal returns is *not* a device-tracking id it will accept back. Sending it neither

skips verification nor is harmless — it breaks the challenge, leaving the

SecondaryValidation page without its templateContext so the antiforgery token

cannot be read and SendCode returns 500. The account reports

RememberMeSettings.EnrollDeviceTracking: False, which fits. The token is therefore

stored but deliberately never sent.

The bridge mode's real virtue is that it holds no credentials at all. Prefer it unless you specifically need bridge-less.

How it works

Every MyChart cookie is HttpOnly and login is MFA-gated, so the session cannot be copied out of the browser and replayed from Node. Requests are therefore relayed through the user's own signed-in tab via the fetchproxy bridge and the ContextMint Bridge browser extension, reusing their authenticated session. The server never reads or stores the session cookie.

The portal's web app talks to a JSON API in two generations — modern POST api/ / and legacy form-encoded POST / / . Both are documented, with live-captured shapes, in docs/MYATRIUMHEALTH-API.md.

Install

{

"mcpServers": { "myatriumhealth": { "command": "npx", "args": ["-y", "@chrischall/myatriumhealth-mcp"] } } }

Bridge mode needs ContextMint Bridge, installed from its releases page — in Chrome, unzip the chrome zip and add it via chrome://extensions → Developer mode → Load unpacked. Use Chrome for now: the Safari build will ship inside the ContextMint app, which has no public download yet.

ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README points to it. Its source is public at nullnet-app/contextmint-bridge: build it yourself, or check a release zip against the .sha256 file published beside it (shasum -a 256 -c contextmint-bridge-chrome- .zip.sha256).

Then sign in to my.atriumhealth.org in your browser and call mah_healthcheck. The first call prints a pair code — approve it once in the ContextMint Bridge popup.

EnvDefaultPurpose
MAH_USERNAME—MyAtriumHealth username. Set with MAH_PASSWORD to enable bridge-less mode.
MAH_PASSWORD—Portal password. Both are required; setting only one falls back to the bridge (with a warning).
MAH_DEVICE_FILE~/.myatriumhealth-mcp/device.jsonSession state (0600). Holds the live cookie jar as well as the device token — treat as a credential.
MAH_WS_PORT37149fetchproxy concentrator port (bridge mode only). The whole fleet shares this one port; override only when hosting.
MAH_READ_ONLYfalsetrue refuses mah_reply_message sends (previews still work). The tool stays listed either way.
MCP_CONFIRM_MODEask-userWhat a reply does on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop). ask-user: two steps — the first call sends nothing and returns a preview plus a token, and the model must get your approval in chat before calling again with it. auto: the same two steps, but the model may use the token after reviewing the preview itself. refuse: replies are refused on such clients. A client that can show prompts (Claude Code) always gets the real prompt, unless MCP_CONFIRM_ELICITATION=off. An unrecognised value is treated as refuse.
MCP_CONFIRM_ELICITATIONonoff never shows a confirmation prompt, so every client gets the MCP_CONFIRM_MODE path. Set it for a client that claims to support prompts but never shows one (the reply hangs — opencode 2.0.x). Any other value stays on, with a warning on stderr.
MCP_CONFIRM_TTL_SECONDS600How long a token stays valid.
MCP_CONFIRM_SECRETrandom per processSigning key; set it only if tokens must survive a server restart.
MCP_BLOB_BASE_URL / MCP_BLOB_SIGNING_KEY—Set by mcp-host, never by hand: the per-registration upload store behind mah_upload_slots. Unset on a local install, where only base64 attachments work.

Tools

All read-only except two. mah_set_active_patient changes only which patient this connector reads — it writes nothing to any chart. mah_reply_message sends a message a provider will see, which cannot be undone: see Replying.

Every reading tool returns { patient, data }, so the chart a response belongs to is stated rather than inferred.

ToolWhat it returns
mah_list_allergiesAllergies with reactions and severity
mah_list_health_issuesThe problem list
mah_list_immunizationsImmunizations and dates, by organization
mah_list_medicationsMedications with dosing instructions (sig) and prescriber
mah_list_test_resultsLabs and imaging: name, abnormal flag, date, provider comments
mah_list_upcoming_visitsUpcoming and in-progress appointments
mah_list_past_visitsPast visits, grouped by organization
mah_list_goalsPatient goals
mah_get_health_summaryHealth-summary header and action plans
mah_list_message_foldersMessage Center folders with unread counts
mah_list_messagesMessage Center conversations for a folder, each with the conversationId to reply to
mah_reply_messageReply to a conversation as the active patient — asks you to confirm first: a prompt where the client supports one, otherwise a preview and a confirmToken *(irreversible)*
mah_upload_slotsHosted only: signed upload URLs for files to attach to a reply, named back to mah_reply_message by blobKeys. Sends nothing
mah_list_insuranceInsurance coverages on file
mah_list_care_teamCare team providers, internal and external
mah_list_billing_accountsBilling accounts and balances (parsed from HTML)
mah_healthcheckConnection health — bridge status when relaying, credential and session status when signing in server-side
mah_auth_statusWhether a session can be resumed and whether a device token is stored
mah_sign_inSign in server-side; reports verification channels if a code is needed *(needs credentials)*
mah_send_verification_codeAsk the portal to send a code to the account holder *(needs credentials)*
mah_verify_codeSubmit the code the user received *(needs credentials)*
mah_list_patientsThe patients this login can open — the account holder and any proxy subjects
mah_get_patient_contextWhich patient the readers are serving, confirmed with the portal
mah_set_active_patientPoint every reader at one of those patients; survives restarts. Through the browser bridge this switches your own tab too, and a read refuses rather than switching it back if you change patients there

Every reading tool takes view: compact (the default) or full. The raw envelopes are large — test results ~33 KB, medications ~30 KB — so compact is what you want for browsing, and full returns MyAtriumHealth's payload untouched.

compact always strips image and avatar URLs, which is subtractive and cannot drop a field nobody knew about. Ten readers additionally reduce each record to its clinically meaningful fields, because their real payloads were captured and a projection derived from them: mah_list_allergies, mah_list_health_issues, mah_list_immunizations, mah_list_medications, mah_list_care_team, mah_list_goals, mah_list_test_results, mah_list_past_visits, mah_list_insurance and mah_list_messages.

Every other reader gets the URL strip only. That field list is applied where one was actually established and nowhere else — the list above is generated from PROJECTED_ENDPOINTS and checked aga

Only the beginning is shown; read the rest in the repo