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

MCP Ratchet Clinical Charting

by m2ai-mcp-serversversion 0.1.0i★ 0iRuns on your computerRepository ↗
Registry nameio.github.m2ai-mcp-servers/mcp-ratchet-clinical-charting

How to install

What it does

MCP server for clinical charting with Claude - document patient visits to EMR

  • Connects Runs on your computer
  • Account or key Needs POINTCARE_API_KEY
  • Category Clinics & health

Why it ranks here

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

Popularity0/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 score12/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (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 MCP Ratchet Clinical Charting. Follow https://mcp.popnx.com/i/m2ai-mcp-servers-mcp-ratchet-clinical-charting.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 MCP Ratchet Clinical Charting 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 MCP Ratchet Clinical Charting 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": { "ratchet-clinical-charting": { "command": "npx", "args": [ "-y", "mcp-ratchet-clinical-charting" ], "env": { "POINTCARE_API_KEY": "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 POINTCARE_API_KEY, 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 MCP Ratchet Clinical Charting 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 MCP Ratchet Clinical Charting 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": {
        "ratchet-clinical-charting": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-ratchet-clinical-charting"
          ],
          "env": {
            "POINTCARE_API_KEY": "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 MCP Ratchet Clinical Charting and tell me what you can do for me, then show me one thing

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

1 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.

  • POINTCARE_API_URL EMR API base URL (optional - runs in mock mode if not set)

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 MCP Ratchet Clinical Charting yet

MCP Ratchet Clinical Charting 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 MCP Ratchet Clinical Charting

  • You need a MCP Ratchet Clinical Charting 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 MCP Ratchet Clinical Charting key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a MCP Ratchet Clinical Charting key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a MCP Ratchet Clinical Charting key (create it on the maker’s site) · Install Node.js on your computer first (one time)

B · Others in Clinics & health 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 MCP Ratchet Clinical Charting 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 MCP Ratchet Clinical Charting 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 ratchet-clinical-charting --env POINTCARE_API_KEY=your-value -- npx -y mcp-ratchet-clinical-charting 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 POINTCARE_API_KEY, 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 MCP Ratchet Clinical Charting 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 MCP Ratchet Clinical Charting 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 ratchet-clinical-charting --env POINTCARE_API_KEY=your-value -- npx -y mcp-ratchet-clinical-charting

    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 MCP Ratchet Clinical Charting listed as connected

  6. Try it

    Use MCP Ratchet Clinical Charting and tell me what you can do for me, then show me one thing

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

1 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.

  • POINTCARE_API_URL EMR API base URL (optional - runs in mock mode if not set)

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 MCP Ratchet Clinical Charting 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 MCP Ratchet Clinical Charting 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": { "ratchet-clinical-charting": { "command": "npx", "args": [ "-y", "mcp-ratchet-clinical-charting" ], "env": { "POINTCARE_API_KEY": "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 POINTCARE_API_KEY, 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 MCP Ratchet Clinical Charting 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 MCP Ratchet Clinical Charting 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 MCP Ratchet Clinical Charting settings, POINTCARE_API_KEY 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 MCP Ratchet Clinical Charting and tell me what you can do for me, then show me one thing

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

1 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.

  • POINTCARE_API_URL EMR API base URL (optional - runs in mock mode if not set)

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 MCP Ratchet Clinical Charting 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 MCP Ratchet Clinical Charting 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": { "ratchet-clinical-charting": { "type": "stdio", "command": "npx", "args": [ "-y", "mcp-ratchet-clinical-charting" ], "env": { "POINTCARE_API_KEY": "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 POINTCARE_API_KEY, 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 MCP Ratchet Clinical Charting 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 MCP Ratchet Clinical Charting 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 MCP Ratchet Clinical Charting settings, POINTCARE_API_KEY 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 MCP Ratchet Clinical Charting and tell me what you can do for me, then show me one thing

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

1 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.

  • POINTCARE_API_URL EMR API base URL (optional - runs in mock mode if not set)

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 MCP Ratchet Clinical Charting💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user ratchet-clinical-charting --env POINTCARE_API_KEY=your-value -- npx -y mcp-ratchet-clinical-charting

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "ratchet-clinical-charting": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ratchet-clinical-charting"
      ],
      "env": {
        "POINTCARE_API_KEY": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "ratchet-clinical-charting": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ratchet-clinical-charting"
      ],
      "env": {
        "POINTCARE_API_KEY": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "ratchet-clinical-charting": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-ratchet-clinical-charting"
      ],
      "env": {
        "POINTCARE_API_KEY": "your-value"
      }
    }
  }
}

Values you fill in

  • POINTCARE_API_URL env
    EMR API base URL (optional - runs in mock mode if not set)
  • POINTCARE_API_KEY secret required env
    EMR API key (required for production mode)

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
55/wk
Connection
Runs on your computer
Latest versioni
0.1.0
Published to registryi
Jan 20, 2026
Code last changedi
Nov 14, 2026
Maker
m2ai-mcp-servers
Packages
npm: mcp-ratchet-clinical-charting
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 m2ai-mcp-servers, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 6 days ago

  • ✓ 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 mcp-ratchet-clinical-charting@0.1.0

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/m2ai-mcp-servers-mcp-ratchet-clinical-charting.svg)](https://mcp.popnx.com/en/servers/m2ai-mcp-servers-mcp-ratchet-clinical-charting)

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 Clinics & healthi

  • More stars than 0% of the other 1193 servers in this category
  • Published to the registry more recently than 0% of the other 1193 servers in this category
  • Basic checks equal to or better than 99% of the other 1193 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 MCP Ratchet Clinical Charting 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: POINTCARE_API_KEY

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 6 days ago, and the latest version (0.1.0) reached the registry 10 months 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: Medplum MCP, Mirobody, Codescene MCP Server, Marrow, WHOOP — MissingMCP

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

Medplum MCP

Securely access and manage FHIR healthcare data stored in Medplum.

by medplumWidely used★ 2.8KUpdated 4 months ago

Runs in the cloud✓ service owner · medplum.com

Mirobody

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

by thetahealthGrowing↓ 725/wk★ 1.6KUpdated yesterday

Runs on your computer✓ thetahealth.ai

Codescene MCP Server

An MCP server that provides CodeScene Code Health analysis tools.

by codescene-ossGrowing↓ 3.8K/wk★ 85Updated 8 months ago

Runs on your computer✓ service owner · codescene.com

Marrow

Marrow Health: your Apple Health data over MCP, from the free iOS app. Reads, and writes on demand.

by skeletonarmytechEarly↓ 62/wk★ 5Updated 29 days ago

Runs on your computer✓ skeletonarmy.tech
Compared with similar ones
This one
MCP Ratchet Clinical Charting
Medplum MCPMirobodyCodescene MCP ServerMarrowWHOOP — MissingMCP
Runs whereInstalls on your computerRuns in the cloud, nothing to installInstalls on your computerInstalls on your computerInstalls on your computerRuns in the cloud, nothing to install
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/43/32/33/32/4
LicenseMITApache-2.0Apache-2.0NOASSERTIONMITMIT
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.

chartinghero

MCP server for clinical charting with Claude. Lets Claude search patients, document home health visits (SOAP note, vitals, interventions, education) and read visit history.

Status: the mock backend is complete. The FHIR R4 (US Core) backend can search patients and read visit history; it cannot write yet. See docs/FHIR-PIVOT-PLAN.md. Do not use with real patient data.

Status

ComponentStatus
MCP server (stdio)Working, mock backend
Unit testsnpm test
FHIR R4 backend, read (search_patient, get_patient_history)Working against a local or sandbox FHIR R4 server
FHIR R4 backend, write (create_visit_note)Not in this build; the call is refused
Production EMR writesOut of scope until SMART user auth (0.3.0)

Quick start

From npm

The 0.1.0 npm release was published under an earlier package name, which will be deprecated. Until chartinghero is published, install from source.

From source
git clone https://github.com/m2ai-mcp-servers/chartinghero.git

cd chartinghero npm install npm run build npm test

Mock mode

Mock mode is the default backend. It:

  • uses 5 fictional test patients
  • stores visit notes in memory (lost on restart)
  • saves new notes as pending_review, unsigned, authored by a fictional nurse
  • prefixes every tool result with [MOCK DATA: fictional patients]

FHIR mode (read only)

With BACKEND=fhir the server reads from a FHIR R4 server:

  • At startup it reads /metadata and stops unless fhirVersion starts with 4.0.
  • search_patient looks up the PT-xxxxx identifier, the server id, the name (every word must match; add a YYYY-MM-DD date of birth to narrow it) and the phone number when the server supports phone search. A phone number matches as the server stores it; the digits-only spelling is tried as well.
  • get_patient_history lists home health Encounters newest first. A visit with an unsigned note is pending_review, and so is one whose status the server reports as unknown; with a signed note it is completed. A visit with no note takes the Encounter's own status, and a cancelled visit stays cancelled. Encounters entered in error are left out. Vitals count when they are linked to the visit or were taken during it.
  • When the server cannot return notes and vitals with the Encounters, history is built from the nurse notes instead: one row per visit, with no visit type.
  • Results come one page at a time; a result with more pages includes a cursor to pass back. A cursor keeps the filters and page size it was issued with. A total shown as 3+ counts only the pages read so far. The order across pages is the server's (_sort=-date).
  • create_visit_note is refused. With FHIR_WRITE=on it still resolves the patient and runs the duplicate-visit search, then stops. A note-only write (no Encounter) is refused outright until it has a duplicate check of its own.
  • A bearer token is only sent over https, or over http to a loopback address.

The server only trusts what it can check: it filters results again itself, follows paging links only under FHIR_BASE_URL, refuses redirects, and reports upstream errors by HTTP status and issue code only.

Local FHIR server
docker compose -f docker/compose.fhir.yml up -d   # HAPI FHIR R4 on 127.0.0.1:8080, data in memory

node scripts/seed-fhir.mjs # fictional patients, visits, vitals and notes (waits for the server to come up)

Then run with BACKEND=fhir FHIR_BASE_URL=http://127.0.0.1:8080/fhir FHIR_ENVIRONMENT=local FHIR_PRACTITIONER_ID= VISIT_TIMEZONE=America/New_York. Restarting the container wipes its data.

Tools

ToolDescription
search_patientFind a patient by name, ID, or phone
create_visit_noteDocument a visit with vitals and a SOAP note
get_patient_historyList a patient's previous visits
Example usage (in Claude)
"Search for patient Eleanor Thompson"

→ Returns patient PT-10001 with demographics and status

"Create a visit note for PT-10001 with blood pressure 120/80" → Creates and stores the visit note with vitals

"Get visit history for PT-10001" → Returns the list of previous visits

Claude Desktop

Add to the Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{

"mcpServers": { "chartinghero": { "command": "node", "args": ["/absolute/path/to/chartinghero/dist/index.js"] } } }

Restart Claude Desktop, then check that search_patient, create_visit_note and get_patient_history are listed. Try: "Search for patient Eleanor".

Test patients (mock mode)

IDNameStatusPrimary diagnosis
PT-10001Eleanor ThompsonActiveType 2 Diabetes, CHF
PT-10002Robert MartinezActiveCOPD, Post-surgical
PT-10003Margaret WilsonActiveParkinson's Disease
PT-10004James ThompsonActivePost-stroke rehab
PT-10005Dorothy AndersonDischargedHip replacement

Configuration

Config fails closed: an invalid value stops the server at startup with a message naming the variable.

VariableRequiredDescription
BACKENDWhen any FHIR_* var is setmock or fhir. Unset with no FHIR_* vars means mock, with a stderr banner.
FHIR_BASE_URL, FHIR_ENVIRONMENT, FHIR_PRACTITIONER_ID, VISIT_TIMEZONEWhen BACKEND=fhirFHIR server, local or sandbox, authoring Practitioner id, IANA time zone.
FHIR_WRITENooff (default) or on. on is refused unless the host is in WRITE_HOSTS (src/config/hosts.ts).
FHIR_WRITE_PROFILE, FHIR_BEARER_TOKEN, FHIR_IDENTIFIER_SYSTEMNofull or note-only; static token; identifier namespace.
DASHBOARD_SYNCNooff (default) or on. With on and the mock backend, new notes are copied to the demo dashboard via SUPABASE_URL and SUPABASE_ANON_KEY. Synthetic data only.
LOG_LEVELNodebug, info, warn or error

Variables from the 0.1.0 release are still read for one release with a deprecation warning, but no longer select a backend.

Project structure

chartinghero/

├── src/ │ ├── index.ts # MCP server entry point │ ├── config.ts # Fail-closed configuration │ ├── config/hosts.ts # WRITE_HOSTS allowlist │ ├── legacy-env.ts # Deprecated 0.1.0 env vars (one release) │ ├── backends/ # PatientBackend seam, mock backend, factory, signed paging cursors │ ├── backends/fhir/ # FHIR client, /metadata capabilities, read path, write pre-flight │ ├── auth/ # none, static bearer token │ ├── mappers/ # DTO mappers │ ├── tools/ # search-patient, create-visit-note, get-patient-history │ ├── services/ # patient-service (validation + projection hook), mock-data, supabase-service │ ├── types/ # Patient and visit types │ └── utils/ # Logger, errors ├── tests/ # service, config, startup, backends/ (in-memory FHIR server), contract/ (both backends) ├── docker/compose.fhir.yml # local FHIR R4 server ├── scripts/seed-fhir.mjs # fictional seed data for it ├── docs/ │ └── FHIR-PIVOT-PLAN.md # Backend pivot plan ├── package.json ├── tsconfig.json └── jest.config.js

Development

npm run dev    # run with tsx

npm test # jest npm run lint # eslint

npx jest tests/contract runs one contract against both backends. The FHIR side replays recorded responses by default. To run it against the local server, seed it and set FHIR_IT_BASE_URL=http://127.0.0.1:8080/fhir; add FHIR_RECORD=1 to rewrite the recordings in tests/fixtures/recorded/.

Related projects

  • [chartinghero-demo-emr](https://github.com/m2ai-mcp-servers/chartinghero-demo-emr): demo EMR dashboard that displays visits written by this server.

License

MIT