Skip to main content
Glama
Sign In
zentao-mcp-server

zentao-mcp-server

by znmin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to zentao-mcp-server

No user-submitted related servers found.

    Related Servers

    • Zentao MCP Server

      Tytt
      A
      license
      Not graded
      quality
      D
      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.
      11 npm
      12
      MIT

    • @maxenlin/mcp-zentao-11-3

      CGBZNB
      A
      license
      D
      quality
      C
      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
      49 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
      26 npm
      16
      -

    • zentao-mcp

      wohaixiao-qds
      F
      license
      A
      quality
      D
      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.
      5
      -
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.2/5.0

    Scored across 14 tools

    Disambiguation2/5

    add_bug_comment and comment_bug are functionally near-identical (both add a plain comment without changing state), forcing the agent to guess; verify_bug also overlaps with close_bug since verify-pass closes the bug. get_bug_detail and get_bug_actions hit the same endpoint and require reading long descriptions to tell apart.

    Naming Consistency4/5

    Almost all tools follow verb_noun snake_case (get_bug_detail, resolve_bug, upload_attachment, batch_resolve_my_bugs). The lone deviation is comment_bug, which lacks a noun and breaks the pattern, contributing to its confusion with add_bug_comment.

    Tool Count4/5

    14 tools is a reasonable size for a bug-workflow server. However, a slot is wasted on a redundant comment tool, and the batch_resolve variant could arguably be a parameter rather than a separate tool.

    Completeness2/5

    The surface covers read, comment, resolve, verify, close and attachments, but there is no create_bug at all and no way to edit bug fields or reassign ownership, so an agent cannot originate or triage work. Scope is also limited to 'my' bugs/projects with no general search.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources