azure-devops -2024

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-devops-mcp-server-2024 node server.js \
  --env AZURE_DEVOPS_ORG="your-organization-name" \
  --env AZURE_DEVOPS_PAT="your-personal-access-token"

How to use

This MCP server provides a bridge to the Azure DevOps API, enabling programmatic interaction with your Azure DevOps projects, repositories, work items, and other resources. Once running, you can use the server's exposed MCP endpoints to automate common workflows such as creating and managing projects, listing repositories, reading or updating work items, and triggering pipelines. The included environment variables allow you to authenticate with Azure DevOps using a personal access token and target a specific organization. Typical usage involves starting the server and then invoking its endpoints from your automation scripts or other MCP-enabled tools to integrate Azure DevOps into your CI/CD or tooling pipelines.

How to install

Prerequisites:

Node.js and npm installed on your machine
Access to an Azure DevOps organization and a Personal Access Token (PAT) with appropriate scopes

Installation steps:

Clone the MCP server repository or download the release artifacts.
Install dependencies: npm install
Configure environment variables (see mcp_config below) or create a .env file with the following keys: AZURE_DEVOPS_ORG=<your-organization> AZURE_DEVOPS_PAT=<your-pat>
Start the server: node server.js
(Optional) Run the server in production or via a process manager (e.g., PM2) for resilience.

Configuration example (env vs command-line):

If using environment variables, ensure they are exported in your shell before starting: export AZURE_DEVOPS_ORG=my-org export AZURE_DEVOPS_PAT=yourpat
If using a .env file, ensure your startup script loads it prior to launching the server.

Additional notes

Notes and tips:

Keep your Azure DevOps PAT secured; use scope-limited tokens and rotate regularly.
The MCP server relies on the Azure DevOps REST APIs; some operations may be subject to API rate limits.
If you encounter authentication errors, re-check PAT scopes and organization name.
For local development, you can set AZURE_DEVOPS_ORG and AZURE_DEVOPS_PAT as environment variables or adjust the code to read from a config file.
Ensure Node.js version compatibility with the server codebase and dependencies.
Consider running behind a reverse proxy and enabling TLS in production environments.