Mirobody vs Ucsc Genome
A side-by-side look at the Mirobody and Ucsc Genome 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 as a local process; choose Ucsc Genome 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.
- You prefer a local stdio subprocess transport.
Choose Ucsc Genome when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
hg38, mm39, danRer11.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 57/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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,387 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Mirobody | View Ucsc Genome |
Tools & capabilities
Mirobody tools
No tool names declared yet. Check the project README from the listing page.
Ucsc Genome tools 3
hg38mm39danRer11
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": {
"mirobody": {
"command": "uvx",
"args": [
"--python",
"3.12",
"mirobody"
]
}
}
}
Ucsc Genome
{
"mcpServers": {
"ucsc-genome": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-ucsc-genome"
]
}
}
}
Frequently asked questions
Mirobody is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Ucsc Genome belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Mirobody for biology & bioinformatics work and Ucsc Genome 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. Ucsc Genome 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 ucsc-genome 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. Ucsc Genome has 53/100 (Good) with 1 views, 0 installs and 0 GitHub stars.