Fhirhydrant vs Medplum MCP

A side-by-side look at the Fhirhydrant and Medplum MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Fhirhydrant logoFhirhydrantBiology & Bioinformatics · Local subprocess (stdio)FHIR MCP server with SMART Backend Services, response compaction, FHIRPath, and guarded writes.55GoodAuth: not declaredMedplum MCP logoMedplum MCPBiology & BioinformaticsSecurely access and manage FHIR healthcare data stored in Medplum.41FairAuth: not declared

Verdict: choose Fhirhydrant for biology & bioinformatics work as a local process; choose Medplum MCP for biology & bioinformatics. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Fhirhydrant logoChoose Fhirhydrant when

  • You need dedicated capabilities in the Biology & Bioinformatics domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like terminology_lookup, code_search.
Explore Fhirhydrant

Medplum MCP logoChoose Medplum MCP when

  • You need dedicated capabilities in the Biology & Bioinformatics domain.
Explore Medplum MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFhirhydrant logoFhirhydrantMedplum MCP logoMedplum MCP
CategoryBiology & BioinformaticsBiology & Bioinformatics
Quality signal55/100 · Good41/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars182,760
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools2Not listed

Tools & capabilities

Fhirhydrant tools 2

  • terminology_lookupLooks up one LOINC or SNOMED CT code
  • code_searchSearches codes by text filter with paging support

Medplum MCP tools

No tool names declared yet. Check the project README from the listing page.

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.

Fhirhydrant

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "fhirhydrant": {
      "command": "npx",
      "args": [
        "-y",
        "fhirhydrant"
      ]
    }
  }
}

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.

Frequently asked questions

Fhirhydrant is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Medplum MCP belongs to Biology & Bioinformatics and uses an install path we have not confirmed yet. Pick Fhirhydrant for biology & bioinformatics work and Medplum MCP 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.

Fhirhydrant has no declared pricing — check the project's own site. Medplum MCP 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 fhirhydrant and mcp-112 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Fhirhydrant has a quality signal of 55/100 (Good) with 1 views, 0 installs and 18 GitHub stars. Medplum MCP has 41/100 (Fair) with 2 views, 0 installs and 2,760 GitHub stars.