Mcp Ratchet Clinical Charting

io.github.m2ai-mcp-serversPublished by GitHub account m2ai-mcp-serversv0.1.0Updated Oct 27, 2026

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

The publisher's own server: [PREPROD] Clinical.ly Research Suite

VerifiedSTDIODesktop onlyLocation & LifestyleFiles & Storage

Overview

AI-generated overview

Local MCP server that lets Claude look up patients and write visit notes for home health charting, currently against mock data only.

What you can do
  • Search patients by name, ID or phone number
  • Create visit notes with vitals for a patient
  • Retrieve a patient's visit history
  • Runs in mock mode by default with five fictional test patients and in-memory notes
When to use it
Worth trying if you want to explore or demo AI-assisted clinical charting in Claude Desktop before real EMR integration exists. Not yet suitable for actual patient documentation, since production PointCare integration is still pending.
Requirements
Runs locally via npx with Node.js, configured in the Claude Desktop config file. Production mode needs the POINTCARE_API_URL and POINTCARE_API_KEY environment variables; without them it stays in mock mode. Optional RATCHET_MOCK_MODE and LOG_LEVEL variables.
Before you install
Production mode requires an EMR API key (POINTCARE_API_KEY) and would send patient data to the PointCare API. The server creates and stores visit notes, so writes are involved. Mock mode keeps fictional data in memory only; real EMR integration is not implemented yet.

Installation

In SourceWeft

  1. Open Mcp Ratchet Clinical Charting in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-ratchet-clinical-charting

MCP server for clinical charting with Claude (codename: Ratchet) - Enables Claude to document patient visits directly into Electronic Medical Records, reducing administrative burden for home health nurses.

Note: Currently runs in Mock Mode for development/testing. Production EMR integration coming soon.

Status

ComponentStatus
MCP Server✅ Working (Mock Mode)
Unit Tests✅ 20/20 Passing
Claude Desktop✅ Ready for Testing
PointCare API⏳ Pending API Documentation

Current Mode: Mock Mode - Uses realistic test data for development and testing.

Quick Start

From npm (Recommended)

bash
npx mcp-ratchet-clinical-charting

From Source

bash
git clone https://github.com/m2ai-mcp-servers/mcp-ratchet-clinical-charting.gitcd mcp-ratchet-clinical-chartingnpm installnpm run buildnpm run dev  # Development modenpm test     # Run tests

Mock Mode

Ratchet runs in mock mode by default when POINTCARE_API_URL is not configured. Mock mode:

  • Uses 5 fictional test patients
  • Stores visit notes in memory
  • Returns realistic responses
  • Perfect for development and Claude Desktop testing

Available Tools

ToolDescriptionMock Mode
search_patientFind patient by name, ID, or phone✅ Working
create_visit_noteDocument a patient visit with vitals✅ Working
get_patient_historyRetrieve patient visit history✅ Working

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 visit note with vitals
"Get visit history for PT-10001"→ Returns list of previous visits

Claude Desktop Integration

Configure Claude Desktop

Add to your Claude Desktop config file:

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

json
{  "mcpServers": {    "ratchet": {      "command": "npx",      "args": ["-y", "mcp-ratchet-clinical-charting"]    }  }}

For production mode with EMR integration:

json
{  "mcpServers": {    "ratchet": {      "command": "npx",      "args": ["-y", "mcp-ratchet-clinical-charting"],      "env": {        "POINTCARE_API_URL": "https://api.pointcare.com",        "POINTCARE_API_KEY": "your-api-key"      }    }  }}

Step 3: Restart Claude Desktop

Restart Claude Desktop to load the new MCP server.

Step 4: Verify

In Claude Desktop, you should see:

  • search_patient tool available
  • create_visit_note tool available
  • get_patient_history tool available

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

Origin Story

Ratchet evolved from the M2AI NurseCall n8n workflow, built to help home health nurses with visit documentation:

Current Flow (M2AI NurseCall):┌─────────┐    ┌─────────┐    ┌─────────┐    ┌─────────┐│ Twilio  │───>│  n8n    │───>│  VAPI   │───>│  Email  ││  SMS    │    │ Workflow│    │  Call   │    │ Summary │└─────────┘    └─────────┘    └─────────┘    └─────────┘

The Problem: Visit notes go to email but still need manual entry into PointCare EMR.

Ratchet's Solution:

Future Flow (with Ratchet):┌─────────┐    ┌─────────┐    ┌──────────┐    ┌───────────┐│ Twilio  │───>│  n8n    │───>│ Ratchet  │───>│ PointCare ││  SMS    │    │ Workflow│    │   MCP    │    │    EMR    │└─────────┘    └─────────┘    └──────────┘    └───────────┘

Configuration

VariableRequiredDescription
POINTCARE_API_URLNo*PointCare API base URL
POINTCARE_API_KEYNo*API key or token
RATCHET_MOCK_MODENoForce mock mode (true/false)
LOG_LEVELNoLogging level (debug/info/warn/error)

*Required for production use. Mock mode activates when not set.

Project Structure

ratchet/├── src/│   ├── index.ts              # MCP server entry point│   ├── config.ts             # Configuration management│   ├── tools/                # Tool implementations│   │   ├── search-patient.ts│   │   ├── create-visit-note.ts│   │   └── get-patient-history.ts│   ├── services/             # Business logic│   │   ├── patient-service.ts│   │   └── mock-data.ts│   ├── types/                # TypeScript types│   └── utils/                # Logger, errors├── tests/│   └── patient-service.test.ts├── dist/                     # Compiled output├── prds/│   └── RATCHET-PRD.yaml├── docs/│   └── API_REQUIREMENTS.md├── package.json├── tsconfig.json└── jest.config.js

Development

bash
# Run in watch modenpm run dev
# Run testsnpm test
# Run tests with coveragenpm test -- --coverage
# Lintnpm run lint

Next Steps

  1. Acquire PointCare API documentation - See docs/API_REQUIREMENTS.md
  2. Complete PRD - Fill in tool specifications with real API details
  3. Implement real API calls - Replace mock responses
  4. Integration testing - Test with PointCare sandbox

Related Projects

License

MIT


Built with GRIMLOCK - Autonomous MCP Server Factory

Source: README.md at commit f6a9782

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Clinical integrations