pingcode-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PINGCODE_TOKEN | No | Existing PingCode access token (Bearer Token). One of three authentication methods. | |
| PINGCODE_PASSWORD | No | PingCode account plain text password for password authentication (sent as MD5 internally). | |
| PINGCODE_USERNAME | No | PingCode account login name or email for password authentication (alternative method). | |
| PINGCODE_CLIENT_ID | No | PingCode application Client ID for client credentials authentication (alternative method). | |
| PINGCODE_LOG_LEVEL | No | Logging level: debug, info, warn, error. | info |
| PINGCODE_MAX_PAGES | No | Maximum number of pages for paginated API requests. | 20 |
| PINGCODE_API_BASE_URL | No | Root URL of the PingCode Open API. | https://open.pingcode.com |
| PINGCODE_WEB_BASE_URL | Yes | Web page domain used for parsing work item links and password login (required). | |
| PINGCODE_CLIENT_SECRET | No | PingCode application Client Secret for client credentials authentication (alternative method). | |
| PINGCODE_MAX_RESPONSE_BYTES | No | Maximum allowed response size in bytes. | 5242880 |
| PINGCODE_REQUEST_TIMEOUT_MS | No | HTTP request timeout in milliseconds. | 15000 |
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
| Name | Description |
|---|---|
| pingcode_check_connectionA | 验证 PingCode API 地址是否可访问、Token 是否有效，并返回当前身份的非敏感摘要。 |
| pingcode_get_work_item_detailA | 读取 PingCode 工作项完整内容，支持链接、内部 ID 或编号（如 SAAS-12144）作为输入。 |
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 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.