@maxenlin/mcp-zentao-11-3
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENTAO_URL | Yes | 禅道服务器地址，必须包含 /zentao 路径 | |
| ZENTAO_PASSWORD | Yes | 禅道密码 | |
| ZENTAO_USERNAME | Yes | 禅道用户名 |
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 50 tools
While most tools follow a get/update/export/analyze pattern, there are many overlapping variants (e.g., exportItems, exportStory, exportBug, exportStoriesBySearch; getProductBugs, getMyBugs, getStoryRelatedBugs, getBugRelatedBug) and most tools have no descriptions, making it hard to know which one to use.
Tool names consistently use camelCase verb+noun construction (get*, create*, update*, export*, analyze*), with only a few outliers like initZentao, getConfig, and exportItems. The naming scheme is recognizable and predictable.
50 tools is excessive for a Zentao integration, with many single-purpose export and summary helpers that could be consolidated or omitted. The count feels heavy and likely to overwhelm rather than streamline agent workflows.
The set covers read operations and basic state transitions across tasks, bugs, stories, and test cases, plus exports and analysis helpers. However, there are notable gaps: no create/update for stories or bugs, no add-comment operations, and no deeper test-management workflows.