How do I use azure-devops-mcp-server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@azure-devops-mcp-server show me my active bugs" 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.

azure-devops-mcp-server

by branjesusdev

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

azure-devops-mcp-server

Servidor MCP (Model Context Protocol) para Azure DevOps, implementado sobre stdio nativo — sin SDK de MCP ni dependencias externas más allá de dotenv. Expone Azure Boards, Azure Repos y Azure Pipelines como tools invocables por Claude.

Instalación y arranque

pnpm install        # instalar dependencias
pnpm start          # iniciar servidor MCP
pnpm dev            # iniciar con recarga automática (node --watch)

Variables de entorno requeridas (.env, ver .env.example):

Variable	Descripción
`AZURE_DEVOPS_PAT`	Personal Access Token de Azure DevOps
`AZURE_DEVOPS_ORG`	Nombre de la organización (ej. `movii`)
`AZURE_ASSIGNED_TO`	(Opcional) usuario para `query_my_bugs` (default en `src/config.js`)

Related MCP server: Azure DevOps MCP Server

Herramientas (tools) disponibles

Boards — `src/boards/index.js`

Tool	Qué hace	Ejemplo básico
`query_my_bugs`	Lista los bugs activos asignados al usuario configurado en `ASSIGNED_TO`.	`query_my_bugs()`
`get_work_item`	Obtiene un work item por ID (título, estado, descripción, repro steps, discussion, etc.).	`get_work_item(id: 12767)`
`query_work_items`	Ejecuta una consulta WIQL y devuelve `id/title/state/type` de cada resultado.	`query_work_items(wiql: "SELECT [System.Id] FROM WorkItems WHERE [System.WorkItemType]='Bug' AND [System.State]<>'Closed'")`
`update_work_item_state`	Cambia el estado de un work item.	`update_work_item_state(id: 12767, state: "Active")`
`create_work_item`	Crea un work item (`User Story`, `Task`, `Bug`, ...) con título, descripción HTML, criterios de aceptación, area/iteration path, tags y — para `Task` — `activity`, `originalEstimate`, `startDate`/`finishDate` y `parentId` (enlaza como hija vía `Hierarchy-Reverse`).	`create_work_item(project: "movii-business-line", type: "Task", title: "Implementar endpoint de saldo", activity: "Development", originalEstimate: 8, startDate: "2026-07-10", finishDate: "2026-07-11", parentId: 4821)`

Repos — `src/repos/index.js`

Tool	Qué hace	Ejemplo básico
`get_repositories`	Lista los repositorios de un proyecto (id, nombre, rama por defecto).	`get_repositories(project: "internal")`
`search_code`	Busca texto en el código vía Azure DevOps Code Search (wildcards, AND/OR/NOT).	`search_code(searchText: "ValidatePSE", repositoryName: "moviired-portal", branch: "development", project: "internal")`
`get_file_content`	Lee el contenido de un archivo de un repo en una rama dada.	`get_file_content(repositoryId: "moviired-portal", path: "/app/Http/Controllers/PSEController.php", branch: "development", project: "internal")`
`create_branch`	Crea una rama nueva desde otra existente.	`create_branch(repositoryId: "moviired-portal", branchName: "bug/12767", sourceBranch: "development")`
`push_commit`	Hace commit de un archivo modificado en una rama existente.	`push_commit(repositoryId: "moviired-portal", branchName: "bug/12767", filePath: "/app/...php", content: "<...>", message: "fix: #12767")`
`create_pull_request`	Abre un PR entre dos ramas.	`create_pull_request(repositoryId: "moviired-portal", sourceBranch: "bug/12767", targetBranch: "development", title: "fix: #12767 - ...")`
`get_pull_request`	Consulta estado (`active`/`completed`/`abandoned`), merge status y fechas de un PR.	`get_pull_request(repositoryId: "moviired-portal", pullRequestId: 8095)`

Pipelines — `src/pipelines/index.js`

Tool	Qué hace	Ejemplo básico
`get_pipelines`	Lista los pipelines del proyecto.	`get_pipelines(project: "internal")`
`get_pipeline_runs`	Últimas ejecuciones de un pipeline (estado, resultado, fechas).	`get_pipeline_runs(pipelineId: 42, top: 5, project: "internal")`

Cierre — `src/services/index.js`

Tool	Qué hace	Ejemplo básico
`notify_task_completed`	Hook de cierre: persiste un reporte en `reports/output.json` y finaliza la tarea.	`notify_task_completed(taskId: "12767", summary: "Bug resuelto, PR #8095 mergeado", status: "success")`

Todos los tools de proyecto (Repos/Pipelines/create_work_item) aceptan project — si se omite, usar el nombre exacto del proyecto Azure DevOps (no hay default global, cada llamada project-scoped lo exige). Los tools de Boards de solo-lectura/escritura de work items (get_work_item, query_work_items, update_work_item_state) son org-scoped: el ID de work item es único a nivel organización, no requieren project.

Qué agente usar para cada tarea

Tarea	Agente	Qué hace
Resolver/investigar un bug por ID	`bug-resolver`	Lee el work item, investiga el código (`search_code` → `get_file_content`), produce un plan de fix estructurado. No toca git.
Ejecutar el fix y abrir el PR	`repo-writer`	Recibe el plan de `bug-resolver` y ejecuta rama + commit + PR + notificación de cierre. No analiza bugs.
Verificar pipeline y cerrar el bug tras mergear el PR	`pipeline-monitor`	Verifica el resultado del pipeline post-merge; si pasó, cierra el work item y comenta la traza completa (duraciones, tokens).
Crear una historia de usuario o tarea nueva, con detalle profesional	`story-writer`	Investiga el código fuente relevante (repo Azure DevOps y/o ruta local), redacta introducción/objetivo/alcance/criterios de aceptación, y crea el work item directamente con `create_work_item`.
Desglosar una User Story existente en Tasks	`task-writer`	Lee la historia, investiga el repositorio asociado, propone/completa Tasks con `activity`, `originalEstimate` y fechas, y las crea enlazadas como hijas de la historia.

Ver CLAUDE.md para el flujo paso a paso de cada uno (bugs: diagnóstico → fix/PR → verificación de pipeline; historias: confirmación de contexto → story-writer; desglose de tareas: confirmación de contexto → task-writer).

Available Tools

15 tools

create_branchC

Crea una rama nueva desde otra existente

Inputs: branchName (required), repositoryId (required), sourceBranch (required), project.

create_pull_requestB

Crea un Pull Request entre dos ramas

Inputs: title (required), repositoryId (required), sourceBranch (required), targetBranch (required), +2 more.

create_work_itemC

Crea un work item (User Story, Task, Bug, etc.) en Azure Boards

Inputs: title (required), project (required), tags, type, +11 more.

get_file_contentC

Lee el contenido de un archivo en un repositorio

Inputs: path (required), repositoryId (required), branch, project.

get_pipeline_runsB

Obtiene ejecuciones recientes de un pipeline

Inputs: pipelineId (required), top, project.

get_pipelinesB

Lista todos los pipelines del proyecto

Inputs: project.

get_pull_requestB

Obtiene el estado actual de un Pull Request

Inputs: repositoryId (required), pullRequestId (required), project.

get_repositoriesB

Lista todos los repositorios del proyecto

Inputs: project.

get_work_itemA

Obtiene un work item de Azure Boards por ID

Inputs: id (required).

notify_task_completedC

Hook de cierre: persiste reporte y finaliza la tarea

Inputs: status (required), taskId (required), summary (required).

push_commitC

Hace commit de un cambio en un archivo dentro de una rama existente

Inputs: content (required), message (required), filePath (required), branchName (required), +2 more.

query_my_bugsA

Lista los bugs activos asignados al usuario configurado en ASSIGNED_TO

Inputs: no named parameters.

query_work_itemsB

Consulta work items usando WIQL

Inputs: wiql (required).

search_codeB

Busca texto en los archivos de un repositorio usando Azure DevOps Code Search

Inputs: searchText (required), top, branch, project, +1 more.

update_work_item_stateA

Actualiza el estado de un work item en Azure Boards

Inputs: id (required), state (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.3/5.0

Scored 2026-07-14 19:25 across 15 tools

Disambiguation4/5

Most tools target distinct resources/actions. However, query_my_bugs overlaps with query_work_items as a specific case, potentially causing agent confusion.

Naming Consistency4/5

Uses verb_noun pattern consistently except for notify_task_completed (verb_noun_past) and mixing get/query verbs for similar operations.

Tool Count5/5

15 tools cover the major Azure DevOps domains without being excessive. Each tool serves a clear purpose within git, work items, pipelines, and searching.

Completeness3/5

Missing update/delete for pull requests and branches, and no delete for work items. The surface covers core workflows but has notable gaps that may force workarounds.

Resources

Related MCP Connectors

backlog-forge
com.arcanum-plus
Crie épicos, features, histórias e tasks no Azure DevOps a partir de uma conversa.
Project Management Developer Tools
2
https://backlog-forge.arcanum-plus.com/mcp
salesforce-devops
cloud.serpent
Plan Salesforce deploys, open pull requests and trigger pipelines from your AI client.
CI/CD & DevOps Version Control CRM
2
https://mcp.serpent.cloud/mcp
Azure DevOps (ADO)
io.github.PremierInc
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
CI/CD & DevOps Version Control Project Management
22,083
https://mcp.dev.azure.com
GitHub
io.github.github
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Version Control Developer Tools CI/CD & DevOps
1234,365
https://api.githubcopilot.com/mcp/

Related MCP Servers

Azure DevOps MCP Proxy
Cloud Platforms Developer Tools Version Control
ennuiii
A
license
Not graded
quality
D
maintenance
Enables interaction with Azure DevOps through Personal Access Token authentication. Supports work item management, wiki operations, project/repository listing, and build pipeline access through natural language.
Updated a year ago (2025-08-19 06:08 UTC)
888 npm
MIT
Azure DevOps MCP Server
Version Control Project Management Developer Tools
grizzlypeaksoftware
A
license
Not graded
quality
D
maintenance
Enables AI assistants to interact with Azure DevOps to manage work items, Git repositories, branches, commits, and projects through natural language commands.
Updated 10 months ago (2026-01-14 23:51 UTC)
888 npm
5
MIT
Azure DevOps MCP Server
Developer Tools Project Management Version Control
AgentsGang
A
license
Not graded
quality
D
maintenance
Enables interaction with Azure DevOps services including work items, builds, releases, test plans, repositories, and search via natural language commands from a code editor.
Updated a year ago (2025-08-01 19:16 UTC)
49 npm
MIT
Azure DevOps MCP Server
CI/CD & DevOps Version Control Project Management
PaulVineethP
A
license
Not graded
quality
C
maintenance
Enables AI assistants to interact with Azure DevOps APIs for managing projects, work items, repositories, pull requests, and pipelines through natural language.
Updated 4 months ago (2026-06-30 17:58 UTC)
51 npm
1
MIT

azure-devops-mcp-server

Instalación y arranque

Herramientas (tools) disponibles

Boards — src/boards/index.js

Repos — src/repos/index.js

Pipelines — src/pipelines/index.js

Cierre — src/services/index.js

Qué agente usar para cada tarea

Available Tools

Tool Schema Changelog

TDQS

Resources

Related MCP Connectors

Related MCP Servers

Azure DevOps MCP Proxy

Azure DevOps MCP Server

Azure DevOps MCP Server

Azure DevOps MCP Server

Boards — `src/boards/index.js`

Repos — `src/repos/index.js`

Pipelines — `src/pipelines/index.js`

Cierre — `src/services/index.js`