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.
-
Azure DevOps MCP Server
by billg118
Related Servers
Alternatives to Azure DevOps MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with Azure DevOps, providing tools for managing work items, repositories, pipelines, and more through the Model Context Protocol.1008 npmMIT
- 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.171,094 npmMIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to interact with Azure DevOps entities like projects, repositories, work items, pull requests, and pipelines.15 npm17MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage work items, repos, pull requests, pipelines, boards, wikis, and test plans through Model Context Protocol tools, resources, and prompts, supporting PAT, OAuth, Managed Identity, and Service Principal authentication.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Azure DevOps to manage work items, Git repositories, branches, commits, and projects through natural language commands.778 npm5MIT
TDQS
C2.9/5.0
Scored across 49 tools
Disambiguation3/5
Several near-duplicate pairs create real ambiguity: get_project vs get_project_details, get_repository vs get_repository_details, get_repository_tree vs get_all_repositories_tree, and get_pull_request_checks vs get_pull_request_changes. Descriptions do distinguish them (e.g. 'comprehensive details' vs basic), but an agent must read carefully to pick correctly. The bulk of the remaining tools (work items, pipelines, wikis) are cleanly separated by resource.
Naming Consistency4/5
Almost everything follows a verb_noun snake_case pattern (list_*, get_*, create_*, update_*, search_*, manage_*). Minor deviations exist: get_me uses a pronoun object, get_all_repositories_tree adds an extra qualifier, and pipeline_timeline drops the verb entirely in favor of noun-first naming. These are readable but break the otherwise predictable convention.
Tool Count2/5
49 tools is well beyond a manageable surface for one server, spanning six distinct domains (orgs/projects, repos/git, work items, search, pull requests, pipelines, wikis). The volume plus the redundant *_details siblings suggests the surface could be consolidated substantially. Agents will struggle to route reliably across this many options.
Completeness3/5
Read/create/update coverage is broad and genuinely deep (work item attachments and links, PR threads and checks, pipeline logs and timelines, wiki pages). However, delete operations are notably missing across most domains: no delete_work_item, delete_branch, delete_repository, delete_pull_request, or delete_wiki_page — only attachments have a delete tool. These gaps will force agents to declare dead ends on common lifecycle tasks.
Maintenance
ActivityActive
ResponsivenessSyncing