ZenTao MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | 日志级别，例如 info | |
| ZENTAO_TOKEN | No | 自动登录用的 token | |
| ZENTAO_ACCOUNT | No | 自动登录用的账号 | |
| ZENTAO_BASE_URL | No | 禅道 API V1 根地址，如 http://host/zentao/api.php/v1 | |
| ZENTAO_PASSWORD | No | 自动登录用的密码 | |
| ZENTAO_HTTP_BACKEND | No | HTTP 后端，axios 或 curl；未设置时 Linux/macOS 默认 curl，Windows 默认 axios |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| initZentaoC | 初始化禅道连接并登录（支持 password 或 token）。 |
| getProductsB | 获取禅道产品列表。 |
| getMyBugsB | 按状态与产品筛选我的 bug 列表。 |
| getBugDetailB | 查看单个 bug 详情。 |
| resolveBugC | 提交 Bug 解决动作（fixed/notrepro/duplicate/...）。 |
| activateBugB | 激活（重新打开）Bug，对应禅道 API v1：POST /bugs/{id}/active。适用于已解决/已关闭后重新激活。 |
| healthCheckB | 检查当前会话与服务可用性。 |
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 clearly distinct purpose with no ambiguity. activateBug, resolveBug, getBugDetail, and getMyBugs handle different bug lifecycle stages and views, while getProducts, healthCheck, and initZentao cover separate administrative and setup functions. The descriptions make it easy to distinguish between tools like activateBug (reopen) and resolveBug (close with resolution).
The naming follows a mostly consistent verb_noun pattern with minor deviations. Tools like activateBug, getBugDetail, getMyBugs, getProducts, and resolveBug use clear action-object naming. However, healthCheck and initZentao deviate slightly by using compound nouns without verbs, though they remain readable and intuitive.
With 7 tools, this server is well-scoped for bug tracking and system management in ZenTao. Each tool earns its place by covering essential operations: bug lifecycle (activate, resolve, view), product listing, and system setup/health. The count is neither too sparse nor bloated, fitting the domain appropriately.
The tool set provides strong coverage for bug management with create, read, update (activate/resolve), and delete implied through resolution. Minor gaps exist, such as no explicit tool for creating bugs or managing other entities like tasks or users, but agents can work around this with the available tools for core workflows.