Skip to main content
Glama
taiga-delegate

taiga-delegate

Related Servers

Alternatives to taiga-delegate

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Full-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.
      100
      6
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for the Taiga project management API. Enables AI assistants to manage projects, issues, user stories, tasks, epics, sprints, and wiki pages via natural language commands.
      55
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP 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.
      6
      15 npm
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A 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.
      17
      975 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that lets AI agents connect to LTD project workspaces to inspect project health, search and manage tasks, assign owners, and add comments, with scoped tokens and preview-confirm safety for writes.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local, stdio-based MCP server that lets multiple coding agents share one project database for tasks, verification evidence, signals, knowledge, and conversation indexes. It enforces workflows with allowlisted verification runners and gate checks on acceptance criteria, evidence, dependencies, and high-risk approval before work can be closed.
      59 npm
      MIT

    TDQS

    B3/5.0

    Scored across 35 tools

    Disambiguation4/5

    Most tools are cleanly separated by resource and CRUD verb. Minor overlap exists between taiga_create_user_story and taiga_bulk_create_stories, and between taiga_add_comment and update tools that accept inline comments, but boundaries remain understandable. mcp_usage_stats is unrelated to the Taiga domain and slightly muddies the set.

    Naming Consistency4/5

    Nearly all tools follow a predictable taiga_verb_noun convention with snake_case. The lone mcp_usage_stats tool breaks both the prefix and domain pattern. Aside from that outlier, naming is highly consistent.

    Tool Count2/5

    At 35 tools, the surface is heavy for a project-management server and exceeds the rubric's 25+ threshold. While Taiga has many resources, the count feels inflated by partial CRUD sets and utility tools rather than a tightly scoped surface.

    Completeness2/5

    Coverage is strong for stories, issues, epics, and wiki pages, including delete operations. However, tasks only support create with no list/get/update/delete, sprints lack update/delete, projects lack update/delete, and membership/comments only support add. These gaps will block common agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues