MCP Server Azure Devops

What Tiberriver256/mcp-server-azure-devops MCP server does

Tiberriver256/mcp-server-azure-devops MCP server gives MCP-compatible assistants access to Azure DevOps APIs. It covers organization and project discovery, repository inspection and changes, work item management, code and wiki search, wiki retrieval, and pipeline operations.

The server supports both Azure DevOps Services and Azure DevOps Server deployments. Azure DevOps Services-only tools include retrieving the authenticated user and listing accessible organizations. The repository can be useful for teams that need on-premises Azure DevOps Server support, including older installations, or for workflows not covered by Microsoft's official Azure DevOps MCP server.

How it works

The server runs as a Node.js application and communicates with an AI client through the Model Context Protocol. Feature modules organize operations for areas such as projects, work items, repositories, and pipelines. Each exposed tool sends a corresponding request to Azure DevOps and returns the result to the assistant.

Tiberriver256/mcp-server-azure-devops MCP server can read repository files and directory trees, create branches, and commit multiple file changes using unified diffs or search-and-replace instructions. It can also retrieve, create, update, list, and link work items. Pipeline tools cover discovery, run details, artifacts, timelines, logs, and triggering runs with parameters.

Setup and configuration

The published package can be launched with npx -y @tiberriver256/mcp-server-azure-devops. Running from source requires Node.js 16 or newer, npm or yarn, dependency installation, a build, and the start script. Development mode is available through the repository's development script.

Set AZURE_DEVOPS_ORG_URL to the Azure DevOps organization URL or server collection URL. Authentication is selected with AZURE_DEVOPS_AUTH_METHOD, whose supported values are pat, azure-identity, and azure-cli; it defaults to Azure Identity. PAT authentication also requires AZURE_DEVOPS_PAT. AZURE_DEVOPS_DEFAULT_PROJECT can provide a default project when a tool call does not specify one. API version, Azure service-principal credentials, and logging can be configured with the documented optional variables.

For Claude Desktop or Cursor, configure the MCP server with the npx command and the required environment variables. Azure CLI authentication assumes the user has already completed az login.

Tools and capabilities

Available operations include:

• Inspect the authenticated user, organizations, projects, repositories, refs, statistics, and repository contents.
• Traverse repository trees and search code across repositories in a project.
• Create branches and commits, including multiple file changes.
• Retrieve, create, update, list, search, and link work items.
• List wikis, retrieve wiki pages, and search wiki content.
• List pipelines, inspect definitions and runs, download a single artifact file as text, view timelines and logs, and trigger runs.

Limitations and notes

Tiberriver256/mcp-server-azure-devops MCP server requires an Azure DevOps account with suitable permissions and valid credentials. Authentication failures, insufficient permissions, network problems, and configuration errors can prevent operations from succeeding.

Azure DevOps Server deployments support PAT authentication only. Azure Identity and Azure CLI authentication are documented for Azure DevOps Services. The get_me and list_organizations operations are also limited to Azure DevOps Services. The server should be evaluated against the official Microsoft Azure DevOps MCP server when working exclusively with Azure DevOps Services, especially if a product-supported implementation is preferred.