Mirobody vs Sourcebook
A side-by-side look at the Mirobody and Sourcebook MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mirobody for biology & bioinformatics work; choose Sourcebook 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 Mirobody when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
Choose Sourcebook 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 | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 51/100 · Good | 39/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,389 | 3 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Mirobody | View Sourcebook |
Tools & capabilities
Mirobody tools
No tool names declared yet. Check the project README from the listing page.
Sourcebook 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.
Mirobody
No confirmed install command for Mirobody yet — follow the setup steps linked from its listing page rather than a guessed package name.
Sourcebook
{
"mcpServers": {
"sourcebook": {
"command": "npx",
"args": [
"-y",
"sourcebook"
]
}
}
}