Log inSubmit server

Medplum MCP vs Mirobody

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

Medplum MCP logoMedplum MCPBiology & BioinformaticsSecurely access and manage FHIR healthcare data stored in Medplum.41FairAuth: not declaredMirobody logoMirobodyBiology & Bioinformatics · Local subprocess (stdio)Turn scattered health data into answers you can trace. Self-hosted AI health data engine for lab reports, wearables and genetics, with a built-in MCP server. Run it with Docker and one LLM key, or keep every model local on llama.cpp.57GoodAuth: not declared

Verdict: choose Medplum MCP for biology & bioinformatics work; choose Mirobody 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?

Medplum MCP logoChoose Medplum MCP when

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

Mirobody logoChoose Mirobody when

  • You need dedicated capabilities in the Biology & Bioinformatics domain.
  • You prefer a local stdio subprocess transport.
Explore Mirobody

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMedplum MCP logoMedplum MCPMirobody logoMirobody
CategoryBiology & BioinformaticsBiology & Bioinformatics
Quality signal41/100 · Fair57/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredBYOK (pay the provider)
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2,7531,387
Directory activity 2 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView Medplum MCP View Mirobody

Tools & capabilities

Medplum MCP tools

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

Mirobody 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.

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.

Mirobody

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mirobody": {
      "command": "uvx",
      "args": [
        "--python",
        "3.12",
        "mirobody"
      ]
    }
  }
}

Frequently asked questions

Medplum MCP is categorized under Biology & Bioinformatics and uses an install path we have not confirmed yet. Mirobody belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Medplum MCP for biology & bioinformatics work and Mirobody 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. Mirobody is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 mirobody 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,753 GitHub stars. Mirobody has 57/100 (Good) with 1 views, 0 installs and 1,387 GitHub stars.

Popular comparisons with Medplum MCP

Popular comparisons with Mirobody