zentao
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENTAO_TOKEN | No | API token for authentication (preferred) | |
| ZENTAO_ACCOUNT | No | Account username for login-based authentication | |
| ZENTAO_BASE_URL | Yes | Base URL of the Zentao instance | |
| ZENTAO_PASSWORD | No | Password for the account |
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 76 tools
Most tools target distinct entities and actions, but there are a few overlapping listings (e.g., zentao_list_project_testtasks and zentao_list_testtasks) that might cause confusion. However, descriptions and naming help differentiate.
All tools follow the 'zentao_verb_noun' pattern consistently, using standard verbs like list, get, create, update, delete, plus a few specific actions (assign, close, link, unlink). The pattern is highly predictable.
76 tools is on the high side but appropriate for a full-featured project management system like ZenTao, which covers numerous entities (projects, products, plans, executions, bugs, testcases, etc.). Each tool earns its place.
The tool set provides CRUD and listing for most major entities (users, products, plans, projects, executions, builds, stories, bugs, testcases, tasks, feedbacks, tickets). Minor gaps like a dedicated close or archive operation are covered by update tools.