F
licenseA
qualityD
maintenanceAn MCP server that provides seamless interaction with Azure DevOps Git repositories, enabling users to manage repositories, branches, pull requests, and pipelines through natural language.
8
11 npm
3
-
MCP Azure DevOps Server
by getsomesh
Related Servers
Alternatives to MCP Azure DevOps Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that provides tools to interact with Azure DevOps, including querying work items, repositories, pull requests, builds, commits, and creating work items via a standardized interface.-
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI assistants to manage Azure DevOps resources including Work Items, Git repositories, pipelines, and user identities.11 npmMIT
- AlicenseNot gradedqualityAmaintenanceThis MCP server enables agents to list, view diffs, create, and submit Azure DevOps pull requests using VS Code's Microsoft authentication.559 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables seamless interaction with Azure DevOps for managing Git repositories, branches, and pull requests through natural language. It also supports automating and monitoring pipelines while providing secure, type-safe operations within MCP-compatible clients.11 npm-
- AlicenseBqualityBmaintenanceMCP server for Bitbucket Server integration, enabling project, repository, pull request, source code, branch, and code review operations via the Bitbucket Server APIs.2718 npmMIT
TDQS
B3.4/5.0
Scored across 4 tools
Disambiguation4/5
Repository-related tools and variable-related tools are clearly separated, and the descriptions clarify their scope. The only mild ambiguity is between get_pipeline_variables and get_variable_groups, but their descriptions differentiate pipeline-scoped variables from project-level variable groups.
Naming Consistency5/5
All tool names follow a consistent get_/search_ + noun pattern, making the naming predictable and easy to navigate. There is no mixing of conventions or vague verbs.
Tool Count4/5
Four tools is slightly thin for a server claiming Azure DevOps coverage, but each tool covers a distinct read-only concern. The count is acceptable for a focused utility server, though not richly scoped.
Completeness2/5
The server only covers limited read operations for repositories, pipeline variables, and variable groups. Major Azure DevOps areas like work items, build/release execution, pull requests, and commits are entirely absent, leaving significant gaps for common agent workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues