Ithura MCP vs MCP Taiga
A side-by-side look at the Ithura MCP and MCP Taiga MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
MCP TaigaProduct Management · Local subprocess (stdio)Taiga project management: issues, user stories, tasks, epics, sprints, comments, attachments and wiki via a compact set of tools.56GoodAuth: not declaredVerdict: choose Ithura MCP for product management work as a local process; choose MCP Taiga for product management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Ithura MCP when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ITHURA_API_KEY, ITHURA_WORKSPACE_SLUG, ITHURA_API_URL.
Choose MCP Taiga when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You want tools like
projects, work, sprints.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | MCP Taiga | |
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 36/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | ITHURA_API_KEYITHURA_WORKSPACE_SLUGITHURA_API_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 3 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 6 |
| Full listing | View Ithura MCP | View MCP Taiga |
Tools & capabilities
Ithura MCP tools
No tool names declared yet. Check the project README from the listing page.
MCP Taiga tools 6
projectsproject` accepts an ID or slugworktype`, `project`, `item`, `subject`, `itemssprintsproject`, `sprint`, `name`, `start`, `finishcommentstype`, `item`, `text`, `commentIdattachmentstype`, `item`, `attachmentId`, `filePath` or `fileContent`, `savePathwikiproject`, `page`, `content`, `watch
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.
Ithura MCP
{
"mcpServers": {
"mcp-102": {
"command": "npx",
"args": [
"-y",
"ithura-mcp"
],
"env": {
"ITHURA_API_KEY": "YOUR_ITHURA_API_KEY_HERE",
"ITHURA_WORKSPACE_SLUG": "YOUR_ITHURA_WORKSPACE_SLUG_HERE",
"ITHURA_API_URL": "YOUR_ITHURA_API_URL_HERE"
}
}
}
}
MCP Taiga
{
"mcpServers": {
"negoro26-mcp-taiga": {
"command": "npx",
"args": [
"-y",
"mcp-taiga"
]
}
}
}
Frequently asked questions
Ithura MCP is categorized under Product Management and uses a local stdio subprocess. MCP Taiga belongs to Product Management and uses a local stdio subprocess. Pick Ithura MCP for product management work and MCP Taiga for product management.
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.
Ithura MCP has no declared pricing — check the project's own site. MCP Taiga 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 mcp-102 and negoro26-mcp-taiga as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ithura MCP has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCP Taiga has 56/100 (Good) with 0 views, 0 installs and 3 GitHub stars.