Medplum MCP
Securely access and manage FHIR healthcare data stored in Medplum.
MCP server for clinical charting with Claude - document patient visits to EMR
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
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
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.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: 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
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
SettingsDeveloperEdit Config
{
"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
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
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
A · Use an app that can connect MCP Ratchet Clinical Charting
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)
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.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: 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
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
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user ratchet-clinical-charting --env POINTCARE_API_KEY=your-value -- npx -y mcp-ratchet-clinical-chartingReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see MCP Ratchet Clinical Charting listed as connected
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
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)
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.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: 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
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
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
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
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)
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.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: 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
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
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
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
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.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user ratchet-clinical-charting --env POINTCARE_API_KEY=your-value -- npx -y mcp-ratchet-clinical-chartingClaude 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"
}
}
}
}POINTCARE_API_URL envPOINTCARE_API_KEY secret required envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
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
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account m2ai-mcp-servers, which owns the repo
Code last changed 6 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
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
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/m2ai-mcp-servers-mcp-ratchet-clinical-charting)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.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: POINTCARE_API_KEY
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).
The GitHub repo last changed 6 days ago, and the latest version (0.1.0) reached the registry 10 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Medplum MCP, Mirobody, Codescene MCP Server, Marrow, WHOOP — MissingMCP
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
Securely access and manage FHIR healthcare data stored in Medplum.
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
An MCP server that provides CodeScene Code Health analysis tools.
Marrow Health: your Apple Health data over MCP, from the free iOS app. Reads, and writes on demand.
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
| This one MCP Ratchet Clinical Charting | Medplum MCP | Mirobody | Codescene MCP Server | Marrow | WHOOP — MissingMCP | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Installs on your computer | Installs on your computer | Installs on your computer | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 3/3 | 2/3 | 3/3 | 2/4 |
| License | MIT | Apache-2.0 | Apache-2.0 | NOASSERTION | MIT | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
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.
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.
| Component | Status |
|---|---|
| MCP server (stdio) | Working, mock backend |
| Unit tests | npm 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 writes | Out of scope until SMART user auth (0.3.0) |
The 0.1.0 npm release was published under an earlier package name, which will be deprecated. Until chartinghero is published, install from source.
git clone https://github.com/m2ai-mcp-servers/chartinghero.git
cd chartinghero npm install npm run build npm test
Mock mode is the default backend. It:
pending_review, unsigned, authored by a fictional nurse[MOCK DATA: fictional patients]With BACKEND=fhir the server reads from a FHIR R4 server:
/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.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.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.
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.
| Tool | Description |
|---|---|
search_patient | Find a patient by name, ID, or phone |
create_visit_note | Document a visit with vitals and a SOAP note |
get_patient_history | List a patient's previous visits |
"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
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".
| ID | Name | Status | Primary diagnosis |
|---|---|---|---|
| PT-10001 | Eleanor Thompson | Active | Type 2 Diabetes, CHF |
| PT-10002 | Robert Martinez | Active | COPD, Post-surgical |
| PT-10003 | Margaret Wilson | Active | Parkinson's Disease |
| PT-10004 | James Thompson | Active | Post-stroke rehab |
| PT-10005 | Dorothy Anderson | Discharged | Hip replacement |
Config fails closed: an invalid value stops the server at startup with a message naming the variable.
| Variable | Required | Description |
|---|---|---|
BACKEND | When any FHIR_* var is set | mock or fhir. Unset with no FHIR_* vars means mock, with a stderr banner. |
FHIR_BASE_URL, FHIR_ENVIRONMENT, FHIR_PRACTITIONER_ID, VISIT_TIMEZONE | When BACKEND=fhir | FHIR server, local or sandbox, authoring Practitioner id, IANA time zone. |
FHIR_WRITE | No | off (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_SYSTEM | No | full or note-only; static token; identifier namespace. |
DASHBOARD_SYNC | No | off (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_LEVEL | No | debug, 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.
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
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/.
MIT