Skip to main content
Glama

Related Servers

Alternatives to taiga-mcp

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
      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
      B
      quality
      C
      maintenance
      An 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.
      35
      MIT
    • 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
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects 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

    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

    ActivitySlowing
    ResponsivenessOutdated data