CODING DevOps MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECT | No | 默认项目名称 | |
| CODING_TOKEN | Yes | CODING Personal Access Token |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_issuesC | 查询我最近更新的工作项，可以根据其中IssueType查询，默认查询limit为20条 |
| create_issueC | 创建新的工作项 |
| delete_issueC | 删除工作项 |
| delete_projectB | 删除 CODING DevOps 中的指定项目 |
| list_projectsC | 查询当前用户在 CODING DevOps 中的项目列表 |
| create_projectC | 在 CODING DevOps 中创建新项目 |
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 6 tools
Each tool has a clearly distinct purpose targeting either issues or projects with specific CRUD operations. The separation between issue-related tools (create_issue, delete_issue, list_issues) and project-related tools (create_project, delete_project, list_projects) is unambiguous, with no functional overlap that could cause agent confusion.
All tools follow a perfectly consistent verb_noun pattern with snake_case naming. The naming convention is uniform across all six tools (create_issue, create_project, delete_issue, delete_project, list_issues, list_projects), making them predictable and easy for agents to understand and use correctly.
With 6 tools, this server is well-scoped for its DevOps project and issue management domain. Each tool earns its place by providing essential CRUD operations for both resources, avoiding both excessive complexity and insufficient coverage for the apparent scope.
The tool set provides excellent coverage for the core DevOps domain with complete CRUD operations for both issues and projects. The only minor gap is the absence of update operations (update_issue, update_project), which agents might need to work around by deleting and recreating resources, but the surface otherwise supports complete lifecycle management.