Skip to main content
Glama
dannyvan

@dannyvan/zentao-mcp

by dannyvan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @dannyvan/zentao-mcp

No user-submitted related servers found.

    Related Servers

    • zentao-rest-v1-mcp

      cwj9195
      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

    • ZenTao MCP Server

      leeguooooo
      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
      -

    • Zentao MCP Server

      Tytt
      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
      -

    • zentao-mcp

      wohaixiao-qds
      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.
      -
    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/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct action on the Bug resource: read, search, lifecycle transitions, confirmation, and assignment. The lifecycle verbs (resolve, close, activate, confirm, assign) are clearly separate state changes, and the descriptions clarify any subtle overlap.

    Naming Consistency5/5

    All tools follow a consistent zentao_<verb>_bug pattern, with plural bug only where list/search return collections. The naming is predictable and makes the action for each tool immediately obvious.

    Tool Count5/5

    Nine tools is a well-scoped size for a bug-management server. Each tool covers a meaningful operation, and the count is neither bloated nor too thin.

    Completeness2/5

    The toolset covers querying and state transitions well, but there is no create_bug tool and no generic update tool for fields like title, severity, or priority. The comment_bug tool is also explicitly non-functional, so agents cannot fully manage bugs through this server alone.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources