F
licenseNot graded
qualityD
maintenanceMCP 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.
-
azdo-onprem-mcp
by ajithnow
Related Servers
Alternatives to azdo-onprem-mcp
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.39511 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables reading and updating Azure DevOps work items, comments, metadata, and relations from an MCP-compatible client.511 npmMIT
- 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.172,288 npmMIT
- AlicenseAqualityAmaintenanceA local MCP server that connects Claude Desktop, Claude Code, and Claude Chat to your Azure DevOps organization, enabling querying work items, reviewing pull requests, triggering pipelines, searching code, managing test plans, and updating wikis using plain language.30MIT
- AlicenseNot gradedqualityDmaintenanceA focused MCP server for Azure DevOps work item administration, enabling AI agents to create, update, query, and manage work items with full CRUD operations and advanced WIQL querying.MIT
TDQS
A4.2/5.0
Scored across 3 tools
Disambiguation5/5
Each tool targets a distinct resource/action: listProjects for projects, getWorkItem for a specific work item by ID, and searchWorkItems for finding work items by title. No overlap in functionality.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in camelCase: listProjects, getWorkItem, searchWorkItems. The naming is predictable and uniform.
Tool Count5/5
With only three tools, each serves a clear and non-redundant purpose. The count is well-scoped for a focused Azure DevOps read-only server.
Completeness2/5
The tool surface is severely limited, providing only read operations. There is no ability to create, update, or delete work items, nor any support for queries beyond title-based search. Significant gaps exist for a typical Azure DevOps integration.
Maintenance
ActivityInactive
ResponsivenessNo issues