Last EHR — Medplum vs Openfda

In-depth architectural comparison of the Last EHR — Medplum and Openfda MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Last EHR — Medplum when:

• You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Last EHR — Medplum Details

Choose Openfda when:

• You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Openfda Details

Feature & Specification Comparison

Specification	Last EHR — Medplum Biology, Medicine and Bioinformatics	Openfda Biology, Medicine and Bioinformatics
Summary	Read-only Medplum chart search and patient context for MCP clients.	OpenFDA MCP — wraps the openFDA API (free, no auth required)
Category & Scope	Biology, Medicine and Bioinformatics	Biology, Medicine and Bioinformatics

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "last-ehr-medplum": {
      "command": "npx",
      "args": [
        "-y",
        "@lastehr/agent-write-conformance"
      ]
    }
  }
}

{
  "mcpServers": {
    "openfda": {
      "url": "https://gateway.pipeworx.io/openfda/mcp"
    }
  }
}

Related MCP Server Comparisons