Skip to main content
Glama
Sign In
taiga-mcp

taiga-mcp

by kiet0807
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to taiga-mcp

No user-submitted related servers found.

    Related Servers

    • taiga-mcp

      juanleon8581
      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
      8 npm
      ISC

    • @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
      39 npm
      6
      MIT

    • taiga-delegate

      hemanthkandru
      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

    • Taiga MCP Server

      negoro26
      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
      20 npm
      3
      MIT

    • Taiga MCP

      rafleze
      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.
      8 npm
      MIT

    • jira-mcp-server

      chrisurf
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that provides AI agents structured access to Jira Cloud, enabling project listing, sprint overview, issue retrieval, and JQL search.
      1,575 npm
      MIT
    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

    A4.3/5.0

    Scored across 17 tools

    Disambiguation4/5

    The list tools are split cleanly by item type (stories, tasks, issues, epics, sprints, wiki pages), and descriptions explicitly cross-reference each other, e.g. 'Bugs and requests are issues: use list_issues'. The only real overlaps are `search` versus the per-type list tools that also accept a `search` filter, and get_sprint versus list_sprints; both are explained but still require a judgment call.

    Naming Consistency4/5

    Consistent snake_case with a dominant verb_noun pattern (list_projects, get_item, get_attachment, list_wiki_pages, create_item, update_item). Minor deviations: bare `search` with no object, `add_comment` instead of a create_* form, and the generic create_item/update_item names sit oddly next to the type-granular list_* family.

    Tool Count4/5

    17 tools is at the upper edge but each maps to a distinct resource or operation in Taiga's model (projects, sprints, stories, tasks, issues, epics, wiki, activity, attachments, writes). Nothing looks like filler, though a few tools (get_attachment, list_activity) are niche enough that the set could have been trimmed slightly.

    Completeness4/5

    Read coverage is excellent across the whole domain, and write coverage handles the core story/task/issue lifecycle plus comments. Gaps: no wiki page authoring, no epic creation (create_item covers only story/task/issue), and no sprint management; deletion is deliberately absent, which agents can work around by closing items.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources