MCP Pharma vs Mirobody
A side-by-side look at the MCP Pharma 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 MCP Pharma for biology & bioinformatics work as a local process; choose Mirobody for biology & bioinformatics. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Pharma when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MCP_PHARMA_API_KEY, MCP_PHARMA_API_BASE, MCP_PHARMA_TIMEOUT, MCP_PHARMA_LOG_LEVEL.
Choose Mirobody when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 37/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | MCP_PHARMA_API_KEYMCP_PHARMA_API_BASEMCP_PHARMA_TIMEOUTMCP_PHARMA_LOG_LEVEL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1,389 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP Pharma | View Mirobody |
Tools & capabilities
MCP Pharma 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.
MCP Pharma
{
"mcpServers": {
"mcp-pharma": {
"command": "uvx",
"args": [
"atomno-mcp-pharma"
],
"env": {
"MCP_PHARMA_API_KEY": "YOUR_MCP_PHARMA_API_KEY_HERE",
"MCP_PHARMA_API_BASE": "YOUR_MCP_PHARMA_API_BASE_HERE",
"MCP_PHARMA_TIMEOUT": "YOUR_MCP_PHARMA_TIMEOUT_HERE",
"MCP_PHARMA_LOG_LEVEL": "YOUR_MCP_PHARMA_LOG_LEVEL_HERE"
}
}
}
}
Mirobody
No confirmed install command for Mirobody yet — follow the setup steps linked from its listing page rather than a guessed package name.