@chrischall/myatriumhealth-mcp 0.0.0 → 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -6,16 +6,16 @@
6
6
  "email": "chris.c.hall@gmail.com"
7
7
  },
8
8
  "metadata": {
9
- "description": "MCP server for Angi \u2014 find home-service pros by trade and city, read ratings, reviews and pro profiles. Angi serves its pages only to a real browser, so requests route through the user's own angi.com tab via the fetchproxy browser extension, reusing their existing session. The trade/city taxonomy is read from Angi's public sitemaps directly.",
10
- "version": "0.0.0"
9
+ "description": "MCP server for Angi — find home-service pros by trade and city, read ratings, reviews and pro profiles. Angi serves its pages only to a real browser, so requests route through the user's own angi.com tab via the fetchproxy browser extension, reusing their existing session. The trade/city taxonomy is read from Angi's public sitemaps directly.",
10
+ "version": "0.1.0"
11
11
  },
12
12
  "plugins": [
13
13
  {
14
14
  "name": "myatriumhealth-mcp",
15
15
  "displayName": "MyAtriumHealth",
16
16
  "source": "./",
17
- "description": "Read MyAtriumHealth (Epic MyChart) records \u2014 test results, medications, allergies, immunizations, health issues, visits \u2014 by relaying requests through the user's signed-in browser tab via the fetchproxy bridge.",
18
- "version": "0.0.0",
17
+ "description": "Read MyAtriumHealth (Epic MyChart) records — test results, medications, allergies, immunizations, health issues, visits — by relaying requests through the user's signed-in browser tab via the fetchproxy bridge.",
18
+ "version": "0.1.0",
19
19
  "author": {
20
20
  "name": "Chris Hall"
21
21
  },
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "name": "myatriumhealth-mcp",
3
3
  "displayName": "MyAtriumHealth",
4
- "version": "0.0.0",
5
- "description": "MyAtriumHealth (Epic MyChart) access for Claude \u2014 test results, medications, allergies, immunizations, visits",
4
+ "version": "0.1.0",
5
+ "description": "MyAtriumHealth (Epic MyChart) access for Claude — test results, medications, allergies, immunizations, visits",
6
6
  "author": {
7
7
  "name": "Chris Hall",
8
8
  "email": "chris.c.hall@gmail.com"
package/README.md CHANGED
@@ -7,6 +7,40 @@ immunizations, health issues, goals and visits.
7
7
  > This project was developed and is maintained by AI. Use at your own discretion.
8
8
  > It reads personal health information, and only ever from the signed-in user's own account.
9
9
 
10
+ ## Two ways to authenticate
11
+
12
+ | Mode | When | Credentials held |
13
+ |---|---|---|
14
+ | **Browser bridge** (default) | no credentials configured | **none** |
15
+ | **Bridge-less** | `MAH_USERNAME` + `MAH_PASSWORD` set | your portal password, on disk |
16
+
17
+ Bridge-less logs in server-side — no browser, no extension — which is what makes
18
+ hosting possible. Verification is **human-in-the-loop**: the portal challenges,
19
+ `mah_sign_in` reports the channels your account allows, the portal sends a code to
20
+ **you**, and `mah_verify_code` submits only what you provide. Nothing here bypasses the
21
+ second factor.
22
+
23
+ **When the session expires** you do *not* reconnect the MCP or restart anything. The
24
+ next tool call returns an actionable error naming the channels and your masked
25
+ destinations; you pick one, the portal texts or emails **you**, and `mah_verify_code`
26
+ resumes the session in place. A pending challenge is remembered, so further tool calls
27
+ report it rather than re-submitting your password each time.
28
+
29
+ **How the session persists.** After one verification the cookie jar is stored (0600,
30
+ bound to the account) and reused, so restarts resume the existing session rather than
31
+ signing in again — no browser and no further codes until the session lapses.
32
+
33
+ > **What does NOT work, measured rather than assumed:** the `RememberDeviceId` this
34
+ > portal returns is *not* a device-tracking id it will accept back. Sending it neither
35
+ > skips verification nor is harmless — it breaks the challenge, leaving the
36
+ > SecondaryValidation page without its `templateContext` so the antiforgery token
37
+ > cannot be read and `SendCode` returns 500. The account reports
38
+ > `RememberMeSettings.EnrollDeviceTracking: False`, which fits. The token is therefore
39
+ > stored but deliberately never sent.
40
+
41
+ The bridge mode's real virtue is that it holds **no credentials at all**. Prefer it
42
+ unless you specifically need bridge-less.
43
+
10
44
  ## How it works
11
45
 
12
46
  Every MyChart cookie is `HttpOnly` and login is MFA-gated, so the session cannot be
@@ -39,7 +73,10 @@ call prints a pair code — approve it once in the Transporter popup.
39
73
 
40
74
  | Env | Default | Purpose |
41
75
  |---|---|---|
42
- | `MAH_WS_PORT` | `37149` | fetchproxy concentrator port. The whole fleet shares this one port; override only when hosting. |
76
+ | `MAH_USERNAME` | — | MyAtriumHealth username. Set **with** `MAH_PASSWORD` to enable bridge-less mode. |
77
+ | `MAH_PASSWORD` | — | Portal password. Both are required; setting only one falls back to the bridge (with a warning). |
78
+ | `MAH_DEVICE_FILE` | `~/.myatriumhealth-mcp/device.json` | Session state (0600). Holds the **live cookie jar** as well as the device token — treat as a credential. |
79
+ | `MAH_WS_PORT` | `37149` | fetchproxy concentrator port (bridge mode only). The whole fleet shares this one port; override only when hosting. |
43
80
 
44
81
  ## Tools
45
82
 
@@ -57,8 +94,16 @@ All read-only — this surface exposes no writes.
57
94
  | `mah_list_goals` | Patient goals |
58
95
  | `mah_get_health_summary` | Health-summary header and action plans |
59
96
  | `mah_list_message_folders` | Message Center folders with unread counts |
97
+ | `mah_list_messages` | Message Center conversations for a folder |
98
+ | `mah_list_insurance` | Insurance coverages on file |
99
+ | `mah_list_care_team` | Care team providers, internal and external |
100
+ | `mah_list_billing_accounts` | Billing accounts and balances (parsed from HTML) |
60
101
  | `mah_get_menu` | Which portal features this account exposes |
61
- | `mah_healthcheck` | Bridge health, and whether the portal session is signed in |
102
+ | `mah_healthcheck` | Connection health — bridge status, or credential/session status in bridge-less mode |
103
+ | `mah_auth_status` | Whether a session can be resumed and whether a device token is stored *(bridge-less only)* |
104
+ | `mah_sign_in` | Sign in server-side; reports verification channels if a code is needed *(bridge-less only)* |
105
+ | `mah_send_verification_code` | Ask the portal to send a code to the account holder *(bridge-less only)* |
106
+ | `mah_verify_code` | Submit the code the user received *(bridge-less only)* |
62
107
 
63
108
  Listing tools take `compact` (default `false`). The raw envelopes are large — test
64
109
  results ~33 KB, medications ~30 KB — so pass `compact: true` when browsing. If the
@@ -78,11 +123,15 @@ in again between uses.
78
123
  shell with the `fpx` CLI — no server to run. Its `references/endpoints.md` carries
79
124
  live-verified `jq` recipes for every endpoint here.
80
125
 
81
- ## Known gap
126
+ ## Messages
127
+
128
+ `mah_list_messages` is the one endpoint that cannot be called with an empty body. It
129
+ needs a five-key request whose `PageNonce` is the CSP nonce of an `/app/*` page, and
130
+ whose `externalLoadParams` lists the **non-local** organizations only — passing the
131
+ local organization returns HTTP 500. The client assembles this from
132
+ `conversations/GetOrganizations` and its explicit `isLocal` flag.
82
133
 
83
- The message list (`api/conversations/GetConversationList`) is not yet reachable: it
84
- needs a page nonce plus organization handles that have not been pinned down. See
85
- `docs/MYATRIUMHEALTH-API.md`.
134
+ `api/item-feed/FetchItemFeed` still needs parameters that have not been captured.
86
135
 
87
136
  ## Development
88
137