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.1006MIT
- AlicenseAqualityBmaintenanceMCP 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.615 npm3MIT
- AlicenseAqualityBmaintenanceA read-only MCP server that lets AI assistants answer questions about Taiga projects — sprints, user stories, tasks, issues, epics, wiki pages, activity and attached files — without opening Taiga. It runs locally with credentials in a .env file or hosted over HTTP with a sign-in per person.17975 npm1MIT
- 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 gradedqualityCmaintenanceConnects Claude and other MCP clients to self-hosted or cloud Taiga instances, letting users browse projects and sprints and read, search, create, update, comment on, and delete user stories, tasks, issues, and epics. Each person signs in with their own instance URL and account, with per-user permissions enforced.MIT
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.