F
licenseB
qualityC
maintenanceEnables interaction with ZenTao project management system through RESTful API v1. Supports bug tracking, project/product management, and automated token authentication for seamless integration.
10
20
1
-
zentao-rest-v1-mcp
by cwj9195
Related Servers
Alternatives to zentao-rest-v1-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables 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.7221ISC
- FlicenseNot gradedqualityFmaintenanceEnables 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.611-
- FlicenseAqualityAmaintenanceEnables interaction with ZenTao project management system through RESTful APIs. Supports listing products, managing bugs, viewing statistics, and filtering personal bug assignments through natural language.42115-
- FlicenseNot gradedqualityFmaintenanceEnables LLMs to interact with ZenTao project management system, supporting project and task management operations including creating, querying, and updating projects and tasks through natural language.4-
- AlicenseCqualityBmaintenanceEnables full CRUD operations on Zentao entities like requirements, bugs, tasks, test cases, projects, and products through natural language.176161MIT
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