mcp-zentao
Related Servers
Alternatives to mcp-zentao
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that lets clients drive a ZenTao instance through its REST API v2, exposing 119 OpenAPI-defined operations plus plan, story, and assignment query helpers for common lookups. Enables reading and writing ZenTao data — including stories, bugs, tasks, plans, users, and status transitions — directly from Codex, Claude Desktop, and other MCP clients.20 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides an MCP server for ZenTao (禅道) project management. It enables read-only queries for projects, tasks, bugs, users, and stories, and supports write operations like task assignment, progression, and bug resolution when explicitly confirmed.21 npmMIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that integrates with Zentao's RESTful API to manage bugs, including listing, resolving, closing, and commenting, with support for product and project set contexts.1129 npm1MIT
- FlicenseNot gradedqualityAmaintenanceAn MCP server that integrates with Zentao API to provide tools for accessing tasks, bugs, and attachments from project management.2,469 npm-
- FlicenseNot gradedqualityDmaintenanceEnables query and management of Zentao bugs, tasks, projects, and iterations directly from MCP-compatible IDEs like Cursor or Claude Desktop.-
- AlicenseDqualityCmaintenanceEnables AI-powered interaction with ZenTao 11.3 legacy systems, supporting task, bug, requirement, and test case management via MCP protocol.487 npm5MIT
TDQS
Scored across 48 tools
Many tools have overlapping purposes, such as the multiple export functions (exportItems, exportStory, exportBug, exportStoriesBySearch) and the numerous analysis/generation utilities (generateStorySummary, generateBugSummary, analyzeStoryComplexity, analyzeBugPriority, analyzeTaskWorkload, generateCodePromptFromStory, generateTestPromptFromBug, generateCodeReviewChecklist). Tools like getStoryRelatedBugs and getBugRelatedStory likely refer to the same relationship, creating confusion.
The naming uses a loose verb_noun pattern, but with mixed verb styles and no coherent convention. Synonyms like get/fetch, search/export, and analyze/generate are used interchangeably. There is also inconsistent camelCase and batch prefixes (e.g., updateTask vs batchUpdateTasks) without a clear systematic structure.
48 tools is excessively heavy for a single server. While ZenTao is a broad domain, many tools are near-duplicates (multiple export variants, numerous analysis helpers) that could be consolidated. The count appears inflated with convenience wrappers rather than essential distinct operations.
The set covers fetching and updating tasks/bugs/stories but lacks core lifecycle operations like createStory, updateStory, deleteBug, or closeTask. Test case creation exists but no update/delete, and there is no createTestTask. The heavy emphasis on analysis and export leaves gaps in standard CRUD workflows, causing incomplete coverage.