A
licenseNot graded
qualityF
maintenanceEnables AI assistants to interact with Azure DevOps entities like projects, repositories, work items, pull requests, and pipelines.
13 npm
17
MIT
mcp-azure-devops
by dockndevai
Related Servers
Alternatives to mcp-azure-devops
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Azure DevOps to manage work items, Git repositories, branches, commits, and projects through natural language commands.511 npm5MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with Azure DevOps APIs for managing projects, work items, repositories, pull requests, and pipelines through natural language.11 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Azure DevOps APIs for managing projects, work items, repositories, pull requests, pipelines, and more through natural language.9,196 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Azure DevOps for managing work items, repositories, wikis, and automating development workflows.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Azure DevOps projects, including work items, test results, Git repositories, and dependency analysis via the Model Context Protocol.-
TDQS
A4/5.0
Scored across 15 tools
Disambiguation5/5
Each tool targets a distinct Azure DevOps resource or action: projects, teams, team members, processes, work items, iterations, repositories, branches, pull requests, pipelines, and builds. list_* and get_* pairs are clearly complementary rather than overlapping, and query_work_items vs get_work_item is a clear search-then-fetch workflow.
Naming Consistency5/5
Tool names follow a consistent list_<resource> and get_<resource> snake_case convention, with query_work_items as the only special-case verb. No mixed casing or vague verbs like 'process' or 'run' appear, making the naming predictable and easy to navigate.
Tool Count5/5
Fifteen tools is at the upper edge of the well-scoped range but still appropriate: each tool covers a meaningful read operation on a distinct Azure DevOps entity, and none feel redundant. The count reflects a focused read-only browsing surface rather than an unwieldy grab bag.
Completeness2/5
The set covers read-only browsing across major Azure DevOps entities, but it has no create, update, delete, or run operations at all. This is especially problematic because list_processes references creating a project and list_pipelines references run_pipeline, yet neither create_project nor run_pipeline is exposed, leaving agents with dead ends and incomplete workflows.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive