Claude Task Master vs Icf MCP
A side-by-side look at the Claude Task Master and Icf MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Claude Task Master for developer tools work as a local process; choose Icf MCP for biology & bioinformatics over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Claude Task Master when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ANTHROPIC_API_KEY, OPENAI_API_KEY, GOOGLE_API_KEY, PERPLEXITY_API_KEY, XAI_API_KEY, OPENROUTER_API_KEY, MISTRAL_API_KEY, TASK_MASTER_TOOLS.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Biology & Bioinformatics |
| Quality signal | 61/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | ANTHROPIC_API_KEYOPENAI_API_KEYGOOGLE_API_KEYPERPLEXITY_API_KEYXAI_API_KEYOPENROUTER_API_KEYMISTRAL_API_KEYTASK_MASTER_TOOLS | WHO_CLIENT_IDWHO_CLIENT_SECRET |
| Verified owner | Community listing | Community listing |
| GitHub stars | 28,270 | 1 |
| Directory activity | 10 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Claude Task Master | View Icf MCP |
Tools & capabilities
Claude Task Master tools
No tool names declared yet. Check the project README from the listing page.
Icf MCP tools 1
icf
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.
Claude Task Master
{
"mcpServers": {
"eyaltoledano-claude-task-master": {
"command": "npx",
"args": [
"-y",
"task-master-ai"
],
"env": {
"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"GOOGLE_API_KEY": "YOUR_GOOGLE_API_KEY_HERE",
"PERPLEXITY_API_KEY": "YOUR_PERPLEXITY_API_KEY_HERE",
"XAI_API_KEY": "YOUR_XAI_API_KEY_HERE",
"OPENROUTER_API_KEY": "YOUR_OPENROUTER_API_KEY_HERE",
"MISTRAL_API_KEY": "YOUR_MISTRAL_API_KEY_HERE",
"TASK_MASTER_TOOLS": "YOUR_TASK_MASTER_TOOLS_HERE"
}
}
}
}
Icf MCP
{
"mcpServers": {
"icf-mcp": {
"url": "https://mcp-icf.medseal.app/mcp"
}
}
}
Frequently asked questions
Claude Task Master is categorized under Developer Tools and uses a local stdio subprocess. Icf MCP belongs to Biology & Bioinformatics and uses a remote HTTP/SSE transport. Pick Claude Task Master for developer tools work and Icf MCP 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.
Claude Task Master is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Icf MCP 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 eyaltoledano-claude-task-master and icf-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Claude Task Master has a quality signal of 61/100 (Good) with 10 views, 0 installs and 28,270 GitHub stars. Icf MCP has 51/100 (Good) with 2 views, 0 installs and 1 GitHub stars.