Skip to main content
Glama

Related Servers

Alternatives to ZenTao MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      D
      quality
      C
      maintenance
      Enables interaction with ZenTao open-source instances to query and manage tasks, bugs, stories, test cases, and test runs, using REST v1 with legacy fallback for incompatible routes.
      52
      15 npm
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      Enables interaction with ZenTao project management system through RESTful APIs. Supports listing products, managing bugs, viewing statistics, and filtering personal bug assignments through natural language.
      4
      36 npm
      15
      -
    • F
      license
      Not graded
      quality
      F
      maintenance
      Enables AI assistants to manage Zentao bugs, requirements, and test cases through natural language interactions. It supports querying, creating, and updating various Zentao data entities including products, projects, and executions.
      10 npm
      11
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Exposes Zentao REST API as MCP tools for listing/searching bugs, reading details with screenshots, and resolving bugs after explicit confirmation. Includes a setup wizard to configure Codex, Claude, Cursor and other clients.
      -
    • A
      license
      A
      quality
      Not graded
      maintenance
      Enables direct integration with Zentao bug tracking systems through Cursor. Supports authentication, bug retrieval, searching, and listing operations for comprehensive bug management through natural language.
      5
      7 npm
      -

    TDQS

    B3.2/5.0

    Scored across 10 tools

    Disambiguation3/5

    The tools have clear distinctions in most cases, but there is some overlap between getMyBug, getMyBugs, and getNextBug, which all retrieve bugs assigned to the user with slight variations in scope (single vs. list vs. next). Additionally, call is a generic tool that could potentially duplicate functionality of specific tools like getBugDetail or markBugResolved, creating ambiguity in tool selection for agents.

    Naming Consistency2/5

    Naming conventions are inconsistent: tools use a mix of camelCase (getBugDetail, getMyBug) and snake_case (get_token, markBugResolved), with no clear pattern. Verb usage varies, such as 'get' for retrieval and 'mark' for updates, but the inconsistency in casing and structure reduces predictability and readability.

    Tool Count5/5

    With 10 tools, the count is well-scoped for a ZenTao bug tracking and project management server. It covers core operations like bug retrieval, resolution, project listing, and token management, providing a balanced set without being overwhelming or too sparse for the domain.

    Completeness4/5

    The tool set covers essential workflows for bug management (e.g., get, list, resolve) and project/product access, with minor gaps such as missing tools for creating bugs or updating bug details beyond resolution. However, the generic call tool can potentially fill these gaps, making the surface reasonably complete for typical agent tasks.