Skip to main content
Glama
cwj9195

zentao-rest-v1-mcp

by cwj9195
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to zentao-rest-v1-mcp

No user-submitted related servers found.

    Related Servers

    • @maxenlin/mcp-zentao-11-3

      CGBZNB
      A
      license
      D
      quality
      B
      maintenance
      Enables AI assistants to interact with Zentao 11.x legacy instances, managing tasks, bugs, stories, and test cases, and supports retrieving comments and operation history for tasks and bugs.
      50
      20 npm
      MIT

    • 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
      12
      -

    • 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
      16 npm
      15
      -
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    D1.5/5.0

    Scored across 52 tools

    Disambiguation3/5

    Most tools have fairly clear resource/action targets, but several overlap conceptually: multiple export tools, multiple get-task/get-bug variants, and generic helpers like initZentao/getConfig are easy to confuse. Without descriptions, an agent could struggle to choose between related tools like exportItems, exportModuleItemsAsMarkdown, and exportStoriesBySearch.

    Naming Consistency4/5

    The tools mostly follow a camelCase verb_noun pattern such as getTaskDetail, createTestCase, and resolveBug. Minor inconsistencies exist in singular/plural usage and entity-relationship naming, e.g. getStoryRelatedBugs vs getBugRelatedStory, but the overall convention is predictable and readable.

    Tool Count1/5

    With 52 tools, the surface is far too large for an MCP server, exceeding the 50+ threshold for an extreme mismatch. Many tools are auxiliary helpers, export variants, and analysis/generation utilities that inflate the set beyond a focused CRUD interface. This will overwhelm agents and make tool selection expensive and error-prone.

    Completeness3/5

    Task and bug lifecycles are reasonably covered with create, read, update, and state transitions, while test cases and stories have meaningful read/run/export support. However, there are notable gaps: no story update/create/delete, no test case update/delete, and no product detail or project management tools. The presence of many generate/analyze/format helpers does not fully compensate for missing core lifecycle operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources