Medplum MCP Server

Connect Medplum to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Medplum is a healthcare platform that helps you quickly develop high-quality compliant applications. The medplum mcp server is what makes that connection.

What the server does

Medplum is a developer platform that enables flexible and rapid development of healthcare apps.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Full — stack TypeScript**: We use Node.js to power our servers, and React to power our frontend apps. Almost all of the code you'll touch in this codebase
• PostgreSQL — Data storage
• Redis — Background jobs and caching
• Express — API server
• TypeScript — Type-safe JavaScript
• React — Frontend React app
• Codebase — The Codebase tool exposed by this server
• Technologies — With the ground rules out of the way, let's talk about the coarse architecture of this mono repo:

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Medplum's toolset — Full, PostgreSQL, Redis and 5 more — is a fair guide to whether it matches your workflow. It is maintained by medplum; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.