A
licenseNot graded
qualityB
maintenanceMCP server that enables AI assistants to manage Azure DevOps resources including Work Items, Git repositories, pipelines, and user identities.
21 npm
MIT
devops-wrangler
by fuseboxhq
Related Servers
Alternatives to devops-wrangler
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceAn MCP server for Azure DevOps that allows users to manage work items, sprints, iterations, and attachments. It supports custom WIQL queries and includes pre-defined prompts for common tasks like sprint planning, bug reporting, and daily standup generation.369 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-
- 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
- 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.4146 PyPIMIT
- AlicenseCqualityCmaintenanceA Model Context Protocol server that enables AI assistants to interact with Azure DevOps work items, projects, wikis, and boards through natural language.4182 npm4MIT
TDQS
A3.8/5.0
Scored across 12 tools
Disambiguation4/5
Most tools target distinct resources and actions, but there is minor overlap: sprints.set and update_item both assign work items to sprints, and tags.query partially overlaps with query_items. Descriptions clarify the intended use, so ambiguity is low.
Naming Consistency4/5
The ado_ prefix gives a consistent namespace, but naming patterns vary: some tools use verb_noun (create_items, update_item) while others are resource-only nouns with sub-actions (projects, comments, sprints, plans, tags). This is a minor inconsistency, though names remain predictable and readable.
Tool Count5/5
12 tools is well within the ideal range for a domain-specific server. Each tool covers a meaningful area of Azure DevOps, and the count feels balanced without unnecessary bloat or missing essentials.
Completeness4/5
The surface covers configuration, project selection, work item lifecycle (create, query, update, delete), linking, comments, sprints, tags, and plans. Minor gaps exist, such as lack of project creation/deletion and explicit single-item fetch, but these are not critical for the apparent focus on work item management.
Maintenance
ActivityInactive
ResponsivenessNo issues