F
licenseNot graded
qualityD
maintenanceEnables AI assistants to interact with Azure DevOps projects, including work items, test results, Git repositories, and dependency analysis via the Model Context Protocol.
-
ado-mcp
by og-mcp
Related Servers
Alternatives to ado-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
- AlicenseAqualityCmaintenanceEnables AI agents to discover Azure DevOps repositories, manage pull requests, and interact with PR comments and reviews via the Model Context Protocol.451MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Azure DevOps for managing work items, repositories, wikis, and automating development workflows.MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to interact with Azure DevOps entities like projects, repositories, work items, pull requests, and pipelines.13 npm17MIT
- 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
TDQS
B3.3/5.0
Scored across 113 tools
Disambiguation4/5
Most tools have clearly distinct purposes, especially with well-defined descriptions for different resource types. However, a few pairs like 'ado_list_pipelines' vs 'ado_list_build_definitions' (YAML vs classic builds) could cause minor confusion without careful reading.
Naming Consistency5/5
All tool names follow a strict 'ado_verb_noun' pattern in snake_case. Verbs are consistently imperative (list, get, create, update, delete) and nouns are descriptive (repo, branch, pr, work_item, pipeline, etc.). No naming convention deviations are present.
Tool Count2/5
With 113 tools, the server is extremely comprehensive but far exceeds the typical well-scoped range (3-15). The high number makes it difficult for agents to efficiently navigate and choose the correct tool, and it would benefit from being split into multiple focused servers per Azure DevOps domain.
Completeness5/5
The tool surface covers an impressively broad range of Azure DevOps features: source control, pull requests, work items (with queries, comments, attachments, links), boards, sprints, backlogs, pipelines (YAML and classic), releases, test management, wikis, search, feeds, security, and analytics. Only niche areas like service connections or variable groups are missing, but the core workflows are fully supported.
Maintenance
ActivityInactive
ResponsivenessNo issues