ZenTao MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENTAO_TOKEN | No | 可选，已有 token；如果未提供会自动通过 /tokens 获取 | |
| ZENTAO_ACCOUNT | No | 登录账号 | |
| ZENTAO_BASE_URL | No | 禅道服务地址，形如 https://xxx.com | |
| ZENTAO_PASSWORD | No | 登录密码 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_tokenA | Fetch a token via POST /tokens using env ZENTAO_ACCOUNT/PASSWORD. Caches in-memory. |
| callA | Call any ZenTao RESTful API endpoint (api.php/v1). Automatically injects Token header. Paths accept leading slash or relative. |
| listMyProjectsC | List projects related to the current account (PM/PO/QD/RD/assigned/team). |
| searchProductsB | Search products by keyword; returns a short list of products. |
| getMyBugB | Get the first active bug assigned to me in a product (by productName). Returns full bug detail. |
| getMyBugsB | List bugs assigned to me under a product. Defaults to active bugs only. |
| getNextBugB | Get the next active bug assigned to me under a product (first match). |
| getBugStatsB | Get counts of bugs assigned to me under a product (total and active). |
| getBugDetailC | Get bug detail by ID; also extracts image URLs from steps HTML into stepsImages. |
| markBugResolvedC | Mark a bug as resolved (resolution=fixed). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ZenTao RESTful v1 endpoints summary | |
| Current ZenTao config state (env names only) | |
| Projects related to current account |
TDQS
Scored across 10 tools
The tools have clear distinctions in most cases, but there is some overlap between getMyBug, getMyBugs, and getNextBug, which all retrieve bugs assigned to the user with slight variations in scope (single vs. list vs. next). Additionally, call is a generic tool that could potentially duplicate functionality of specific tools like getBugDetail or markBugResolved, creating ambiguity in tool selection for agents.
Naming conventions are inconsistent: tools use a mix of camelCase (getBugDetail, getMyBug) and snake_case (get_token, markBugResolved), with no clear pattern. Verb usage varies, such as 'get' for retrieval and 'mark' for updates, but the inconsistency in casing and structure reduces predictability and readability.
With 10 tools, the count is well-scoped for a ZenTao bug tracking and project management server. It covers core operations like bug retrieval, resolution, project listing, and token management, providing a balanced set without being overwhelming or too sparse for the domain.
The tool set covers essential workflows for bug management (e.g., get, list, resolve) and project/product access, with minor gaps such as missing tools for creating bugs or updating bug details beyond resolution. However, the generic call tool can potentially fill these gaps, making the surface reasonably complete for typical agent tasks.