F
licenseA
qualityB
maintenanceA local MCP server that bridges Claude Desktop/Cowork to the Azure DevOps CLI, enabling full use of az devops, az repos, az boards, az pipelines, and az artifacts commands.
12
-
azure-devops-local-mcp
by Laonnda
Related Servers
Alternatives to azure-devops-local-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA self-hosted remote MCP server for Azure DevOps that bridges OAuth 2.1 between MCP clients and Microsoft Entra ID, enabling any OAuth-capable client (e.g., Claude Code, Claude Desktop) to access Azure DevOps resources.MIT
- AlicenseBqualityDmaintenanceA read-only MCP server connecting AI assistants to Azure DevOps Server (on-premises) for browsing projects, repos, builds, work items, releases, pipelines, and test results.39898 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Azure DevOps services including work items, repositories, pipelines, wikis, and test plans through a local MCP server that provides direct access to Azure DevOps REST APIs from your code editor.126,228 npmMIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that integrates Azure DevOps with Cursor IDE, allowing Claude AI to manage projects, work items, repositories, pull requests, and test plans.148 npm12MIT
- AlicenseAqualityCmaintenanceAn MCP server that exposes 41 Azure DevOps tools to AI assistants, enabling management of pipelines, repositories, pull requests, releases, work items, test management, and wikis through natural language.41MIT
TDQS
A3.9/5.0
Scored across 30 tools
Disambiguation4/5
Tools are generally well-separated by resource domain and action, and descriptions explicitly disambiguate similar options. The main potential confusion is between list/query variants such as ado_workitems_query vs ado_workitems_list_recent and ado_wiki_list vs ado_wiki_list_pages, but the descriptions clarify the intended use.
Naming Consistency5/5
All tools follow a consistent ado_<resource>_<action> snake_case pattern, with predictable verbs like list, get, create, update, and trigger. Even multi-part actions such as get_pr_threads or create_pr_comment fit the pattern cleanly.
Tool Count2/5
30 tools is a heavy surface for an MCP server, exceeding the range where the full set can be easily held in context. The tools are organized by domain, but the overall count still creates significant selection overhead for an agent.
Completeness3/5
The server covers work items, Git/PRs, pipelines, wiki, and test management quite broadly, with good create/read/update support for work items and test plans. However, notable lifecycle gaps remain: PR creation/update/merge is missing, and wiki/test plan deletion is not exposed, which can create dead ends in common workflows.
Maintenance
ActivityMaintained
ResponsivenessNo issues