devops-wrangler
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@devops-wrangler Show me all active bugs in the current project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
devops-wrangler
An MCP (Model Context Protocol) server for Azure DevOps work item management. Enables AI assistants like Claude to create, query, update, and manage work items, sprints, and more.
Installation
Using npx (recommended)
npx devops-wranglerGlobal installation
npm install -g devops-wranglerRelated MCP server: Azure DevOps MCP Server
Configuration
Claude Code
The easiest way to add the server:
claude mcp add --transport stdio devops-wrangler -- npx devops-wranglerOr manually add to your MCP settings (~/.claude/mcp_servers.json):
{
"mcpServers": {
"devops-wrangler": {
"command": "npx",
"args": ["devops-wrangler"]
}
}
}Claude Desktop
Add to your Claude Desktop config:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"devops-wrangler": {
"command": "npx",
"args": ["devops-wrangler"]
}
}
}Setup
Once configured, use the ado_configure tool to connect to your Azure DevOps organization:
Configure Azure DevOps with:
- PAT: your-personal-access-token
- Organization: https://dev.azure.com/your-orgCreating a Personal Access Token (PAT)
Go to Azure DevOps → User Settings → Personal Access Tokens
Create a new token with the following scopes:
Work Items: Read & Write
Project and Team: Read
Graph: Read (for user lookups)
Available Tools
Configuration
Tool | Description |
| Configure Azure DevOps connection with PAT and organization URL |
| Check current configuration status |
Projects
Tool | Description |
| List projects, set active project, or list area paths |
Work Items
Tool | Description |
| Create work items with optional hierarchy (Epic > Feature > User Story > Task) |
| Query existing work items with filters |
| Update work item fields (title, state, assignee, description, etc.) |
| Delete a work item (soft delete to recycle bin or permanent) |
| Link work items to each other, PRs, commits, or branches |
Comments & Tags
Tool | Description |
| Add or list comments on work items (supports markdown) |
| List, add, remove, or query tags |
Sprints & Plans
Tool | Description |
| List sprints, assign items to sprints, create/delete sprints |
| View delivery plans and roadmaps |
Usage Examples
Create a feature with user stories
Create a Feature called "User Authentication" with these User Stories:
- Implement login page
- Add password reset flow
- Create session managementQuery active bugs
Show me all active bugs in the projectAdd to current sprint
Create a Task called "Fix API timeout" and add it to the current sprintUpdate work item
Update work item #12345 - set state to "Active" and assign to john@example.comFeatures
Hierarchical work item creation: Create Epics with Features, User Stories, and Tasks in a single operation
Sprint management: List sprints, create new sprints, assign work items to current sprint
Markdown support: Comments and descriptions support full markdown formatting
Tag management: Add, remove, and query work items by tags
Linking: Connect work items to each other, pull requests, commits, or branches
License
ISC
Available Tools
12 toolsado_commentsA
Manage work item comments.
Actions:
add: Add comment to work item (requires: id, text)
list: List comments on work item (requires: id, optional: limit)
Markdown Support: Azure DevOps comments support full markdown formatting including bold, italic, code, lists, headers, links, and code blocks.
Inputs: id (required), action (required), text, limit.
ado_configureB
Configure Azure DevOps connection with your PAT and organization URL
Inputs: pat (required), organization (required), defaultProject.
ado_create_itemsA
Create work items in Azure DevOps with optional hierarchy (Epic > Feature > User Story > Task). Items are assigned to the configured Area Path (board). Use addToCurrentSprint=true to add items to the active sprint.
Inputs: items (required), addToCurrentSprint.
ado_delete_itemA
Delete a work item (moves to recycle bin by default, use permanent=true for hard delete)
Inputs: id (required), permanent.
ado_link_itemA
Link a work item to another work item, pull request, commit, or branch
Inputs: id (required), target (required), linkType (required), comment.
ado_plansA
Manage delivery plans (roadmaps).
Actions:
list: List delivery plans in project
get: Get plan timeline details (requires: planId, optional: startDate, endDate)
Inputs: action (required), planId, endDate, startDate.
ado_projectsA
Manage Azure DevOps projects.
Actions:
list: List all projects in organization
set: Set active project (requires: project)
areas: List area paths in active project
Inputs: action (required), project.
ado_query_itemsA
Query existing work items in the active Azure DevOps project
Inputs: type, limit, state.
ado_sprintsA
Manage sprints/iterations.
Actions:
list: List sprints for configured team (optional: timeframe)
set: Assign work item to sprint (requires: id, sprint)
create: Create a new sprint (requires: name, optional: startDate, finishDate, parent)
delete: Delete a sprint (requires: path, optional: reclassifyId)
Inputs: action (required), id, name, path, +6 more.
ado_statusA
Check current Azure DevOps configuration status
Inputs: no named parameters.
ado_tagsA
Manage work item tags in Azure DevOps.
Actions:
list: List all tags in the project (no additional params)
add: Add tags to a work item (requires: id, tags)
remove: Remove tags from a work item (requires: id, tags)
query: Find work items by tag (requires: tag, optional: limit)
Inputs: action (required), id, tag, tags, +1 more.
ado_update_itemB
Update a work item's fields (title, state, assignee, description, area path, sprint, story points)
Inputs: id (required), state, title, areaPath, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
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.
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.
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.
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
Related MCP Connectors
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
Devopness MCP server for DevOps happiness! Empower AI Agents to deploy apps and infra, to any cloud.
MCP server for building and testing AI agents with multi-model experimentation and insights.
MCP Server for JFrog, providing tools for development and artifact management.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn 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.36MIT
- AlicenseAqualityDmaintenanceAn 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.4147 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI assistants to manage Azure DevOps resources including Work Items, Git repositories, pipelines, and user identities.20 npmMIT
- AlicenseCqualityDmaintenanceA Model Context Protocol server that enables AI assistants to interact with Azure DevOps work items, projects, wikis, and boards through natural language.4194 npm4MIT