Mirobody vs Protein Atlas

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

Mirobody 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 declaredProtein Atlas logoProtein AtlasBiology & Bioinformatics · Local subprocess (stdio)Human Protein Atlas (HPA) MCP — keyless.56GoodAuth: not declared

Verdict: choose Mirobody for biology & bioinformatics work as a local process; choose Protein Atlas 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?

Mirobody logoChoose Mirobody when

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

Protein Atlas logoChoose Protein Atlas when

  • You need dedicated capabilities in the Biology & Bioinformatics domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like search_genes, get_protein, top_tissues.
Explore Protein Atlas

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMirobody logoMirobodyProtein Atlas logoProtein Atlas
CategoryBiology & BioinformaticsBiology & Bioinformatics
Quality signal57/100 · Good56/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingBYOK (pay the provider)Not declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1,3870
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listed3

Tools & capabilities

Mirobody tools

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

Protein Atlas tools 3

  • search_genesSearch the Human Protein Atlas for human genes/proteins by gene symbol or keyword. Returns each gene with its Ensembl gene id (needed by get_protein and top_tissues), synonyms, and description. Keyless.
  • get_proteinGet a trimmed Human Protein Atlas profile for one protein by Ensembl gene id (e.g. "ENSG00000146648"): gene, description, protein class, biological process, molecular function, RNA tissue specificity/distribution, subcellular location, and disease involvement. Use search_genes to find the Ensembl id. Keyless.
  • top_tissuesList a protein's top-expressing human tissues by RNA expression (nTPM), highest first, for one Ensembl gene id. Use search_genes to find the Ensembl id. Keyless.

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.

Mirobody

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

Protein Atlas

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "protein-atlas": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-protein-atlas"
      ]
    }
  }
}

Frequently asked questions

Mirobody is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Protein Atlas belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Mirobody for biology & bioinformatics work and Protein Atlas 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.

Mirobody is bring-your-own-key: usage is billed by the API provider you supply a key for. Protein Atlas 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 mirobody and protein-atlas as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Mirobody has a quality signal of 57/100 (Good) with 1 views, 0 installs and 1,387 GitHub stars. Protein Atlas has 56/100 (Good) with 2 views, 0 installs and 0 GitHub stars.