azure

MCP Server for the Azure DevOps API, enabling project management, repository operations, and more.

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio zubeidhendricks-azure-mcp-server node server.js \
  --env AZURE_DEVOPS_ORG="Azure DevOps organization name" \
  --env AZURE_DEVOPS_TOKEN="Personal Access Token with required scopes" \
  --env AZURE_DEVOPS_PROJECT="Azure DevOps project name (optional, if needed by server)" \
  --env AZURE_DEVOPS_API_VERSION="6.0"

How to use

This MCP server provides integration tooling for Azure DevOps within an MCP environment. It enables automations around Azure DevOps resources such as projects, work items, repositories, builds, and pipelines by exposing MCP-compatible endpoints and actions. Clients can trigger operations like creating work items, querying project data, or managing repository contents through the MCP protocol, enabling streamlined workflows that connect with other tools in the same MCP network. The server is designed to be invoked by MCP clients that understand the standard mcp protocol, allowing you to embed Azure DevOps capabilities into custom automation flows and integrations.

How to install

Prerequisites:

Node.js (LTS version) installed on the host
Access to an Azure DevOps organization and a Personal Access Token (PAT) with the required scopes
Git to clone the repository (if you are pulling from a remote source)

Install steps:

Clone the MCP server repository: git clone https://github.com/your-org/azure-mcp-server.git cd azure-mcp-server
Install dependencies: npm install
Configure environment variables:
- AZURE_DEVOPS_ORG: your Azure DevOps organization name
- AZURE_DEVOPS_PROJECT: (optional) default project name to operate on
- AZURE_DEVOPS_TOKEN: your Azure DevOps Personal Access Token
- AZURE_DEVOPS_API_VERSION: optional, e.g., 6.0 (default if not provided)
Run the MCP server: node server.js
Verify the server is running by checking the console logs or hitting the MCP management endpoint as documented for your deployment environment.

Additional notes

Tips and common considerations:

Keep your PAT securely stored; avoid hard-coding it in code. Use environment variables or a secret manager.
Ensure the PAT has only the necessary scopes to reduce risk.
If you run the server behind a reverse proxy or firewall, make sure the MCP endpoints are accessible to your MCP clients.
When upgrading Azure DevOps API versions, verify compatibility with the server and adjust AZURE_DEVOPS_API_VERSION if needed.
If you run multiple MCP servers, namespace conflicts can occur; use distinct server names and endpoints for each integration.

Related MCP Servers

mcp-vegalite

MCP server from isaacwasserman/mcp-vegalite-server

github-chat

A Model Context Protocol (MCP) for analyzing and querying GitHub repositories using the GitHub Chat API.

nautex

MCP server for guiding Coding Agents via end-to-end requirements to implementation plan pipeline

pagerduty

PagerDuty's official local MCP (Model Context Protocol) server which provides tools to interact with your PagerDuty account directly from your MCP-enabled client.

futu-stock

mcp server for futuniuniu stock

mcp -boilerplate

Boilerplate using one of the 'better' ways to build MCP Servers. Written using FastMCP