Skip to main content
Glama
reenrik

zube-mcp

by reenrik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to zube-mcp

No user-submitted related servers found.

    Related Servers

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

    • Fizzy Do MCP

      ryanyogan
      A
      license
      Not graded
      quality
      C
      maintenance
      Open-source MCP server that connects AI assistants to Fizzy (Basecamp's task management) with 70+ tools for boards, cards, workflows, and AI-powered project management.
      10 npm
      3
      MIT

    • @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
      24 npm
      4
      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

    C2.9/5.0

    Scored across 42 tools

    Disambiguation2/5

    The set includes multiple card-listing tools with overlapping scopes: list_cards, list_project_cards, list_triage_cards, and list_epic_cards. While filters could consolidate these, the redundancy creates ambiguity about which tool to select. Most other tools are clearly distinct.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (list_, get_, create_, update_, move_, archive_, delete_). No style mixing or vague verbs; one can predict tool names from the resource.

    Tool Count2/5

    With 42 tools, the surface is heavy for a project management server. Several tools overlap (card listers) and some entities have many CRUD variants, inflating the count beyond what is necessary.

    Completeness3/5

    Core card lifecycle is well covered (create, read, update, move, archive, comment), but notable gaps include no update/delete for workspaces, no label update/delete, and no relation listing/deletion. These are workable but not full CRUD.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources