pingcode-mcp
Related Servers
Alternatives to pingcode-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceRead-only MCP server that provides coding agents with traceable Markdown context from PingCode Wiki, enabling listing of spaces/pages and retrieving requirement context.5 npm-
- AlicenseAqualityAmaintenanceMCP server for Jira integration with stdio transport. Enables reading, writing, and managing Jira issues and projects directly from Claude Desktop. Supports issue creation, updates, comments, JQL search, and project management.231,787 npm14MIT

teamhood-mcpofficial
FlicenseAqualityCmaintenanceA read-only MCP server that enables querying Teamhood workspaces, users, boards, items, and time logs through the Teamhood Open API, running locally via stdio so your API key stays on your machine.10-- AlicenseNot gradedqualityCmaintenanceA read-only MCP server for querying Redmine issue data via the Redmine REST API, designed for seamless integration with AI assistants.15 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables reading and updating Azure DevOps work items, comments, metadata, and relations from an MCP-compatible client.898 npmMIT
- FlicenseAqualityDmaintenanceA lightweight MCP server providing read access to craft.io workspaces and items like products and features. It enables users to query workspace details and retrieve specific items through the Model Context Protocol.4-
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one checks connectivity/authentication, the other retrieves work item details. There is no overlap or ambiguity between them.
Both tools follow a consistent 'pingcode_<verb>_<noun>' pattern (check_connection, get_work_item_detail), using snake_case and clear verbs. The naming is uniform and predictable.
With only 2 tools, the server feels thin for a PingCode integration. This is borderline—there is no bloat, but the scope is very narrow, which earns a 3 per the calibration.
The tool surface is severely incomplete for a PingCode MCP server. It only provides connectivity checking and reading a work item, missing any create, update, list, search, or delete operations. Agents would hit immediate dead ends for any workflow beyond a simple read.