Model Context Protocol server for Taiga project management API integration, providing tools for managing epics, user stories, tasks, and issues.
The Taiga MCP server has only 2 tools visible in source code, both with serious deficiencies. taiga_capabilities has an empty input schema ({}) and a generic 40-char description; echo has a single string parameter with minimal context. Neither tool has documented output schemas. The codebase shows significant infrastructure (FastMCP, environment config, transport security) but the actual tool definitions are skeletal. No error handling guidance, no parameter validation messaging, no composition or chaining support evident. The server exposes only read-only utility functions and lacks the domain tools (create_task, update_project, search_issues, etc.) expected of a project management MCP server.
Echo a message back to the caller.
Return server capabilities and policy configuration (non-sensitive). Intended for ChatGPT / IDE agents / Builder Agent to adapt behavior.
taiga_capabilities has NO documented input schema (empty {} object).
taiga_capabilities description is only 40 chars and does not explain WHY an agent should call it, WHEN to use it, or WHAT the response structure is. Under 50-char descriptions cannot guide LLM selection.
echo tool name does not follow verb_noun pattern and is ambiguous. 'Echo' suggests logging/debugging, not a meaningful project management action. Name should reflect actual use case (e.g., 'test_connection' if for server health checks).
No output schemas documented for either tool. LLMs cannot plan downstream calls or extract expected fields. Response structures are invisible.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 36 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 46 | - | v1 |
No error handling guidance anywhere. If a tool fails, the LLM receives no instruction on whether to retry, ask the user, or abandon the goal.
Server advertises 'Taiga MCP' but exposes zero domain tools (no create_task, list_projects, search_issues, update_story, etc.). The two visible tools are server metadata and echo. This is not a functional project management assistant.