DevOps Enhanced MCP
Related Servers
Alternatives to DevOps Enhanced MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA self-hosted remote MCP server for Azure DevOps that bridges OAuth 2.1 between MCP clients and Microsoft Entra ID, enabling any OAuth-capable client (e.g., Claude Code, Claude Desktop) to access Azure DevOps resources.MIT
- AlicenseNot gradedqualityCmaintenanceMulti-user wrapper around Microsoft's Azure DevOps MCP server, enabling AI agents to authenticate per-user and interact with Azure DevOps tools via isolated PATs.898 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI assistants to manage Azure DevOps resources including Work Items, Git repositories, pipelines, and user identities.20 npmMIT
- FlicenseAqualityBmaintenanceA local MCP server that bridges Claude Desktop/Cowork to the Azure DevOps CLI, enabling full use of az devops, az repos, az boards, az pipelines, and az artifacts commands.12-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Azure DevOps services including work items, repositories, pipelines, wikis, and test plans through a local MCP server that provides direct access to Azure DevOps REST APIs from your code editor.126,228 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server that provides tools to interact with Azure DevOps, including querying work items, repositories, pull requests, builds, commits, and creating work items via a standardized interface.-
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose targeting specific Azure DevOps resources and actions. For example, create-work-item, get-work-items, update-work-item, and add-work-item-comment form a coherent work item lifecycle without overlap, while get-builds, get-pipeline-status, and trigger-pipeline cover distinct pipeline operations. No tools appear to do the same thing.
All tools follow a consistent verb_noun pattern with hyphens, using clear action verbs like 'get', 'create', 'update', 'add', and 'trigger' paired with specific nouns. There are no deviations in naming conventions, making the set predictable and readable throughout.
With 10 tools, this server is well-scoped for Azure DevOps operations, covering work items, pipelines, repositories, and pull requests. Each tool earns its place by addressing a core DevOps workflow, avoiding both thin coverage and bloat.
The tool surface provides strong coverage for key Azure DevOps domains, including CRUD operations for work items and pipeline management. Minor gaps exist, such as no tools for creating or merging pull requests or managing repository branches, but agents can work around these with the available tools.