Icf MCP vs Mirobody
A side-by-side look at the Icf MCP 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 Icf MCP for biology & bioinformatics work over a hosted endpoint; choose Mirobody for biology & bioinformatics. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Icf MCP when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
WHO_CLIENT_ID, WHO_CLIENT_SECRET. - You want tools like
icf.
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 | 51/100 · Good | 51/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | WHO_CLIENT_IDWHO_CLIENT_SECRET | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 1,388 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Icf MCP | View Mirobody |
Tools & capabilities
Icf MCP tools 1
icf
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.
Icf MCP
{
"mcpServers": {
"icf-mcp": {
"url": "https://mcp-icf.medseal.app/mcp"
}
}
}
Mirobody
No confirmed install command for Mirobody yet — follow the setup steps linked from its listing page rather than a guessed package name.