Zentao Bug MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENTAO_URL | Yes | 禅道服务器的URL，例如 https://your-zentao-host | |
| ZENTAO_ACCOUNT | Yes | 禅道账号 | |
| ZENTAO_PASSWORD | Yes | 禅道密码 | |
| ZENTAO_SKIP_SSL | No | 自签名证书设为 true | false |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zentao_health_checkC | Check ZenTao MCP configuration, authentication, and write-operation gates. |
| zentao_list_my_bugsA | List bugs assigned to the current logged-in user. No product/project ID required. |
| zentao_list_bugsB | List bugs by product, project, or execution scope. |
| zentao_get_bugA | Get a single bug with raw payload and AI-friendly summary including plain-text steps. |
| zentao_resolve_bugB | Resolve a bug after fixing code. Requires ZENTAO_ALLOW_RESOLVE_BUG=true unless dryRun=true. |
| zentao_close_bugA | Close a bug. Requires ZENTAO_ALLOW_CLOSE_BUG=true unless dryRun=true. |
| zentao_activate_bugA | Re-activate a bug when fix verification fails. Requires ZENTAO_ALLOW_ACTIVATE_BUG=true unless dryRun=true. |
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 7 tools
Each tool has a unique action and target: activate, close, get, health check, list (general), list (my), resolve. No two tools overlap in purpose; an agent can clearly distinguish them.
All tools use a consistent 'zentao_verb_noun' snake_case pattern (e.g., zentao_activate_bug, zentao_list_bugs). Even zentao_health_check follows the pattern, and zentao_list_my_bugs is a natural variation. No mixing of styles.
With 7 tools covering core bug operations and a health check, the number is well-scoped for a bug management MCP server. It is neither too sparse nor too bloated.
The set covers the main bug lifecycle states (activate, resolve, close) plus listing and retrieval. However, it lacks create and update operations, which are typical for a bug tracker. This is a minor gap that agents can work around if bugs are created via other means.