A
licenseNot graded
qualityC
maintenanceImplements a Model Context Protocol server for intelligent end-to-end requirement management and development automation, integrating with Feishu project systems.
13
5
MIT
CODING DevOps MCP Server
Related Servers
Alternatives to CODING DevOps MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceImplements the Model Context Protocol (MCP) to provide AI models with a standardized interface for connecting to external data sources and tools like file systems, databases, or APIs.1153-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with Azure DevOps resources such as projects, builds, repositories, work items, test plans, and wikis through natural language using the Model Context Protocol.151,759MIT
- AlicenseNot gradedqualityDmaintenanceProvides a standardized interface for interacting with GitHub's tools and services through the Model Context Protocol, enabling unified API access and compatibility with MCP-compliant tools.1MIT
- AlicenseNot gradedqualityDmaintenanceProvides a standardized interface for interacting with Microsoft Teams tools and services through the Model Context Protocol.1MIT
- AlicenseBqualityAmaintenanceA Model Context Protocol server that enables AI assistants to interact with Azure DevOps resources including projects, work items, repositories, pull requests, branches, and pipelines through a standardized protocol.461,794388MIT
TDQS
B3.4/5.0
Scored across 6 tools
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count5/5
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.
Completeness4/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues