Skip to main content
Glama
juanleon8581

taiga-mcp

by juanleon8581
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to taiga-mcp

No user-submitted related servers found.

    Related Servers

    • @illodev/taiga-mcp

      illodev
      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
      26 npm
      2
      MIT

    • Taiga MCP Server

      negoro26
      A
      license
      A
      quality
      A
      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
      10 npm
      MIT

    • zube-mcp

      reenrik
      F
      license
      C
      quality
      D
      maintenance
      MCP server for the Zube.io project management API, exposing boards, cards, epics, tickets, sprints, and workspaces as tools for AI assistants.
      42
      -

    • planning-task-mcp

      sergioramosv
      A
      license
      Not graded
      quality
      F
      maintenance
      Full autonomous project management MCP server enabling AI assistants to manage projects, sprints, tasks, bugs, proposals, and team collaboration via natural language.
      5 npm
      MIT

    • Taiga MCP Server

      greddy7574
      A
      license
      D
      quality
      D
      maintenance
      Enables natural language interaction with Taiga project management systems, allowing management of projects, sprints, user stories, tasks, and issues through conversational AI.
      46
      18 npm
      7
      ISC
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 55 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources