A
licenseB
qualityC
maintenanceEnables AI assistants to interact with Azure DevOps, providing tools for managing work items, repositories, pipelines, and more through the Model Context Protocol.
100
7 npm
MIT
ado-workflows-mcp
by grimlor
Related Servers
Alternatives to ado-workflows-mcp
No user-submitted related servers found.
Related Servers
- 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,759 npmMIT
- 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.-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Azure DevOps repositories and pull requests, including listing PRs, fetching diffs, adding comments, and performing automated code reviews.-
- FlicenseCqualityDmaintenanceEnables AI agents to interact with Azure DevOps through natural language, supporting work items, pull requests, sprints, boards, teams, repositories, and wiki pages.30-
Azure DevOps MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceProvides Azure DevOps tooling for AI agents, enabling interaction with projects, work items, repositories, and pipelines through natural language.151,759 npm2,011MIT
TDQS
A3.6/5.0
Scored across 45 tools
Disambiguation4/5
Most tools have clearly distinct purposes, especially the PR and work item operations. However, the context management tools (set, clear, get status, discover, list) are numerous and could be confusing, though they perform different actions.
Naming Consistency4/5
Naming predominantly follows a verb_noun pattern in snake_case, but there is inconsistency between using 'pr' (add_pr_label, list_pr_reviewers) and 'pull_request' (abandon_pull_request, complete_pull_request). This mixing is minor but noticeable.
Tool Count2/5
45 tools is excessive for the apparent scope. Many tools are redundant (e.g., three comment posting tools) and the context management could be streamlined. The count feels bloated and increases cognitive load.
Completeness4/5
Core PR and work item lifecycles are well-covered, including creation, updates, reviews, and linking. Minor gaps exist (e.g., no delete work item), but the overall surface is rich. The analytics tools add valuable capabilities.
Maintenance
ActivityInactive
ResponsivenessNo issues