Mcp Ratchet Clinical Charting
Wire Claude Code or Cursor to document home-health or clinical visits into a PointCare-style EMR instead of retyping notes after each agent session.
Overview
Ratchet Clinical Charting is a Build-phase MCP server that documents patient visits into an EMR through Claude-compatible agent tools.
What is this MCP server?
- stdio npm package mcp-ratchet-clinical-charting v0.1.0 for Claude-driven visit documentation
- Optional POINTCARE_API_URL and secret POINTCARE_API_KEY for production EMR writes
- Runs in mock mode when EMR env vars are unset so you can prototype charting flows locally
- Targets patient visit documentation workflows rather than general coding assistance
- GitHub source at m2ai-mcp-servers/mcp-ratchet-clinical-charting
- Server schema version 0.1.0
- npm identifier mcp-ratchet-clinical-charting with stdio transport
- Two documented env vars: POINTCARE_API_URL (optional) and POINTCARE_API_KEY (secret, production)
What problem does it solve?
Builders experimenting with AI charting waste time copying agent drafts into the EMR by hand because agents lack a governed write path to clinical systems.
Who is it for?
Indie health-tech or clinical workflow builders prototyping Claude-driven visit notes with a real or mock PointCare EMR hook.
Skip if: General SaaS teams without EMR integration needs, or orgs that cannot accept agent-generated PHI without a full compliance program.
What do I get? / Deliverables
After registration, your agent can call MCP tools to structure and push visit documentation to PointCare-style APIs or mock endpoints while you iterate prompts.
- Agent-callable MCP tools for clinical visit documentation
- Mock EMR responses when API env vars are omitted
- Production writes to PointCare-style endpoints when credentials are set
Recommended MCP Servers
Journey fit
Canonical shelf is Build because you install and configure this MCP bridge while assembling agent tooling and external system hooks, not while operating a live clinic queue. Integrations fits EMR API credentials, stdio MCP wiring, and optional mock mode before production keys exist.
How it compares
EMR integration MCP bridge, not a standalone clinical scribe app or generic note-taking skill.
Common Questions / FAQ
Who is mcp-ratchet-clinical-charting for?
Developers and solo builders wiring Claude or similar agents to home-health or clinical EMR documentation APIs, especially PointCare-compatible stacks.
When should I use mcp-ratchet-clinical-charting?
Use it during Build when you need agent-accessible tools to draft and submit visit charts, starting in mock mode before production API keys.
How do I add mcp-ratchet-clinical-charting to my agent?
Install the npm stdio package, add it to your MCP client config, set POINTCARE_API_KEY (and optional POINTCARE_API_URL) for production, then restart the agent.