Maccabi Health vs Mirobody

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

Maccabi Health logoMaccabi HealthBiology & Bioinformatics · Local subprocess (stdio)Read your own Maccabi Healthcare records: labs, prescriptions, visits, referrals, PDFs.47FairAuth: 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 Maccabi Health for biology & bioinformatics work as a local process; 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?

Maccabi Health logoChoose Maccabi Health when

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

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.

SpecMaccabi Health logoMaccabi HealthMirobody logoMirobody
CategoryBiology & BioinformaticsBiology & Bioinformatics
Quality signal47/100 · Fair57/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredBYOK (pay the provider)
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars131,387
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Maccabi Health 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.

Maccabi Health

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

Mirobody

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

Frequently asked questions

Maccabi Health is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Mirobody belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Maccabi Health 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.

Maccabi Health 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 maccabi-health and mirobody as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Maccabi Health has a quality signal of 47/100 (Fair) with 1 views, 0 installs and 13 GitHub stars. Mirobody has 57/100 (Good) with 2 views, 0 installs and 1,387 GitHub stars.