Gtex vs Mirobody
A side-by-side look at the Gtex and Mirobody MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gtex 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?
Choose Gtex when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
Choose 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 | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 41/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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 | 0 | 1,387 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Gtex | View Mirobody |
Tools & capabilities
Gtex 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.
Gtex
{
"mcpServers": {
"gtex": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-gtex"
]
}
}
}
Mirobody
{
"mcpServers": {
"mirobody": {
"command": "uvx",
"args": [
"--python",
"3.12",
"mirobody"
]
}
}
}
Frequently asked questions
Gtex is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Mirobody belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Gtex 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.
Gtex 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 gtex and mirobody as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gtex has a quality signal of 41/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Mirobody has 57/100 (Good) with 1 views, 0 installs and 1,387 GitHub stars.