Medplum MCP vs MCP Ratchet Clinical Charting
A side-by-side look at the Medplum MCP and MCP Ratchet Clinical Charting MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Medplum MCP for biology & bioinformatics work; choose MCP Ratchet Clinical Charting for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Medplum MCP when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
Choose MCP Ratchet Clinical Charting when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
POINTCARE_API_URL, POINTCARE_API_KEY, RATCHET_MOCK_MODE, LOG_LEVEL. - You want tools like
search_patient, create_visit_note, get_patient_history.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 41/100 · Fair | 51/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | POINTCARE_API_URLPOINTCARE_API_KEYRATCHET_MOCK_MODELOG_LEVEL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,760 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Medplum MCP | View MCP Ratchet Clinical Charting |
Tools & capabilities
Medplum MCP tools
No tool names declared yet. Check the project README from the listing page.
MCP Ratchet Clinical Charting tools 3
search_patientFind patient by name, ID, or phonecreate_visit_noteDocument a patient visit with vitalsget_patient_historyRetrieve patient visit history
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Medplum MCP
No confirmed install command for Medplum MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
MCP Ratchet Clinical Charting
{
"mcpServers": {
"mcp-ratchet-clinical-charting": {
"command": "npx",
"args": [
"-y",
"mcp-ratchet-clinical-charting"
],
"env": {
"POINTCARE_API_URL": "YOUR_POINTCARE_API_URL_HERE",
"POINTCARE_API_KEY": "YOUR_POINTCARE_API_KEY_HERE",
"RATCHET_MOCK_MODE": "YOUR_RATCHET_MOCK_MODE_HERE",
"LOG_LEVEL": "YOUR_LOG_LEVEL_HERE"
}
}
}
}
Frequently asked questions
Medplum MCP is categorized under Biology & Bioinformatics and uses an install path we have not confirmed yet. MCP Ratchet Clinical Charting belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Medplum MCP for biology & bioinformatics work and MCP Ratchet Clinical Charting for biology & bioinformatics.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Medplum MCP has no confirmed install command yet — follow its own setup instructions.
Medplum MCP has no declared pricing — check the project's own site. MCP Ratchet Clinical Charting has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-112 and mcp-ratchet-clinical-charting as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Medplum MCP has a quality signal of 41/100 (Fair) with 2 views, 0 installs and 2,760 GitHub stars. MCP Ratchet Clinical Charting has 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars.