Skip to main content
Glama
jafamo

Taiga MCP Server

by jafamo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Taiga MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      20 npm
      7
      ISC

    • Taiga MCP Server

      ssaurabh9
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables seamless integration between Large Language Models and Taiga project management platform, allowing users to manage projects, user stories, tasks, and team collaboration through natural language commands.
      4
      GPL 3.0

    • taiga-mcp

      juanleon8581
      A
      license
      A
      quality
      B
      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
      7 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
      43 npm
      3
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.3/5.0

    Scored across 31 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair (e.g., list_issues vs. get_issue vs. create_issue), and resource types are clearly separated. The only cross-resource tool is taiga_search, which is explicitly described as full-text search, so no ambiguity exists.

    Naming Consistency5/5

    All tools follow a consistent 'taiga_<verb>_<resource>' pattern with standard verbs (list, get, create, edit, delete). Plural nouns are used for list operations and singular for others, making the naming scheme highly predictable.

    Tool Count2/5

    With 31 tools, the server far exceeds the typical well-scoped range (3-15) and even the 'heavy' range (16-25). While each tool has a clear purpose, the large number feels excessive for a single server, especially given incomplete CRUD coverage across resource types.

    Completeness3/5

    User stories, tasks, and issues have full CRUD operations, but projects, milestones, epics, and wiki pages lack delete operations, and projects and milestones also lack edit operations. These are notable gaps in lifecycle coverage that agents cannot fully work around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources