A
licenseNot graded
qualityB
maintenanceMCP server for Azure DevOps Server 2022 (on-premises) that enables AI assistants to interact with work items, repositories, builds, and sprints through 29 tools.
21 npm
MIT
mcp-devops-onpremise
by zwitbaum
Related Servers
Alternatives to mcp-devops-onpremise
No user-submitted related servers found.
Related Servers
- 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.39559 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI assistants to manage Azure DevOps resources including Work Items, Git repositories, pipelines, and user identities.11 npmMIT
- FlicenseBqualityDmaintenanceAn MCP server that enables AI assistants to interact with Azure DevOps projects, work items, repositories, pipelines, wikis, and more via 21 tools.21-
- 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
- AlicenseNot gradedqualityBmaintenanceAn MCP server for automated code reviews on Azure DevOps pull requests, enabling AI assistants to fetch PR details, validate requirements, post inline comments, and set review votes.MIT
TDQS
B3.4/5.0
Scored across 36 tools
Disambiguation4/5
Resource-prefixed names clearly separate repository, pull request, wiki, and work item tools. Minor overlap exists between wiki_page_update and wiki_page_create_or_update, and several diff/commit tools are related, but the descriptions clarify the intended use of each.
Naming Consistency4/5
Most tools follow a devops_<resource>_<action> pattern with clear verbs like get, list, create, update, and delete. A few names such as devops_repository_diffs_commits, devops_repository_commit_changes, and devops_get_item_content_diff break the verb-first pattern but remain readable and predictable.
Tool Count2/5
With 36 tools, the server feels heavy even though it spans four domains. The count exceeds the 25-tool threshold, and the surface is further fragmented by granular operations such as six separate work item comment tools.
Completeness4/5
Work items, pull requests, and wiki pages have strong CRUD/lifecycle coverage, including comments, threads, links, attachments, and search. Missing repository write operations, pull request merge, and CI/CD tooling are notable gaps, but the primary workflows are not dead-ended.
Maintenance
ActivityMaintained
ResponsivenessNo issues