Skip to main content
Glama
aipper

zentao-mcp-server

by aipper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to zentao-mcp-server

No user-submitted related servers found.

    Related Servers

    • mcp-zentao

      luffy-mcw
      A
      license
      D
      quality
      C
      maintenance
      An MCP server that enables reading and managing Zentao tasks, bugs, requirements, test cases, and test suites via the ZenTao 11.3 Legacy Session API. It integrates with MCP clients like Codex, Claude Desktop, and Cursor.
      48
      7 npm
      MIT

    • zentao-mcp

      askairo
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides an MCP server for ZenTao (禅道) project management. It enables read-only queries for projects, tasks, bugs, users, and stories, and supports write operations like task assignment, progression, and bug resolution when explicitly confirmed.
      21 npm
      MIT

    • 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

    A3.6/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct operation: listing projects, listing bugs, detail, resolve (single/batch), close, verify, comment, upload/download attachments, and token management. Even with overlapping operations like resolve vs batch resolve, the single vs batch scopes are clearly separated by descriptions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (e.g., list_my_projects, resolve_bug, upload_attachment). The naming is predictable and clear, with no mixed conventions.

    Tool Count5/5

    With 11 tools, the server is well-scoped for a bug tracking domain. Each tool serves a specific purpose without redundancy, covering core operations like listing, resolving, commenting, and file attachments.

    Completeness2/5

    The tool set is incomplete for a full bug lifecycle. Missing essential tools: create_bug, update_bug (general-purpose), delete_bug, and search bugs beyond 'my bugs'. The list_my_projects tool is noted as unreliable, and there is no tool to list all bugs or manage other entities like users or products.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources