F
licenseB
qualityD
maintenanceAn MCP server that enables AI assistants to interact with Azure DevOps projects, work items, repositories, pipelines, wikis, and more via 21 tools.
21
-
Azure DevOps MCP Server
by iimsaurav
Related Servers
Alternatives to Azure DevOps MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI assistants to manage Azure DevOps resources including Work Items, Git repositories, pipelines, and user identities.11 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides Azure DevOps integration for AI assistants, enabling them to list projects, run pipelines, analyze failures, view logs, and troubleshoot builds directly from chat interfaces.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Azure DevOps Server 2022 (on-premises) that enables AI assistants to interact with work items, repositories, builds, and sprints through 29 tools.11 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Azure DevOps through an MCP server with 34 tools for PRs, work items, repos, and branches, optimized for token efficiency and agent-first workflows.4 npmMIT
- FlicenseAqualityDmaintenanceAn MCP server that provides seamless interaction with Azure DevOps Git repositories, enabling users to manage repositories, branches, pull requests, and pipelines through natural language.86 npm3-
TDQS
A3.5/5.0
Scored across 41 tools
Disambiguation5/5
Each tool targets a distinct resource-action combination with clear boundaries. For example, work items have separate tools for get, create, update, delete, comments, and query, all with unambiguous names. No two tools appear to do the same thing.
Naming Consistency5/5
Tool names consistently follow a verb_noun pattern (e.g., create_work_item, list_repositories, get_pull_request). The naming style is uniform across all 41 tools, using snake_case and predictable verbs like 'get', 'list', 'create', 'update', 'delete', etc.
Tool Count3/5
41 tools is on the high side for a single server. While the server covers a broad domain (Azure DevOps), the number of tools exceeds the typical well-scoped range of 3-15. It is borderline but still manageable for an agent, though a modular breakdown might be cleaner.
Completeness4/5
The tool surface covers the major Azure DevOps areas: work items, git repos, pull requests, pipelines, releases, wikis, boards, and test runs. Minor gaps exist, such as no tool to create a pull request thread directly (only add comments) and no tool to update a release definition. Overall, the core workflows are well-supported.
Maintenance
ActivityInactive
ResponsivenessNo issues