Skip to content
Cloud InfrastructureAuto-generatedScore: 34

Azure DevOps MCP Server

The Azure DevOps Resource Provider API, developed by Microsoft, serves as a foundational interface for programmatically interacting with and managing the core components of the Azure DevOps platform.

Quick Start Summary

The Azure DevOps MCP server is a Model Context Protocol bridge that connects AI assistants — including Claude Desktop, Cursor, Windsurf, and VS Code Copilot — to the Azure DevOps API through natural language. It exposes 8 API endpoints as callable tools, such as Operations_List, PipelineTemplateDefinitions_List, Pipelines_ListBySubscription, and more. No authentication is required — setup takes approximately 30 seconds. The server uses STDIO transport and can be installed by running npx -y @mcp/azure-com-devops. This integration is sourced from the auto Azure DevOps OpenAPI specification (v2019-07-01-preview) and has a quality score of 34/99 (fair documentation coverage).

8Endpointstools mapped
NoneAuthopen access
34/99Qualityfair
~30 secSetupno auth

Server Details

Category
Cloud Infrastructure
Authentication
None
Endpoints
8 operations
Transport
STDIO
Spec Version
v2019-07-01-preview
Install Command
npx -y @mcp/azure-com-devops

Environment Variables

AZURE_DEVOPS_API_KEY

Example: your_azure_devops_api_key

Top Endpoints

GET
/providers/Microsoft.DevOps/operations

Operations_List

GET
/providers/Microsoft.DevOps/pipelineTemplateDefinitions

PipelineTemplateDefinitions_List

GET
/subscriptions/{subscriptionId}/providers/Microsoft.DevOps/pipelines

Pipelines_ListBySubscription

GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines

Pipelines_ListByResourceGroup

GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DevOps/pipelines/{pipelineName}

Pipelines_Get

Own this API?

Verify ownership of this listing to control the description, configuration details, and documentation links. Choose between free manual verification or instant premium placement.

Option 1: Free Verification

Slow manual review. Requires creating a GitHub issue with verified documentation or domain verification.

  • • Verified badge on page
  • • Standard search sorting
  • • 2-3 business days review
Start Free Claim →
Instant & Boosted

Option 2: Featured Upgrade($9/mo)

Instant verification plus premium styling, featured badges, and directory placement boost.

  • • ★ Featured star & amber highlight border
  • • Top of directory search placement
  • • Instant activation via claim token

📖 Detailed MCP Integration Guide

A technical breakdown of capabilities, agent workflows, and security/configuration best practices.

Capabilities & Use Cases
The Azure DevOps Resource Provider API, developed by Microsoft, serves as a foundational interface for programmatically interacting with and managing the core components of the Azure DevOps platform. Its primary function is to provide a consistent, RESTful endpoint for the lifecycle management of Azure Pipelines—the CI/CD engine of Azure DevOps—as well as access to operational metadata and reusable pipeline templates. This API is indispensable for organizations seeking to automate their infrastructure-as-code deployments, manage pipeline configurations at scale, and enforce standardized deployment patterns across multiple projects and teams. Core capabilities include creating, reading, updating, and deleting pipeline definitions within specific resource groups, as well as listing all pipelines across a subscription or within a particular project. Typical enterprise use cases range from dynamically provisioning pipelines for microservices deployments during cloud resource creation to decommissioning CI/CD workflows as part of environment teardown processes, thereby enabling a fully automated, software-defined infrastructure lifecycle.
🤖AI Agent Value
When exposed as tools to an AI coding assistant via the Model Context Protocol (MCP), this API unlocks a powerful layer of contextual automation for developers. The AI model transforms from a code-completion tool into an active infrastructure operator, capable of bridging the gap between natural language intent and cloud resource management. For example, a developer can instruct the AI to "scaffold a new build-and-test pipeline for the Java service in the dev environment," and the assistant, equipped with the PUT /pipelines/{pipelineName} tool, can generate and apply the full pipeline YAML configuration directly to Azure DevOps. This eliminates manual navigation of portals and accelerates developer onboarding to new projects. The value lies in the direct, actionable integration: the AI can query existing pipeline states (GET endpoints), compare them against a desired configuration, and apply updates (PATCH or PUT) to enforce standards or fix issues, all within the flow of a coding session.
💬Example Workflows
Practical workflows enabled by this MCP integration are diverse and transformative. A developer can ask the AI agent to "Audit all pipelines in the production resource group that use the deprecated Windows-2019 agent pool," using the subscription-scoped GET endpoint to gather data and then report findings or suggest migration scripts. In another scenario, the instruction "Clone the configuration of pipeline main-build and create a new one named feature-branch-build" becomes a single-step task where the AI reads the source pipeline, modifies its name parameter, and issues a PUT request to create the clone. The AI can also facilitate bulk operations, such as "Update the service connection in every pipeline named *deploy* to point to the new prod-v2 endpoint," automating what would otherwise be a tedious, error-prone manual process across dozens of files.
🛡️Security & Auth
Crucially, while the API definition may list authentication as "None," any practical deployment requires robust security. Integration with an MCP server must use Azure Active Directory (Azure AD) OAuth 2.0 authentication or Personal Access Tokens (PATs) with narrowly scoped permissions, adhering strictly to the principle of least privilege. For pipeline management, this typically requires the "Pipelines Read & Execute" or "Full Control" permissions within the specific Azure DevOps project, not at the global organization level. Developers should configure the MCP server to use a service principal or a PAT that is limited to a single project or resource group. Best practices include storing secrets in secure vaults like Azure Key Vault, never hardcoding credentials, and implementing audit logging to track all AI-initiated API calls. The AI assistant itself should be configured to treat infrastructure-modifying actions with explicit user confirmation steps to prevent unintended changes.

Similar APIs

Other APIs in the Cloud Infrastructure category.

Related MCP Server Integrations

Supabase API MCP Setup

Manage Supabase projects, databases, authentication, and storage through your AI agent.

Cloud InfrastructureConfigure →

Cloudflare API MCP Setup

Manage Cloudflare DNS, CDN, Workers, and security settings through your AI agent.

Cloud InfrastructureConfigure →

Vercel API MCP Setup

Deploy projects, manage domains, and monitor deployments through your AI agent.

Cloud InfrastructureConfigure →

DigitalOcean API MCP Setup

The DigitalOcean API is a comprehensive, RESTful interface provided by DigitalOcean, a leading cloud infrastructure provider focused on simplifying cloud computing for developers, startups, and enterprises. It serves as the programmatic backbone for managing the entire DigitalOcean ecosystem, enabling users to provision, configure, and control cloud resources such as Droplets (virtual private servers), Kubernetes clusters, managed databases, networks, storage volumes, and application platforms. Core capabilities include full lifecycle management of these resources, from creation and scaling to monitoring and deletion, mirroring the functionality available in the DigitalOcean control panel. Its primary use cases range from automating infrastructure setup for CI/CD pipelines and enabling infrastructure-as-code practices to supporting dynamic application scaling and resource optimization for SaaS products, e-commerce sites, and development environments. The API is designed for both developers seeking to automate their cloud operations and businesses that require programmable, scalable cloud infrastructure without the complexity of larger hyperscale providers.

Cloud InfrastructureConfigure →

Access Analyzer MCP Setup

The AWS Identity and Access Management Access Analyzer API provides a powerful, policy-as-code service that automatically identifies resources accessible from outside your AWS account or organization. At its core, the service continuously evaluates resource-based policies—such as Amazon S3 bucket policies, AWS Identity and Access Management (IAM) roles, Amazon KMS key policies, and AWS Lambda function policies—using logic-based reasoning to determine which resources grant access to unknown external principals. Its primary use case is for security and compliance teams within enterprises to proactively detect unintended data exposure, enforce least privilege principles, and audit cross-account and cross-service access. The API endpoints allow programmatic control to create, configure, and query analyzers, manage archive rules for storing findings, and generate custom policy documents, making it a foundational tool for automating cloud security posture management at scale.

Cloud InfrastructureConfigure →