@dannyvan/zentao-mcp
Related Servers
Alternatives to @dannyvan/zentao-mcp
No user-submitted related servers found.
Related Servers
- 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
- FlicenseBqualityNot gradedmaintenanceEnables interaction with ZenTao project management system through RESTful API v1. Supports bug tracking, project/product management, and automated token authentication for seamless integration.102-
- 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.14494 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-
- 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
- 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
TDQS
Scored across 9 tools
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.
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.
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.
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.