MCP Ratchet Clinical Charting logo

MCP Ratchet Clinical Charting

Mock-mode MCP server for searching patients, creating visit notes, and retrieving clinical history.

Install MCP Ratchet Clinical Charting

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-ratchet-clinical-charting": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ratchet-clinical-charting"
      ],
      "env": {
        "POINTCARE_API_URL": "YOUR_VALUE_HERE",
        "POINTCARE_API_KEY": "YOUR_VALUE_HERE",
        "RATCHET_MOCK_MODE": "YOUR_VALUE_HERE",
        "LOG_LEVEL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The mcp-ratchet-clinical-charting MCP server gives Claude tools for patient lookup, visit-note creation, and visit-history retrieval. It runs in mock mode by default, using five fictional patients and in-memory notes for development and testing. PointCare EMR integration is planned and requires PointCare configuration when supported. Reach for it when testing conversational clinical charting workflows or evaluating Claude Desktop integration without a production EMR.

Use cases

  • Test conversational patient lookup with fictional records
  • Create sample visit notes with vitals
  • Retrieve mock patient visit histories
  • Evaluate Claude Desktop MCP configuration
  • Prototype a future PointCare documentation workflow

Key features

  • Patient search by name, ID, or phone
  • Visit-note creation with vitals
  • Patient visit-history retrieval
  • Mock mode with five fictional patients
  • In-memory storage for test notes
  • Configurable PointCare and logging settings

Tools3

What MCP Ratchet Clinical Charting lets your agent do. Expand a tool for its parameters.

Self-reported~38 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

7/7 checks healthy over the last 42d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · mcp-ratchet-clinical-charting (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads120Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Tools exposed3Callable tools this server registers over MCP.

How MCP Ratchet Clinical Charting works

What mcp-ratchet-clinical-charting does

The mcp-ratchet-clinical-charting MCP server exposes three clinical charting operations through MCP. search_patient finds a patient using a name, patient ID, or phone number. create_visit_note records a visit and its vitals. get_patient_history returns prior visits for a selected patient.

The project is intended for home health documentation workflows. Its stated goal is to let Claude help document visits instead of leaving summaries in email for manual entry into an electronic medical record. The repository describes a future workflow connecting Ratchet with PointCare, but the current implementation does not provide a production EMR connection.

How it works

When started without a PointCare API URL, the mcp-ratchet-clinical-charting MCP server uses mock mode. This mode supplies five fictional test patients, returns realistic-looking responses, and keeps newly created visit notes in memory. Data therefore supports testing during the running process rather than persistent clinical record storage.

A typical interaction begins with a patient search. After identifying a patient, an agent can create a visit note with vitals such as blood pressure, then request the patient’s visit history. The README reports that the MCP server and its unit tests are working, with 20 of 20 tests passing.

Setup and configuration

The quickest installation path uses npm through npx:

Terminal
npx mcp-ratchet-clinical-charting

For source-based development, clone the repository, install dependencies, build the project, and use the development or test scripts. The project also provides commands for watch mode, coverage, and linting.

Claude Desktop can launch the server with an MCP configuration that uses npx and the package name. After adding the entry, restart Claude Desktop and confirm that the three tools appear. The documented configuration locations are under the Claude application support directory on macOS and the application-data directory on Windows.

Configuration includes RATCHET_MOCK_MODE, which can force mock mode, and LOG_LEVEL, which accepts debug, info, warn, or error. POINTCARE_API_URL specifies a PointCare API base URL, while POINTCARE_API_KEY supplies an API key or token. The README marks the PointCare settings as required for production use; mock mode activates when the API URL is not configured.

Tools and capabilities

  • Search patients by name, ID, or phone number.
  • Create visit notes containing vital measurements.
  • Retrieve a patient’s previous visits.
  • Test the workflow against five fictional patients in mock mode.
  • Run the server from npm or from the TypeScript source project.

Limitations and notes

The mcp-ratchet-clinical-charting MCP server currently operates in mock mode for development and testing. Its sample patients are fictional, notes are held in memory, and the repository states that production PointCare integration is pending API documentation and implementation. Do not treat the mock data store as a production clinical record system.

The README names Claude Desktop as ready for testing. It does not document client-specific setup for other MCP applications. The repository is licensed under MIT.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Ratchet Clinical Charting

mcp-ratchet-clinical-charting is an MCP server that connects Claude to clinical charting workflows and is designed for PointCare EMR integration. Its main tools are search_patient, create_visit_note, and get_patient_history. It currently uses fictional in-memory data by default, while production PointCare connectivity remains pending.

Install it with npx using `npx mcp-ratchet-clinical-charting`. You can also clone the repository, run `npm install`, build it, and start development mode with the provided npm scripts.

Yes, it is documented as ready for Claude Desktop testing. Add an MCP entry that runs `npx -y mcp-ratchet-clinical-charting`, restart Claude Desktop, and verify that the three charting tools are available.

Not currently. The server runs in mock mode by default, while PointCare production integration is pending API documentation and implementation. The documented PointCare URL and API key settings are intended for production mode.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Ratchet Clinical Charting AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-ratchet-clinical-charting?style=directory)](https://allmcps.com/mcp/mcp-ratchet-clinical-charting)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-ratchet-clinical-charting"><img src="https://allmcps.com/api/badge/mcp-ratchet-clinical-charting?style=directory" alt="MCP Ratchet Clinical Charting on AllMCPs" /></a>