How do I install Rxlocal?

Rxlocal is a local plugin. Install it using npm package: rxlocal-mcp and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Rxlocal safe to use?

Yes. Rxlocal passed MCP Marketplace's automated security scan with a score of 8.3/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What credentials does Rxlocal need?

Rxlocal requires the following credentials or environment variables: RXLOCAL_DISABLE_FETCHPROXY, FETCHPROXY_WS_PORT, FETCHPROXY_WS_HOST, FETCHPROXY_IDENTITY_DIR. You can find setup instructions on the server detail page.

What AI apps work with Rxlocal?

Rxlocal uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Rxlocal MCP Server

by Chris Hall

Developer ToolsLow Risk8.3Local

Free

RxLocal (PioneerRx/RedSail) pharmacy portal MCP — profile, age gate, notifications, legal docs

About

RxLocal (PioneerRx/RedSail) pharmacy portal MCP — profile, age gate, notifications, legal docs

Security Report

8.3

Low Risk8.3Low Risk

Valid MCP server (2 strong, 1 medium validity signals). 3 known CVEs in dependencies (0 critical, 2 high severity) Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (152/154 approved); 4 highly-trusted packages.

7 files analyzed · 4 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

file_system

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Set to 1/true to refuse the fetchproxy bridge read (CI/headless). Tools then fail instead of reading a session. Defaults to false.Optional

Environment variable: RXLOCAL_DISABLE_FETCHPROXY

Localhost port of the fetchproxy concentrator the ContextMint Bridge connects to (default 37149). Shared by every MCP on the machine.Optional

Environment variable: FETCHPROXY_WS_PORT

Bind interface for the fetchproxy concentrator, a literal IP only (default 127.0.0.1). Keep on loopback.Optional

Environment variable: FETCHPROXY_WS_HOST

Absolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/).Optional

Environment variable: FETCHPROXY_IDENTITY_DIR

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-chrischall-rxlocal-mcp": {
      "env": {
        "FETCHPROXY_WS_HOST": "your-fetchproxy-ws-host-here",
        "FETCHPROXY_WS_PORT": "your-fetchproxy-ws-port-here",
        "FETCHPROXY_IDENTITY_DIR": "your-fetchproxy-identity-dir-here",
        "RXLOCAL_DISABLE_FETCHPROXY": "your-rxlocal-disable-fetchproxy-here"
      },
      "args": [
        "-y",
        "rxlocal-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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.

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/<groupOwnerID>/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

Reviews

No reviews yet

Be the first to review this server!

4.8

Local

MCP Marketplace

Free

by mcp-marketplace · Developer Tools

Search and install MCP servers from inside your AI client.