@slorenzot/mcp-azure
The @slorenzot/mcp-azure server enables comprehensive interaction with Azure DevOps through the Model Context Protocol (MCP), allowing you to manage Work Items, Git repositories, Pull Requests, sprints, areas, comments, and attachments from any compatible MCP client.
Authentication & Configuration
Configure connections using
ado_configurewith your organization URL, project name, and Personal Access Token (PAT); also supports environment variables and static config files.
Work Item Management
Retrieve, create, and update Work Items (User Stories, Bugs, Tasks, etc.) with fields like title, description, area/iteration path, assignee, and custom fields
Inspect available and required fields for specific Work Item types
Querying Work Items
Query by sprint/iteration path, area path, or execute custom WIQL queries with optional full detail retrieval
Project Structure
List all available iterations/sprints and areas within the project
Git Repository Operations
List repositories, get details for a specific repository, and enumerate branches
Pull Request Lifecycle
List, retrieve, create, update, complete (merge), and abandon Pull Requests
Manage reviewers: add, approve, reject, and view votes
Handle PR threads: create general or code-specific comment threads, reply to existing ones, and update thread status
Retrieve commits and linked Work Items associated with a PR
Comments & Discussions
Add Markdown-supported comments to Work Items and retrieve discussion history
Attachments
Upload files to Azure DevOps, attach new or existing files to Work Items with optional comments, and list all attachments on a Work Item
Predefined Prompts
Includes built-in prompts for common workflows such as sprint analysis, user story creation, daily standups, sprint planning, bulk updates, project reports, and bug reporting.
Provides tools for interacting with Azure DevOps Git repositories, including listing repositories, branches, and managing pull requests with full lifecycle support.
Supports Markdown formatting in comments and descriptions for work items and pull requests, enabling rich text documentation and discussions.
Enables server-side integration with Azure DevOps through Node.js, providing programmatic access to work items, repositories, and project management features.
Facilitates installation and distribution of the Azure DevOps MCP server as an npm package, enabling easy deployment and configuration.
Provides TypeScript-based tooling for Azure DevOps integration, offering type-safe interactions with work items, repositories, and project structures.
Supports installation and dependency management for the Azure DevOps MCP server as an alternative to npm package management.
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., "@@slorenzot/mcp-azure List all active bugs in the current sprint"
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.
@slorenzot/mcp-azure
MCP (Model Context Protocol) server for Azure DevOps. It allows you to interact with Work Items, Git repositories, Pull Requests, sprints, areas, comments, and attachments from any compatible MCP client.
Installation
npm install -g @slorenzot/mcp-azureOr use directly with npx:
npx @slorenzot/mcp-azureRelated MCP server: devops-wrangler
Configuration
Environment Variables
The server is automatically configured using the following environment variables:
Variable | Alternative | Description | Required |
|
| Organization URL (e.g., | Yes |
|
| Personal Access Token | Yes |
|
| Project name | No |
Configuration in Claude Desktop
Add the following configuration to your claude_desktop_config.json file:
{
"mcpServers": {
"azure-devops": {
"command": "npx",
"args": ["-y", "@slorenzot/mcp-azure"],
"env": {
"AZURE_DEVOPS_ORG": "https://dev.azure.com/tu-organizacion",
"AZURE_DEVOPS_PAT": "tu-pat-aqui",
"AZURE_DEVOPS_PROJECT": "tu-proyecto"
}
}
}
}Configuration in OpenCode
OpenCode uses the same MCP, but configuration can be done in two ways:
Option 1: Initial configuration with environment variables
Set the environment variables in your system or in your OpenCode configuration:
export AZURE_DEVOPS_ORG="https://dev.azure.com/tu-organizacion" export AZURE_DEVOPS_PAT="tu-pat-aqui" export AZURE_DEVOPS_PROJECT="tu-proyecto"Or add the MCP server in your OpenCode configuration:
{ "mcpServers": { "azure-devops": { "command": "npx", "args": ["-y", "@slorenzot/mcp-azure"], "env": { "AZURE_DEVOPS_ORG": "https://dev.azure.com/tu-organizacion", "AZURE_DEVOPS_PAT": "tu-pat-aqui", "AZURE_DEVOPS_PROJECT": "tu-proyecto" } } } }
Option 2: Dynamic configuration with ado_configure
OpenCode allows you to configure the connection directly during the session using the ado_configure command:
{
"organization": "https://dev.azure.com/tu-organizacion",
"project": "tu-proyecto",
"pat": "tu-pat-aqui"
}This option is useful for switching between different organizations or projects without modifying the configuration file.
Note: When you use ado_configure, the connection persists during the current OpenCode session.
Obtaining a Personal Access Token (PAT)
Go to your Azure DevOps organization
Click on your avatar (top right corner)
Select Personal Access Tokens
Create a new token with the following permissions:
Work Items: Read & Write
Code: Read & Write (for repository and Pull Request operations)
Project and Team: Read (optional)
Available Tools
Authentication
Tool | Description |
| Configures the connection with organization, project, and PAT |
Work Items
Tool | Description |
| Gets a Work Item by its ID |
| Creates a new Work Item (User Story, Bug, Task, etc.) |
| Updates an existing Work Item |
| Gets the available/required fields for a type |
Queries
Tool | Description |
| Queries Work Items for a specific sprint |
| Queries Work Items for a specific area |
| Executes a custom WIQL query |
Project Structure
Tool | Description |
| Lists the project's iterations/sprints |
| Lists the project's areas |
Git Repositories
Tool | Description |
| Lists all Git repositories in the project |
| Gets details of a specific repository by name or ID |
| Lists the branches of a repository |
Pull Requests
Tool | Description |
| Lists Pull Requests with optional filters (status, branches, creator, reviewer) |
| Gets full details of a Pull Request |
| Creates a new Pull Request |
| Updates Pull Request properties (title, description, draft) |
| Completes (merges) a Pull Request with a configurable strategy |
| Abandons a Pull Request |
Pull Request Reviews
Tool | Description |
| Approves a Pull Request (vote: 10) |
| Rejects a Pull Request (vote: -10) |
| Gets all reviewers and their votes for a Pull Request |
| Adds a reviewer to a Pull Request |
Pull Request Comments
Tool | Description |
| Gets all comment threads for a Pull Request |
| Creates a new comment thread (general or code-specific) |
| Replies to an existing comment thread |
Pull Request Info
Tool | Description |
| Gets all commits for a Pull Request |
| Gets Work Items linked to a Pull Request |
| Updates the status of a comment thread (Fixed, WontFix, etc.) |
Comments and Discussions
Tool | Description |
| Adds a comment to a Work Item (supports Markdown) |
| Gets comments for a Work Item |
Attachments
Tool | Description |
| Uploads a file and returns the attachment URL |
| Adds an attachment to a Work Item |
| Lists attachments for a Work Item |
Usage Examples
Create a User Story
{
"title": "Implementar login con OAuth",
"type": "User Story",
"description": "Como usuario quiero poder iniciar sesión con mi cuenta de Google",
"areaPath": "MiProyecto\\Backend",
"iterationPath": "MiProyecto\\Sprint 5",
"fields": {
"Custom.OKR": "Seguridad",
"Custom.Prioridad": "Alta"
}
}Custom WIQL Query
{
"wiql": "SELECT [System.Id], [System.Title] FROM WorkItems WHERE [System.State] = 'Active' AND [System.AssignedTo] = @Me ORDER BY [System.CreatedDate] DESC",
"getDetails": true
}Add Comment with Markdown
{
"id": 12345,
"comment": "## Análisis completado\n\n- Revisado el código\n- Identificados 3 issues\n\n**Próximo paso:** Corregir validaciones"
}Upload and Attach File
{
"workItemId": 12345,
"filePath": "/ruta/al/archivo.pdf",
"comment": "Documento de especificaciones",
"name": "Especificaciones Funcionales v2.0"
}Link Existing Attachment
{
"workItemId": 12345,
"attachmentUrl": "https://dev.azure.com/org/proj/_apis/wit/attachments/abc123",
"comment": "Diseño de arquitectura",
"name": "Arquitectura del Sistema"
}List Repositories
{
"includeHidden": false,
"top": 50
}List Active Pull Requests
{
"status": "Active",
"top": 20
}Create a Pull Request
{
"repositoryId": "mi-repo",
"sourceRefName": "refs/heads/feature-login",
"targetRefName": "refs/heads/main",
"title": "Implementar login con OAuth",
"description": "Esta PR agrega soporte para login con Google OAuth",
"reviewerIds": ["12345678-1234-1234-1234-1234567890ab"],
"isDraft": false
}Approve a Pull Request
{
"pullRequestId": 12345,
"repositoryId": "mi-repo"
}Complete (Merge) a Pull Request
{
"pullRequestId": 12345,
"repositoryId": "mi-repo",
"mergeStrategy": "Squash",
"deleteSourceBranch": true,
"mergeCommitMessage": "Merge de feature-login"
}Create Code Comment
{
"pullRequestId": 12345,
"repositoryId": "mi-repo",
"content": "Por favor extraer esto en una función separada",
"filePath": "/src/components/Login.tsx",
"startLine": 45,
"endLine": 52
}Available Prompts
The server includes pre-defined prompts to facilitate common tasks:
Prompt | Description |
| Guide to connect to Azure DevOps |
| Analyzes the status of a sprint |
| Creates a structured User Story |
| Generates a daily standup report |
| Helps plan a sprint |
| Updates multiple Work Items |
| Generates a project report |
| Creates a structured Bug report |
Resources
Resource | URI | Description |
Connection status |
| Information about the current connection status |
Development
Requirements
Node.js 18+
npm or yarn
Local Installation
git clone https://github.com/slorenzot/mcp-azure.git
cd mcp-azure
npm install
npm run buildAvailable Scripts
npm run build # Compila TypeScript
npm run start # Inicia el servidor
npm run dev # Modo desarrollo con watchLicense
MIT
Author
Soulberto Lorenzo - @slorenzot
Version
2.4.1 - 34 tools available for Azure DevOps (Work Items, Git Repositories, Pull Requests, etc.)
Available Tools
36 toolsado_abandon_pull_requestC
Abandona un Pull Request (cambia estado a Abandoned).
Inputs: pullRequestId (required), repositoryId.
ado_add_attachmentB
Agrega un adjunto a un Work Item existente. Maneja automáticamente concurrencia cuando múltiples adjuntos se agregan al mismo WI.
Inputs: workItemId (required), name, comment, filePath, +1 more.
ado_add_commentB
Agrega un comentario/entrada de discusión a un Work Item. Soporta formato Markdown.
Inputs: id (required), comment (required).
ado_add_pull_request_reviewerB
Agrega un revisor a un Pull Request.
Inputs: reviewerId (required), pullRequestId (required), vote, repositoryId.
ado_approve_pull_requestB
Aprueba un Pull Request (voto: 10).
Inputs: pullRequestId (required), reviewerId, repositoryId.
ado_complete_pull_requestC
Completa (merge) un Pull Request.
Inputs: pullRequestId (required), repositoryId, mergeStrategy, deleteSourceBranch, +2 more.
ado_configureB
Configura la conexión a Azure DevOps con token de acceso personal (PAT).
Inputs: pat (required), project (required), organization (required).
ado_create_pull_requestC
Crea un nuevo Pull Request.
Inputs: title (required), repositoryId (required), sourceRefName (required), targetRefName (required), +3 more.
ado_create_pull_request_threadB
Crea un nuevo hilo de comentarios (comentario general o comentario de código).
Inputs: content (required), pullRequestId (required), endLine, filePath, +2 more.
ado_create_work_itemA
Crea un nuevo Work Item en Azure DevOps. Usa ado_get_work_item_type_fields para ver campos requeridos.
Inputs: type (required), title (required), fields, areaPath, +3 more.
ado_delete_attachmentB
Elimina un adjunto de un Work Item removiendo su relación. Maneja automáticamente concurrencia cuando múltiples cambios afectan el mismo WI.
Inputs: workItemId (required), comment, attachmentUrl, attachmentName.
ado_delete_work_itemA
Elimina un Work Item en Azure DevOps. Por defecto realiza borrado lógico; usa destroy=true solo para eliminación permanente.
Inputs: id (required), confirm (required), destroy, expectedType.
ado_get_attachmentsB
Obtiene la lista de adjuntos de un Work Item
Inputs: id (required).
ado_get_commentsB
Obtiene los comentarios/historial de discusión de un Work Item
Inputs: id (required), top.
ado_get_pull_requestC
Obtiene detalles completos de un Pull Request.
Inputs: pullRequestId (required), repositoryId, includeCommits, includeWorkItems.
ado_get_pull_request_commitsC
Obtiene todos los commits de un Pull Request.
Inputs: pullRequestId (required), top, repositoryId.
ado_get_pull_request_reviewersA
Obtiene todos los revisores y sus votos de un Pull Request.
Inputs: pullRequestId (required), repositoryId.
ado_get_pull_request_threadsB
Obtiene todos los hilos de comentarios de un Pull Request.
Inputs: pullRequestId (required), repositoryId.
ado_get_pull_request_work_itemsB
Obtiene los work items vinculados a un Pull Request.
Inputs: pullRequestId (required), repositoryId.
ado_get_repositoryB
Obtiene detalles de un repositorio específico por nombre o ID.
Inputs: repositoryId (required).
ado_get_work_itemB
Obtiene un Work Item de Azure DevOps por su ID
Inputs: id (required), full.
ado_get_work_item_type_fieldsB
Obtiene los campos disponibles y requeridos para un tipo de Work Item
Inputs: workItemType (required).
ado_list_areasA
Lista las áreas disponibles en el proyecto
Inputs: no named parameters.
ado_list_branchesB
Lista las ramas (branches) de un repositorio.
Inputs: repositoryId (required), filter, includeStatuses.
ado_list_iterationsA
Lista las iteraciones/sprints disponibles en el proyecto
Inputs: no named parameters.
ado_list_pull_requestsA
Lista Pull Requests con filtros opcionales. Busca por repositorio o en todo el proyecto.
Inputs: top, status, creatorId, reviewerId, +3 more.
ado_list_repositoriesA
Lista todos los repositorios Git del proyecto.
Inputs: top, includeHidden.
ado_query_areaC
Consulta User Stories de un área específica en Azure DevOps
Inputs: areaPath (required), workItemType.
ado_query_sprintA
Consulta User Stories de un sprint específico en Azure DevOps
Inputs: iterationPath (required), state.
ado_query_wiqlC
Ejecuta una consulta WIQL personalizada en Azure DevOps
Inputs: wiql (required), getDetails.
ado_reject_pull_requestC
Rechaza un Pull Request (voto: -10).
Inputs: pullRequestId (required), reviewerId, repositoryId.
ado_reply_to_pull_request_threadC
Responde a un hilo de comentarios existente.
Inputs: content (required), threadId (required), pullRequestId (required), repositoryId.
ado_update_pull_requestC
Actualiza propiedades de un Pull Request (título, descripción, estado de borrador).
Inputs: pullRequestId (required), title, isDraft, description, +1 more.
ado_update_pull_request_thread_statusC
Actualiza el estado de un hilo de comentarios (ej: marcar como Fixed, WontFix, etc.).
Inputs: status (required), threadId (required), pullRequestId (required), repositoryId.
ado_update_work_itemC
Actualiza un Work Item existente en Azure DevOps
Inputs: id (required), state, title, fields, +2 more.
ado_upload_attachmentC
Sube un archivo como adjunto a Azure DevOps y devuelve la URL del adjunto
Inputs: filePath (required), fileName.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 36 tools
Each tool targets a distinct action and resource (e.g., create vs update vs delete work items, add vs upload attachments). No two tools have ambiguous purposes, ensuring clear agent selection.
All tools follow the consistent pattern 'ado_verb_noun' (e.g., ado_create_work_item, ado_list_repositories). The prefix and verb-noun structure are uniform, making it easy to predict tool names.
36 tools is slightly above the typical range, but the Azure DevOps domain is broad. Each tool covers a necessary operation (work items, PRs, repositories, queries, etc.), so the count feels justified rather than bloated.
The tool surface covers the main workflows: CRUD for work items and pull requests, attachments, comments, threads, repositories, and queries. Minor gaps exist (e.g., no create/delete branch or build pipeline tools), but core operations are present.
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.
One MCP server for the services your AI needs: memory, files, Microsoft 365, kanban and more.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI assistants to manage Azure DevOps resources including Work Items, Git repositories, pipelines, and user identities.20 npmMIT
- AlicenseAqualityDmaintenanceAn MCP server for Azure DevOps work item management that enables AI assistants to create, query, update, and manage work items, sprints, and more.129 npmISC
- AlicenseNot gradedqualityDmaintenanceMCP server for Azure DevOps Server 2022 (on-premises) that enables AI assistants to interact with work items, repositories, builds, and sprints through 29 tools.33 npmMIT
- AlicenseNot gradedqualityDmaintenanceA focused MCP server for Azure DevOps work item administration, enabling AI agents to create, update, query, and manage work items with full CRUD operations and advanced WIQL querying.MIT