taiga-mcp
Related Servers
Alternatives to taiga-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceFull-featured MCP server for Taiga project management, enabling AI agents to manage projects, epics, user stories, tasks, issues, sprints, wiki pages, memberships, and roles via Taiga API v1.10033 npm4MIT
- AlicenseAqualityAmaintenanceMCP server for Taiga project management, enabling LLM clients to inspect and manage projects, work items, sprints, comments, attachments, and wiki pages via 6 op-dispatching tools.627 npm3MIT
- AlicenseBqualityCmaintenanceAn MCP server that gives AI agents full Taiga project-management tools — epics, stories, tasks, issues, sprints, wiki, comments, and search — while confining each agent or outside collaborator to only the epics it was granted, signing their comments and tagging their created items for attribution, and logging every tool call for per-token usage metering. It enables safe, least-privilege delegation of a board over stdio or HTTP without sharing full account access.35MIT
- FlicenseCqualityDmaintenanceMCP server for the Zube.io project management API, exposing boards, cards, epics, tickets, sprints, and workspaces as tools for AI assistants.42-
- AlicenseNot gradedqualityDmaintenanceFull autonomous project management MCP server enabling AI assistants to manage projects, sprints, tasks, bugs, proposals, and team collaboration via natural language.16 npmMIT
- AlicenseDqualityDmaintenanceEnables natural language interaction with Taiga project management systems, allowing management of projects, sprints, user stories, tasks, and issues through conversational AI.4617 npm7ISC
TDQS
Scored across 55 tools
Each tool targets a distinct resource and action. There is no overlap; for example, create_epic, create_issue, create_userstory are clearly separate. Even similar tools like list_issue_statuses vs list_issue_types serve different purposes.
All tool names follow a consistent verb_noun pattern using snake_case. Verbs like create, delete, get, list, update, add, bulk_create, link, unlink, search are used uniformly. No mixing of conventions.
With 55 tools, the server is comprehensive but on the high side. The count is justified by covering many entities (epics, issues, tasks, user stories, milestones, wiki pages, roles, projects) and supplementary operations (list statuses, types, priorities, etc.), but could be slightly trimmed.
The tool set provides full CRUD for most entities and includes extras like linking, bulk creation, search, and activity history. Notable gaps: no get_task tool (though create, update, delete, list exist) and no comment CRUD beyond add_comment.