Marketplace for trusted AI agent skills

Skill Detail

Connect Azure DevOps projects, work items, repos, and pipelines to MCP agents

Use Azure DevOps MCP when an agent needs governed access to ADO projects, work items, builds, repos, test plans, wikis, and pipelines.

Integrations & ConnectorsMCP
Integrations & Connectors MCP Security Reviewed
⭐ 1.7k GitHub stars ⬇ 334.3k/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill connect-azure-devops-projects-work-items-repos-and-pipelines-to-mcp-agents Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
View source Documentation
At a glance
Tools required
Azure DevOps organization, MCP-capable client, Microsoft authentication, and Node.js 20+ for the optional local stdio server
Install & setup
Start with the Azure DevOps Remote MCP Server using the upstream onboarding documentation. For local stdio use, install Node.js 20+ and configure the MCP client command as npx -y @azure-devops/mcp <organization>, optionally restricting domains such as core, work, work-items, search, repositories, wiki, test-plans, pipelines, or advanced-security.
Author
Microsoft
Publisher
Organization
Last updated
May 25, 2026
Quick brief

Use Azure DevOps MCP when an agent needs to inspect or update Azure DevOps context through a bounded MCP surface: list projects, retrieve work items, inspect builds, search repos, manage wiki pages, review test plans, or operate pipeline context during engineering workflows. The operator connects the remote Azure DevOps MCP server or configures the local stdio server, scopes the organization and optional domains, authenticates through the supported Microsoft flow, and then asks the agent for concrete DevOps actions with the returned project context. Invoke it instead of using the Azure DevOps UI manually when the job is to let an MCP-capable coding or operations agent gather ADO evidence, summarize current state, draft updates, or coordinate follow-up work. The scope boundary is Azure DevOps MCP tool access for project, work, repo, wiki, test, and pipeline workflows; it is not a generic Microsoft product card, cloud platform listing, or SDK wrapper.

How it works

What this skill actually does

Inputs and prerequisites: Azure DevOps organization, MCP-capable client, Microsoft authentication, and Node.js 20+ for the optional local stdio server.

Setup notes: Start with the Azure DevOps Remote MCP Server using the upstream onboarding documentation. For local stdio use, install Node.js 20+ and configure the MCP client command as npx -y @azure-devops/mcp , optionally restricting domains such as core, work, work-items, search, repositories, wiki, test-plans, pipelines, or advanced-security.

Source and verification boundary: use https://learn.microsoft.com/en-us/azure/devops/mcp-server/remote-mcp-server?view=azure-devops as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a MCP workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.