ZenTao MCP Server
Related Servers
Alternatives to ZenTao MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables interaction with ZenTao project management software through its REST API. Supports bug tracking, product management, and issue resolution with secure authentication for streamlined development workflows.726 npm1ISC
- AlicenseDqualityCmaintenanceEnables 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.5213 npmMIT
- AlicenseBqualityBmaintenanceEnables AI clients to work with ZenTao via its REST API, automatically exchanging account credentials for a Token and supporting project listing, bug querying and history, resolving/closing/verifying bugs, structured comments, and attachment upload/download with verification. Read-only mode and configurable endpoints, upload size, and timeouts let it fit self-hosted deployments.14446 npmMIT
- FlicenseAqualityBmaintenanceEnables interaction with ZenTao project management system through RESTful APIs. Supports listing products, managing bugs, viewing statistics, and filtering personal bug assignments through natural language.430 npm16-
- AlicenseNot gradedqualityDmaintenanceEnables 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.12MIT
- FlicenseAqualityDmaintenanceExposes 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-
TDQS
Scored across 10 tools
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 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.
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.
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.