zentao-rest-v1-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENTAO_URL | Yes | The URL of the ZenTao site, usually including the /zentao deployment path. | |
| ZENTAO_PASSWORD | Yes | Your ZenTao password. Only provided via environment variable, not written into source code or logs. | |
| ZENTAO_USERNAME | Yes | Your ZenTao account. | |
| ZENTAO_TIMEOUT_MS | No | Request timeout in milliseconds. Defaults to 30000. | 30000 |
| ZENTAO_SESSION_TTL_MS | No | Token local cache time in milliseconds. Defaults to 3000000. | 3000000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 52 tools
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.
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.
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.
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.