Skip to main content
Glama
aipper

zentao-mcp-server

by aipper
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ZENTAO_DEBUGNoOptional flag to enable debug logging (true/false)
ZENTAO_ACCOUNTYesThe account (username) to authenticate with ZenTao API
ZENTAO_BASE_URLYesThe base URL of the ZenTao instance (e.g., https://zentao.example.com)
ZENTAO_PASSWORDYesThe password for the ZenTao account
ZENTAO_API_PREFIXNoOptional custom API prefix (default /api.php/v1)
ZENTAO_PRODUCT_IDNoOptional product ID if the instance requires it
ZENTAO_TOKEN_PATHNoOptional custom token endpoint path
ZENTAO_MY_BUGS_PATHNoOptional custom path for 'my bugs' API endpoint (e.g., /my/bug)
ZENTAO_PROJECT_SET_IDNoOptional project set ID for project set perspective
ZENTAO_ALLOW_INSECURE_HTTPNoOptional flag to allow HTTP instead of HTTPS (true/false)
ZENTAO_BUGS_FALLBACK_PATHSNoOptional comma-separated fallback paths for bugs list
ZENTAO_PROJECT_SET_BUGS_PATHSNoOptional project set bugs path template supporting {projectSetId}

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_tokenB

Get or refresh ZenTao API token (cached).

list_my_projectsC

List projects I participate in (heuristic filtering). Not reliable for project-set-only bugs when the project set has no concrete projects.

get_my_bugsA

List bugs assigned to me (supports status/keyword/limit/page filter). For project-set scope, prefer projectSetId or /my/bug instead of relying on list_my_projects.

get_bug_detailA

Get bug detail by ID.

resolve_bugA

Resolve one bug by ID via POST /bugs/{id}/resolve. REQUIREs non-empty solutionModules {rootCause, fixApproach, logicChange, impact} — without it the resolve call will REJECT with an error. Plain comment/solution is no longer accepted. Many instances require resolvedBuild (解决版本); pass it or set ZENTAO_DEFAULT_RESOLVED_BUILD (e.g. trunk). Do NOT use raw HTTP PUT/edit as a resolve substitute — it only flips status without writing solution text.

batch_resolve_my_bugsA

Batch resolve my bugs via the real resolve API (default status=active, resolution=fixed). REQUIRES shared non-empty solutionModules {rootCause, fixApproach, logicChange, impact} — without it the batch will REJECT with an error. Plain comment/solution is no longer accepted. Requires resolvedBuild or ZENTAO_DEFAULT_RESOLVED_BUILD on instances that validate 解决版本. Prefer projectSetId or /my/bug for project-set scope.

close_bugC

Close one bug by ID.

verify_bugA

Verify bug result: pass -> close, fail -> activate.

comment_bugA

Add comment to one bug by ID. REQUIRES solutionModules {rootCause, fixApproach, logicChange, impact} — server auto-formats into 【根因】【修复思路】【改动逻辑】【影响范围】 multi-line template text. Plain comment without solutionModules is no longer accepted.

upload_attachmentA

Upload a file (screenshot, log) and attach to a bug as visual evidence. Use after bug fix to provide screenshot proof.

download_attachmentA

Download a file/attachment from ZenTao by fileID and save to local disk. Uses API Token auth. Returns saved path and file size.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aipper/zentao-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server