Azure DevOps MCP Server

MCP N8N Azure Devops

Local serverstdio

What is the Azure DevOps MCP server?

Most developer tooling work still happens through a UI a human drives. Azure DevOps MCP server moves it into the conversation instead. MCP N8N Azure Devops.

The short version

A Model Context Protocol (MCP) server implementation for Azure DevOps, allowing AI assistants to interact with Azure DevOps APIs through a standardized protocol.

This server implements the Model Context Protocol (MCP) for Azure DevOps, enabling AI assistants like Claude to interact with Azure DevOps resources securely. The server acts as a bridge between AI models and Azure DevOps APIs, providing a standardized way to:

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

The tools it exposes

The server publishes 14 tools. What each one is for:

  • get_me — Get details of the authenticated user (id, displayName, email)
  • list_organizations — List all accessible organizations
  • list_projects — List all projects in an organization
  • get_project — Get details of a specific project
  • get_project_details — Get comprehensive details of a project including process, work item types, and teams
  • list_repositories — List all repositories in a project
  • get_repository — Get details of a specific repository
  • get_repository_details — Get detailed information about a repository including statistics and refs
  • get_file_content — Get content of a file or directory from a repository
  • get_work_item — Retrieve a work item by ID
  • create_work_item — Create a new work item
  • update_work_item — Update an existing work item

What it needs from you

Configuration is passed through the environment: AZURE_DEVOPS_ORG_URL, AZURE_DEVOPS_AUTH_METHOD, AZURE_DEVOPS_DEFAULT_PROJECT, AZURE_DEVOPS_PAT, AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js (v16+) - npm or yarn - Azure DevOps account with appropriate access - Authentication credentials (see Authentication Guide for details): - Personal Access Token (PAT), or - Azure Identity credentials, or - Azure CLI login

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Azure DevOps.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Azure DevOps's toolset — get_me, list_organizations, list_projects and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ramosjuan24; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
get_meGet details of the authenticated user (id, displayName, email)
list_organizationsList all accessible organizations
list_projectsList all projects in an organization
get_projectGet details of a specific project
get_project_detailsGet comprehensive details of a project including process, work item types, and teams
list_repositoriesList all repositories in a project
get_repositoryGet details of a specific repository
get_repository_detailsGet detailed information about a repository including statistics and refs
get_file_contentGet content of a file or directory from a repository
get_work_itemRetrieve a work item by ID
create_work_itemCreate a new work item
update_work_itemUpdate an existing work item
list_work_itemsList work items in a project
manage_work_item_linkAdd, remove, or update links between work items

How to install the Azure DevOps MCP server

{
  "mcpServers": {
    "azureDevOps": {
      "command": "npx",
      "args": ["-y", "@ramosjuan24/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"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js (v16+) - npm or yarn - Azure DevOps account with appropriate access - Authentication credentials (see Authentication Guide for details): - Personal Access Token (PAT), or - Azure Identity credentials, or - Azure CLI login
VariableDescriptionRequired
AZURE_DEVOPS_ORG_URLEndpoint or connection string the server talks to.Yes
AZURE_DEVOPS_AUTH_METHODConfiguration value read at startup.Optional
AZURE_DEVOPS_DEFAULT_PROJECTConfiguration value read at startup.Optional
AZURE_DEVOPS_PATConfiguration value read at startup.Optional
AZURE_TENANT_IDConfiguration value read at startup.Optional
AZURE_CLIENT_IDConfiguration value read at startup.Optional
AZURE_CLIENT_SECRETCredential the server authenticates with.Yes

Example prompts to try

  • Use Azure DevOps to get me.
  • Use Azure DevOps to list organizations.
  • Use Azure DevOps to list projects.

Frequently asked questions

It supports Personal Access Token (PAT), Azure Identity (DefaultAzureCredential), and Azure CLI authentication.