Azure DevOps MCP Server
@AzureDevOpsAPI
About Azure DevOps MCP Server
An MCP server for Azure DevOps
Basic information
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"azureDevOps": {
"command": "npx",
"args": [
"-y",
"@tiberriver256/mcp-server-azure-devops"
],
"env": {
"AZURE_DEVOPS_ORG_URL": "https://dev.azure.com/your-organization",
"AZURE_DEVOPS_AUTH_METHOD": "azure-identity",
"AZURE_DEVOPS_DEFAULT_PROJECT": "your-project-name"
}
}
}
}Tools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is Azure DevOps MCP Server?
A Model Context Protocol (MCP) server implementation for Azure DevOps, allowing AI assistants to interact with Azure DevOps APIs through a standardized protocol. It acts as a bridge between AI models and Azure DevOps resources, enabling secure access to projects, work items, repositories, pull requests, pipelines, wikis, and more.
How to use Azure DevOps MCP Server?
Install Node.js v16+, then run the server via npx with configuration. Provide environment variables for organization URL and authentication method (PAT, Azure Identity, or Azure CLI). Add the configuration to your Claude Desktop or Cursor AI MCP settings file. The server is invoked with npx -y @tiberriver256/mcp-server-azure-devops.
Key features of Azure DevOps MCP Server
- Access and manage projects, work items, repositories, and more.
- Create and update work items, branches, and pull requests.
- Execute common DevOps workflows through natural language.
- Access repository content via standardized resource URIs.
- Supports multiple authentication methods (PAT, Azure Identity, Azure CLI).
- Provides tools for search, pipelines, wikis, and user details.
Use cases of Azure DevOps MCP Server
- List and create work items, branches, and pull requests from a chat interface.
- Search code, wikis, and work items across Azure DevOps projects.
- Retrieve file content from repositories and trigger pipeline runs.
- Get project details and manage work item links programmatically.
FAQ from Azure DevOps MCP Server
What is the Azure DevOps MCP Server and how does it differ from direct Azure DevOps API usage?
It standardizes interaction with Azure DevOps via the Model Context Protocol, allowing AI assistants to perform DevOps operations through natural language without needing to manage API calls directly.
What authentication methods are supported?
Personal Access Token (PAT), Azure Identity (DefaultAzureCredential), and Azure CLI login. Configuration is set via the AZURE_DEVOPS_AUTH_METHOD environment variable.
What prerequisites are required to run the server?
Node.js v16+, npm or yarn, an Azure DevOps account with appropriate access, and valid authentication credentials (PAT, Azure Identity, or Azure CLI login).
What environment variables are required?
AZURE_DEVOPS_ORG_URL is mandatory. AZURE_DEVOPS_AUTH_METHOD defaults to azure-identity. AZURE_DEVOPS_PAT is needed only for PAT authentication. AZURE_DEVOPS_DEFAULT_PROJECT is optional.
Where does the server run and how is data handled?
The server runs locally or in your environment and acts as a bridge; data remains in Azure DevOps. The server does not store data externally.
More Cloud & Infrastructure MCP servers
AWS Model Context Protocol (MCP) Server
alexei-ledA lightweight service that enables AI assistants to execute AWS CLI commands (in safe containerized environment) through the Model Context Protocol (MCP). Bridges Claude, Cursor, and other MCP-aware AI tools with AWS CLI for enhanced cloud infrastructure management.
🐳 docker-mcp
QuantGeekDevA docker MCP Server (modelcontextprotocol)
container-use
aluzzardiDevelopment environments for coding agents. Enable multiple agents to work safely and independently with your preferred stack.

Aws Kb Retrieval Server
modelcontextprotocolModel Context Protocol Servers
Terraform MCP Server
hashicorpThe Terraform MCP Server provides seamless integration with Terraform ecosystem, enabling advanced automation and interaction capabilities for Infrastructure as Code (IaC) development.
Comments