mcp-ado-browser
Related Servers
Alternatives to mcp-ado-browser
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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.97,581 npmMIT
- AlicenseBqualityCmaintenanceA 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.39716 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Azure DevOps projects, including work items, test results, Git repositories, and dependency analysis via the Model Context Protocol.-
- 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.97,581 npmMIT
- AlicenseAqualityBmaintenanceEnables read-only interaction with Azure DevOps Classic Releases, including listing organizations, projects, release definitions, environments, and retrieving release variables through MCP tools.7MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with Azure DevOps, providing tools for managing work items, repositories, pipelines, and more through the Model Context Protocol.10016 npmMIT
TDQS
Scored across 12 tools
Each tool targets a distinct resource/action: projects, repositories, work items, PRs, feeds, artifacts, and authentication. The only possible overlap is between get_work_item_comments and get_comment_details, but their descriptions clearly separate discussion retrieval from comment resolution plus attachment download.
Most tools follow a consistent verb_noun pattern (list_projects, search_work_items, get_pull_request). Minor deviations include get_comment_details (which omits 'work_item') and authenticate (verb-only), but these do not significantly hinder readability.
With 12 tools, the set is well-scoped for a browser-oriented Azure DevOps server. Each tool covers a meaningful browsing operation, and there is no redundancy or bloat.
The toolset provides good read-only coverage: listing and searching projects, repos, work items, PRs, and feeds, plus getting details and comments. Minor gaps include no explicit get_project or get_repository (though list tools return sufficient info) and no code search, but core browsing needs are met.