What can @azure-devops/mcp do?

azure devops work item crud operations via mcp protocol, azure devops repository and git operations via mcp, azure devops pipeline and build execution via mcp, azure devops test results and test plan management via mcp, azure devops project and team configuration queries via mcp, azure devops release and deployment management via mcp

@azure-devops/mcp

MCP ServerFree

MCP server for interacting with Azure DevOps

Open Source

/ 100

6 capabilities

Capabilities6 decomposed

azure devops work item crud operations via mcp protocol

Medium confidence

Enables Claude and other MCP clients to create, read, update, and delete work items (user stories, bugs, tasks) in Azure DevOps projects through standardized MCP tool calls. Translates MCP function schemas into Azure DevOps REST API calls, handling authentication via Personal Access Tokens (PAT) and marshaling work item fields (title, description, state, assignee, area path, iteration) between client and server.

Solves for

Programmatically create bug reports from error logs or test failures without leaving ClaudeQuery and filter work items by project, iteration, or state to build context-aware task listsUpdate work item status, assignee, or description in response to conversation contextDelete or archive completed work items as part of automated cleanup workflows

Best for

Teams using Azure DevOps as their primary project management system

AI-assisted development workflows where Claude needs to interact with backlog items

DevOps engineers building autonomous agents that manage work item lifecycle

Requires

Azure DevOps organization and project with at least one team

Personal Access Token (PAT) with 'Work Items (read, write)' scope

Node.js 16+ runtime

Limitations

Requires valid Azure DevOps Personal Access Token (PAT) with appropriate scopes — token leakage exposes work item access

No built-in caching of work item state — each query hits Azure DevOps REST API, adding latency for high-frequency operations

Limited to work item fields exposed by Azure DevOps REST API v7.0+ — custom fields may require additional mapping

What makes it unique

Implements MCP server pattern specifically for Azure DevOps, translating MCP tool schemas directly to Azure DevOps REST API endpoints with PAT-based authentication, enabling Claude and other MCP clients to manipulate work items without custom integrations

vs alternatives

Provides native MCP integration for Azure DevOps work items, whereas alternatives like Azure DevOps CLI or REST API clients require manual orchestration and lack Claude-native tool calling

azure devops repository and git operations via mcp

Medium confidence

Exposes git repository operations (clone, branch listing, commit history, pull request creation/review) and repository metadata queries through MCP tool calls. Translates MCP requests into Azure DevOps Git REST API calls, managing authentication and handling repository references (project, repo name, branch names) to enable Claude to interact with source control without direct git CLI access.

Solves for

List branches and commits in a repository to understand code history and current stateCreate pull requests programmatically with title, description, and source/target branchesQuery commit history and file changes to provide context for code review or debuggingRetrieve repository metadata (default branch, clone URLs, permissions) for CI/CD setup

Best for

Development teams using Azure Repos (Azure DevOps git) who want Claude to assist with PR creation and code review

CI/CD pipelines that need to query repository state or create PRs based on automated decisions

Developers building AI-assisted code review agents that need git history context

Requires

Azure DevOps organization with Git repositories (Azure Repos)

Personal Access Token (PAT) with 'Code (read, write)' scope

Node.js 16+ runtime

Limitations

No direct file read/write — repository operations are limited to git metadata and PR management, not file content manipulation

Commit history queries return paginated results; large repositories may require multiple API calls to retrieve full history

Pull request creation requires valid source and target branches — no automatic branch creation

What makes it unique

Provides MCP-native git repository operations for Azure Repos, abstracting Azure DevOps Git REST API behind MCP tool schemas, enabling Claude to query branch/commit state and create PRs without git CLI or direct API knowledge

vs alternatives

Simpler than managing git CLI or REST API clients directly; provides Claude-native tool calling for Azure Repos operations, whereas GitHub-focused tools (GitHub MCP) don't support Azure DevOps

azure devops pipeline and build execution via mcp

Medium confidence

Enables triggering, querying, and monitoring Azure Pipelines (CI/CD) builds through MCP tool calls. Translates MCP requests into Azure DevOps Pipelines REST API, handling pipeline definitions, build queuing, status polling, and artifact retrieval. Supports parameterized pipeline execution (passing variables to pipeline runs) and build log streaming for debugging.

Solves for

Trigger a CI/CD pipeline run with custom parameters (branch, environment, feature flags) from ClaudeQuery build status and history to understand deployment state without manual dashboard checksRetrieve build logs and artifacts for debugging failed builds or analyzing test resultsMonitor pipeline execution and wait for completion before proceeding with dependent tasks

Best for

DevOps teams automating CI/CD workflows with Claude-driven orchestration

Developers who want to trigger builds and check status from conversational AI without leaving Claude

Autonomous agents that need to manage deployment pipelines based on code changes or events

Requires

Azure DevOps organization with configured Azure Pipelines

Personal Access Token (PAT) with 'Build (read, execute)' scope

Node.js 16+ runtime

Limitations

Pipeline execution is asynchronous — no built-in polling/waiting mechanism; clients must implement their own status checks

Build logs are returned as plain text; no structured parsing of test results or error patterns

Limited to pipeline execution and status — no pipeline definition editing or creation

What makes it unique

Exposes Azure Pipelines execution and monitoring as MCP tools, allowing Claude to queue builds with parameters and poll status, whereas most CI/CD integrations require webhook-based triggering or manual dashboard interaction

vs alternatives

Provides synchronous pipeline queuing and status queries via MCP, simpler than managing Azure DevOps REST API directly or setting up webhook-based automation

azure devops test results and test plan management via mcp

Medium confidence

Provides access to test execution results, test case management, and test plan operations through MCP tool calls. Translates MCP requests into Azure DevOps Test Management REST API, enabling queries of test runs, test case status, and test plan metadata. Supports filtering by test suite, configuration, and outcome (passed/failed/skipped) to enable Claude to analyze test health and create test cases.

Solves for

Query test results from recent builds to identify failing tests and their error messagesCreate or update test cases and test plans programmatically based on requirementsRetrieve test coverage metrics and test execution history for quality reportingFilter test results by configuration, environment, or test suite to diagnose environment-specific failures

Best for

QA teams using Azure Test Plans who want Claude to analyze test results and suggest fixes

DevOps engineers building autonomous test orchestration and reporting

Development teams integrating test health monitoring into AI-assisted workflows

Requires

Azure DevOps organization with Test Plans configured

Personal Access Token (PAT) with 'Test Management (read, write)' scope

Node.js 16+ runtime

Limitations

Test result queries are read-heavy; no built-in support for bulk test result updates or re-runs

Test case creation requires valid test suite and project context; no automatic test suite discovery

Error messages and stack traces are returned as plain text; no structured parsing of failure root causes

What makes it unique

Integrates Azure Test Plans as MCP tools, allowing Claude to query test results and create test cases without manual dashboard navigation, whereas most test management tools lack conversational AI integration

vs alternatives

Provides Claude-native access to test results and test case management, simpler than parsing test reports manually or querying Azure DevOps REST API directly

azure devops project and team configuration queries via mcp

Medium confidence

Exposes project metadata, team membership, area paths, and iteration (sprint) information through MCP tool calls. Translates MCP requests into Azure DevOps Core REST API to retrieve organizational structure, team configurations, and project settings. Enables Claude to understand project context (available teams, iterations, area paths) for work item operations and team-aware task assignment.

Solves for

List all teams and members in a project to understand organizational structure and find appropriate assigneesRetrieve current and upcoming iterations (sprints) to assign work items to the correct sprintQuery area paths to understand project structure and assign work items to the correct team areaFetch project settings and permissions to validate operations before attempting them

Best for

Teams managing complex multi-team projects who need Claude to understand organizational structure

Autonomous agents that need to discover available teams, iterations, and areas before creating work items

DevOps teams building context-aware task assignment and routing

Requires

Azure DevOps organization and project

Personal Access Token (PAT) with 'Project & Team (read)' scope

Node.js 16+ runtime

Limitations

Read-only operations — no support for creating teams, iterations, or area paths

Team membership queries return basic info (name, email); no detailed permission or role information

Iteration queries return metadata but no work item counts or burndown data

What makes it unique

Provides MCP-based project and team discovery, allowing Claude to query organizational structure and iteration metadata to inform work item creation and assignment, whereas most integrations assume static team/iteration knowledge

vs alternatives

Enables Claude to dynamically discover teams, iterations, and area paths, reducing manual configuration and enabling context-aware work item operations

azure devops release and deployment management via mcp

Medium confidence

Exposes release pipeline operations (create releases, approve deployments, query release status) through MCP tool calls. Translates MCP requests into Azure DevOps Release Management REST API, handling release definitions, deployment approvals, and environment-specific deployment status. Supports querying release history and triggering deployments to specific environments with approval workflows.

Solves for

Create a release from a build artifact and trigger deployment to a specific environmentQuery release status and deployment progress across multiple environmentsApprove pending deployments programmatically based on conditions or Claude's analysisRetrieve release history and deployment logs for auditing and troubleshooting

Best for

DevOps teams automating release workflows with Claude-driven approval and orchestration

Autonomous deployment agents that need to manage multi-environment releases

Teams implementing AI-assisted release management and deployment monitoring

Requires

Azure DevOps organization with Release Pipelines configured

Personal Access Token (PAT) with 'Release (read, execute, manage approvals)' scope

Node.js 16+ runtime

Limitations

Release creation requires valid build artifact and release definition — no automatic release definition generation

Deployment approvals are manual operations; no automatic approval logic based on conditions

Release history queries are paginated; large release histories require multiple API calls

What makes it unique

Provides MCP-based release and deployment management, allowing Claude to create releases, query deployment status, and approve deployments, whereas most release management tools require manual dashboard interaction or webhook-based automation

vs alternatives

Enables Claude to orchestrate multi-environment releases and approvals via conversational interface, simpler than managing Release Management REST API directly

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with @azure-devops/mcp, ranked by overlap. Discovered automatically through the match graph.

MCP Server39

@azure-devops/mcp

MCP server for interacting with Azure DevOps

azure devops work item crud operations via mcpazure repos git repository querying and branch managementazure devops pull request and code review orchestrationazure pipelines build and release orchestration

4 shared capabilities

MCP Server36

@azure/mcp-linux-x64

Azure MCP Server - Model Context Protocol implementation for Azure, for linux on x64

azure operation invocation and state mutation through mcpazure authentication and credential management via mcpmcp protocol server implementation for azure

3 shared capabilities

MCP Server42

@azure/mcp

Azure MCP Server - Model Context Protocol implementation for Azure

azure resource tool exposure via mcp protocolazure container and kubernetes resource managementazure authentication and credential management for mcp context

3 shared capabilities

MCP Server45

Azure MCP Server

Provides Model Context Protocol (MCP) integration and tooling for Azure in Visual Studio Code.

azure service tool exposure via mcp protocol

1 shared capability

MCP Server41

git-mcp

Put an end to code hallucinations! GitMCP is a free, open-source, remote MCP server for any GitHub project

mcp-compliant repository tool exposure via serverless workers

1 shared capability

MCP Server40

servers

Model Context Protocol Servers

git repository operations server with multi-repo support and path validation

1 shared capability

Best For

✓Teams using Azure DevOps as their primary project management system
✓AI-assisted development workflows where Claude needs to interact with backlog items
✓DevOps engineers building autonomous agents that manage work item lifecycle
✓Development teams using Azure Repos (Azure DevOps git) who want Claude to assist with PR creation and code review
✓CI/CD pipelines that need to query repository state or create PRs based on automated decisions
✓Developers building AI-assisted code review agents that need git history context
✓DevOps teams automating CI/CD workflows with Claude-driven orchestration
✓Developers who want to trigger builds and check status from conversational AI without leaving Claude

Known Limitations

⚠Requires valid Azure DevOps Personal Access Token (PAT) with appropriate scopes — token leakage exposes work item access
⚠No built-in caching of work item state — each query hits Azure DevOps REST API, adding latency for high-frequency operations
⚠Limited to work item fields exposed by Azure DevOps REST API v7.0+ — custom fields may require additional mapping
⚠No transactional support — bulk operations are sequential, not atomic
⚠No direct file read/write — repository operations are limited to git metadata and PR management, not file content manipulation
⚠Commit history queries return paginated results; large repositories may require multiple API calls to retrieve full history

Requirements

Azure DevOps organization and project with at least one teamPersonal Access Token (PAT) with 'Work Items (read, write)' scopeNode.js 16+ runtimeMCP client compatible with tool-use-integration protocol (Claude, etc.)Azure DevOps organization with Git repositories (Azure Repos)Personal Access Token (PAT) with 'Code (read, write)' scopeMCP client with tool-use-integration supportAzure DevOps organization with configured Azure Pipelines

Input / Output

Accepts: JSON-structured work item payloads (title, description, state, assignee, area path, iteration), Query filters (project name, work item type, state, assigned to), Work item IDs (integers), Repository identifiers (project name, repository name), Branch names (source and target for PR operations), PR metadata (title, description, reviewers), Commit/history query filters, Pipeline ID or name, Build parameters (branch, variables, queue name), Build ID for status/log queries, Test run ID or test plan ID, Test suite and test case identifiers, Filter criteria (outcome, configuration, tester), Project name or ID, Team name or ID (optional for team-specific queries), Release definition ID or name, Build artifact ID or version, Environment name for deployment targeting, Approval comments and decision (approve/reject)

Produces: JSON work item objects with full metadata (ID, title, state, assignee, created date, updated date), Paginated work item lists with query results, Operation confirmation responses (success/failure with error details), JSON branch lists with metadata (name, commit ID, last updated), Commit history with author, message, date, and file changes, Pull request objects with status, reviewers, and merge state, Repository metadata (clone URLs, default branch, permissions), Build execution confirmation with build ID and queue time, Build status objects (state, result, start/finish time, queued by), Build logs as plain text or structured error summaries, Artifact metadata and download URLs, Test result objects with outcome, duration, error message, and stack trace, Test case metadata (title, steps, expected results, assigned tester), Test plan summary with pass/fail counts and coverage metrics, Test execution history with trend data, Project metadata (name, description, visibility, default team), Team list with member counts and descriptions, Team member objects (name, email, identity ID), Iteration list with start/end dates and status (active, future, past), Area path list with team ownership, Release object with version, status, and created date, Deployment status per environment (pending, in progress, succeeded, failed), Approval request objects with pending approvers and deadline, Release logs and deployment history

UnfragileRank

Adoption67%(30% weight)

Quality14%(25% weight)

Ecosystem30%(25% weight)

Match Graph10%(15% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

6 capabilities

Visit @azure-devops/mcp→

Package Details

npm

Registry

2.6.0

Version

114,267

Weekly Downloads

About

MCP server for interacting with Azure DevOps

Alternatives to @azure-devops/mcp

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of @azure-devops/mcp?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

mcp registry

Looking for something else?

Search →

Capabilities6 decomposed

azure devops work item crud operations via mcp protocol

Medium confidence

Solves for

Best for

Teams using Azure DevOps as their primary project management system

AI-assisted development workflows where Claude needs to interact with backlog items

DevOps engineers building autonomous agents that manage work item lifecycle

Requires

Azure DevOps organization and project with at least one team

Personal Access Token (PAT) with 'Work Items (read, write)' scope

Node.js 16+ runtime

Limitations

Requires valid Azure DevOps Personal Access Token (PAT) with appropriate scopes — token leakage exposes work item access

No built-in caching of work item state — each query hits Azure DevOps REST API, adding latency for high-frequency operations

Limited to work item fields exposed by Azure DevOps REST API v7.0+ — custom fields may require additional mapping

What makes it unique

vs alternatives

Provides native MCP integration for Azure DevOps work items, whereas alternatives like Azure DevOps CLI or REST API clients require manual orchestration and lack Claude-native tool calling

azure devops repository and git operations via mcp

Medium confidence

Solves for

Best for

Development teams using Azure Repos (Azure DevOps git) who want Claude to assist with PR creation and code review

CI/CD pipelines that need to query repository state or create PRs based on automated decisions

Developers building AI-assisted code review agents that need git history context

Requires

Azure DevOps organization with Git repositories (Azure Repos)

Personal Access Token (PAT) with 'Code (read, write)' scope

Node.js 16+ runtime

Limitations

No direct file read/write — repository operations are limited to git metadata and PR management, not file content manipulation

Commit history queries return paginated results; large repositories may require multiple API calls to retrieve full history

Pull request creation requires valid source and target branches — no automatic branch creation

What makes it unique

vs alternatives

Simpler than managing git CLI or REST API clients directly; provides Claude-native tool calling for Azure Repos operations, whereas GitHub-focused tools (GitHub MCP) don't support Azure DevOps

azure devops pipeline and build execution via mcp

Medium confidence

Solves for

Best for

DevOps teams automating CI/CD workflows with Claude-driven orchestration

Developers who want to trigger builds and check status from conversational AI without leaving Claude

Autonomous agents that need to manage deployment pipelines based on code changes or events

Requires

Azure DevOps organization with configured Azure Pipelines

Personal Access Token (PAT) with 'Build (read, execute)' scope

Node.js 16+ runtime

Limitations

Pipeline execution is asynchronous — no built-in polling/waiting mechanism; clients must implement their own status checks

Build logs are returned as plain text; no structured parsing of test results or error patterns

Limited to pipeline execution and status — no pipeline definition editing or creation

What makes it unique

vs alternatives

Provides synchronous pipeline queuing and status queries via MCP, simpler than managing Azure DevOps REST API directly or setting up webhook-based automation

azure devops test results and test plan management via mcp

Medium confidence

Solves for

Best for

QA teams using Azure Test Plans who want Claude to analyze test results and suggest fixes

DevOps engineers building autonomous test orchestration and reporting

Development teams integrating test health monitoring into AI-assisted workflows

Requires

Azure DevOps organization with Test Plans configured

Personal Access Token (PAT) with 'Test Management (read, write)' scope

Node.js 16+ runtime

Limitations

Test result queries are read-heavy; no built-in support for bulk test result updates or re-runs

Test case creation requires valid test suite and project context; no automatic test suite discovery

Error messages and stack traces are returned as plain text; no structured parsing of failure root causes

What makes it unique

vs alternatives

Provides Claude-native access to test results and test case management, simpler than parsing test reports manually or querying Azure DevOps REST API directly

azure devops project and team configuration queries via mcp

Medium confidence

Solves for

Best for

Teams managing complex multi-team projects who need Claude to understand organizational structure

Autonomous agents that need to discover available teams, iterations, and areas before creating work items

DevOps teams building context-aware task assignment and routing

Requires

Azure DevOps organization and project

Personal Access Token (PAT) with 'Project & Team (read)' scope

Node.js 16+ runtime

Limitations

Read-only operations — no support for creating teams, iterations, or area paths

Team membership queries return basic info (name, email); no detailed permission or role information

Iteration queries return metadata but no work item counts or burndown data

What makes it unique

vs alternatives

Enables Claude to dynamically discover teams, iterations, and area paths, reducing manual configuration and enabling context-aware work item operations

azure devops release and deployment management via mcp

Medium confidence

Solves for

Best for

DevOps teams automating release workflows with Claude-driven approval and orchestration

Autonomous deployment agents that need to manage multi-environment releases

Teams implementing AI-assisted release management and deployment monitoring

Requires

Azure DevOps organization with Release Pipelines configured

Personal Access Token (PAT) with 'Release (read, execute, manage approvals)' scope

Node.js 16+ runtime

Limitations

Release creation requires valid build artifact and release definition — no automatic release definition generation

Deployment approvals are manual operations; no automatic approval logic based on conditions

Release history queries are paginated; large release histories require multiple API calls

What makes it unique

vs alternatives

Enables Claude to orchestrate multi-environment releases and approvals via conversational interface, simpler than managing Release Management REST API directly

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to @azure-devops/mcp

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

@azure-devops/mcp

Capabilities6 decomposed

azure devops work item crud operations via mcp protocol

azure devops repository and git operations via mcp

azure devops pipeline and build execution via mcp

azure devops test results and test plan management via mcp

azure devops project and team configuration queries via mcp

azure devops release and deployment management via mcp

Related Artifactssharing capabilities

@azure-devops/mcp

@azure/mcp-linux-x64

@azure/mcp

Azure MCP Server

git-mcp

servers

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to @azure-devops/mcp

Are you the builder of @azure-devops/mcp?

Get the weekly brief

Data Sources

@azure-devops/mcp

Capabilities6 decomposed

azure devops work item crud operations via mcp protocol

azure devops repository and git operations via mcp

azure devops pipeline and build execution via mcp

azure devops test results and test plan management via mcp

azure devops project and team configuration queries via mcp

azure devops release and deployment management via mcp

Related Artifactssharing capabilities

@azure-devops/mcp

@azure/mcp-linux-x64

@azure/mcp

Azure MCP Server

git-mcp

servers

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to @azure-devops/mcp

Are you the builder of @azure-devops/mcp?

Get the weekly brief

Data Sources