Marrow vs Mirobody
A side-by-side look at the Marrow and Mirobody MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MirobodyBiology & 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 declaredVerdict: choose Marrow for biology & bioinformatics work over a hosted endpoint; 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?
Choose Marrow when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
health_summary, list_metrics, metric_daily.
MChoose Mirobody when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M Mirobody | |
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 53/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 1,381 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 9 | Not listed |
| Full listing | View Marrow | View Mirobody |
Tools & capabilities
Marrow tools 9
health_summaryRecent days across activity, heart, sleep and nutritionlist_metricsEvery metric in the mirror, with units and coveragemetric_dailyDaily values for any metric, up to 400 daysmetric_samplesRaw records with timestamps and source devicesworkoutsWorkouts from every source: activity, start, end, duration and sourcenutrition_logThe meal diary: every logged food with full nutrient detail, by daystrength_logEvery lifting set with its set type and estimated 1RM, per-exercise progression, and volume per muscle group (warm-ups left out)sleep_logOne night per wake day: bedtime, wake time, hours asleep, minutes per stagesymptoms_and_moodSymptoms with their severity, and State of Mind entries with valence, feelings and what they were about
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.
Marrow
{
"mcpServers": {
"marrow-4": {
"url": "https://skeletonarmy.tech/mcp"
}
}
}
Mirobody
{
"mcpServers": {
"mirobody": {
"command": "uvx",
"args": [
"--python",
"3.12",
"mirobody"
]
}
}
}
Frequently asked questions
Marrow is categorized under Biology & Bioinformatics and uses a remote HTTP/SSE transport. Mirobody belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Marrow 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.
Marrow 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 marrow-4 and mirobody as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Marrow has a quality signal of 53/100 (Good) with 1 views, 0 installs and 3 GitHub stars. Mirobody has 57/100 (Good) with 0 views, 0 installs and 1,381 GitHub stars.