Rxlocal MCP

Name: Rxlocal MCP
Author: chrischall

作者：chrischall版本 0.3.1i★ –i在你的电脑上运行

注册名称io.github.chrischall/rxlocal-mcp

安装

概览

作者提供的说明（英文原文）

RxLocal pharmacy portal MCP — prescriptions, messages, confirm-gated refill requests

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 诊所与健康

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： RXLOCAL_DISABLE_FETCHPROXY, FETCHPROXY_WS_PORT, FETCHPROXY_WS_HOST, FETCHPROXY_IDENTITY_DIR

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "rxlocal": {
      "command": "npx",
      "args": [
        "-y",
        "rxlocal-mcp"
      ],
      "env": {
        "RXLOCAL_DISABLE_FETCHPROXY": "your-value",
        "FETCHPROXY_WS_PORT": "your-value",
        "FETCHPROXY_WS_HOST": "your-value",
        "FETCHPROXY_IDENTITY_DIR": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add rxlocal --env RXLOCAL_DISABLE_FETCHPROXY=your-value --env FETCHPROXY_WS_PORT=your-value --env FETCHPROXY_WS_HOST=your-value --env FETCHPROXY_IDENTITY_DIR=your-value -- npx -y rxlocal-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "rxlocal": {
      "command": "npx",
      "args": [
        "-y",
        "rxlocal-mcp"
      ],
      "env": {
        "RXLOCAL_DISABLE_FETCHPROXY": "your-value",
        "FETCHPROXY_WS_PORT": "your-value",
        "FETCHPROXY_WS_HOST": "your-value",
        "FETCHPROXY_IDENTITY_DIR": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "rxlocal": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "rxlocal-mcp"
      ],
      "env": {
        "RXLOCAL_DISABLE_FETCHPROXY": "your-value",
        "FETCHPROXY_WS_PORT": "your-value",
        "FETCHPROXY_WS_HOST": "your-value",
        "FETCHPROXY_IDENTITY_DIR": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

RXLOCAL_DISABLE_FETCHPROXY env
Set to 1/true to refuse the fetchproxy bridge read (CI/headless). Tools then fail instead of reading a session. Defaults to false.
FETCHPROXY_WS_PORT env
Localhost port of the fetchproxy concentrator the ContextMint Bridge connects to (default 37149). Shared by every MCP on the machine.
FETCHPROXY_WS_HOST env
Bind interface for the fetchproxy concentrator, a literal IP only (default 127.0.0.1). Keep on loopback.
FETCHPROXY_IDENTITY_DIR env
Absolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/).

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 chrischall 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“诊所与健康”中的其他服务器比较i

星标数多于此分类中其他 1022 个服务器的 0%
发布到注册中心的时间比此分类中其他 1022 个服务器的 88% 更新
基础检查结果等于或优于此分类中其他 1022 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Rxlocal MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.3.1）于3天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Mirobody, FHIR MCP Server, Google Health MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Mirobody

作者：thetahealth

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

在你的电脑上运行★ 1,408Apache-2.0今天更新

安装

FHIR MCP Server

作者：wso2

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

在你的电脑上运行★ 137Apache-2.010天前更新

安装

Google Health MCP

作者：davidmosiah

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

在你的电脑上运行★ 79MIT4个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

rxlocal-mcp

MCP server for the RxLocal pharmacy patient portal (patient.rxlocal.com, PioneerRx / RedSail Technologies). It reads your prescriptions, refill options and pharmacy messages, and can request refills and message the pharmacy behind a confirm gate, through your signed-in browser tab, reusing your authenticated session via the fetchproxy bridge.

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

What it can read

Tool	Returns
`rxlocal_list_prescriptions`	Prescriptions on file: drug, Rx number, rxID, pharmacy, last fill, refills remaining, days supply, expiration, prescriber, and whether a refill can be requested now (`canRequestRefill`) or needs a renewal (`requiresRenewal`). `view: full` adds NDC, imprint and ids; `view: raw` is the whole response.
`rxlocal_get_refill_options`	What a refill request can choose at a pharmacy location: pickup / delivery / mail, pickup times, the pickup calendar, the pharmacy's address, phone and hours, and its refill disclaimers. Your own addresses and phone are only in `view: full`/`raw`.
`rxlocal_list_messages`	Recent secure messages with the pharmacy, newest first. Never marks anything read; recipient email/phone are always removed.
`rxlocal_profile`	Account holder's name, email, phone, account type, patient + user IDs
`rxlocal_age_gate`	Whether the account holder is under the portal's minimum age
`rxlocal_notifications`	The portal's most-relevant notification banner state
`rxlocal_legal`	The Terms of Use or Privacy Policy document
`rxlocal_healthcheck`	Whether the session and API are working

Pharmacy-written text (message bodies, refill disclaimers) comes back inside an untrusted-content envelope: it is data, never instructions.

How it reaches your data

The bridge reads two things from your signed-in tab: the short-lived bearer the web app holds, and the tab's session-id cookie. The server then calls the API itself, adding the portal's public portalid header (the web app's patientPortalID constant, sent on every request). Prescriptions and messages need all three; without the header or the cookie they answer 401. Earlier versions sent neither and concluded the data was unreachable; it is not (verified live, read-only, 2026-10-29).

The server reuses the tab's session and never opens one of its own: the portal keeps one session per user, and starting a new one signs your browser out. After a 401 it re-reads the tab on the next call, so reloading the tab is enough.

Writes

Tool Does

rxlocal_request_refill Requests a refill, or a prescriber renewal for a prescription that needs one, of one or more of your prescriptions. You choose pickup, delivery or mail and, for pickup, a time and date. It is checked against the live refill list (each must show canRequestRefill) and that location's options and pickup calendar before the preview. All prescriptions in one request must be yours and at one location.

rxlocal_send_message Sends a plain-text secure message to your primary pharmacy location. No attachments.

UNVERIFIED on the wire. Both sends are derived from the RxLocal web app's JavaScript bundle (POST refill/ /v1 and POST Messaging/CreatePatientMessage). Neither has been sent to the live portal yet. An owner-supervised live test will confirm them later. Until then, check the result with rxlocal_list_prescriptions (refillRequestStatus) or rxlocal_list_messages.

Each write is sent once. It is never retried on a 429, and a 401 fails without re-reading the token or replaying the request. If a write was sent but the answer was a 5xx, a timeout or a dropped connection, the tool reports status: "unknown". That means it may already have gone through, so check before trying again.

Confirm gate

Every write is gated by @chrischall/mcp-utils' confirmWrite, through its defineWrite / registerWrite. The first call reads the portal to validate, sends nothing, and returns a preview + a `confirmToken`. Only a second call carrying that token sends, and only after you approve the preview. The exact request body and the shown preview are bound into the token, so an argument or portal state that changed since the preview is refused as DRAFT_CHANGED. MCP_CONFIRM_MODE / MCP_CONFIRM_ELICITATION tune this (see the env table).

Setup

No credential is configured in the environment — the server reads the short-lived Keycloak token from the signed-in tab via the ContextMint Bridge browser extension. Install the extension, sign in to patient.rxlocal.com, keep that tab open, and approve the one-time pair code the first tool call prints.

// .mcp.json

{ "mcpServers": { "rxlocal": { "command": "npx", "args": ["-y", "rxlocal-mcp"] } } }

Environment variables (all optional)

Variable	Purpose
`RXLOCAL_DISABLE_FETCHPROXY`	Set to `1` to refuse the browser-bridge read (CI/headless). Every tool then fails, since there is no other credential path.
`FETCHPROXY_WS_PORT`	Localhost port of the fetchproxy concentrator the extension connects to (default `37149`). Shared by every MCP on the machine.
`FETCHPROXY_WS_HOST`	Bind interface for the concentrator, a literal IP (default `127.0.0.1`).
`FETCHPROXY_IDENTITY_DIR`	Where the fetchproxy identity keypair is stored (default `~/.fetchproxy/identity/`).
`MCP_CONFIRM_MODE`	Confirm-gate mode for every write (default `ask-user`). `ask-user` = preview + `confirmToken` round-trip; `auto` lets a capable host confirm in one step; an unrecognised value fails closed (`refuse`).
`MCP_CONFIRM_ELICITATION`	`on` (default) lets the host confirm a write interactively; `off` forces the `confirmToken` round-trip.

Shell-only alternative

A lightweight fpx skill ships under skills/rxlocal-fpx/, with no MCP process required. It covers the reads: profile, age gate, prescriptions, refill options, messages and notifications. It sends nothing.

Development

npm install

npm run build npm test # typecheck + vitest, fully mocked, no network