# Tiberriver256/mcp-server-azure-devops [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://github.com/Tiberriver256/mcp-server-azure-devops  
**GitHub Stars:** 397  
**npm Downloads (last month):** 22189  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/tiberriver256-mcp-server-azure-devops

## Description
Azure DevOps integration for repository management, work items, and pipelines.

## Tools
Capabilities this server exposes over MCP:

- **get_me** — Get details of the authenticated user (id, displayName, email) (Azure DevOps Services only)
- **list_organizations** — List all accessible organizations (Azure DevOps Services only)
- **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_repository_tree** — List a repository's file tree from any path and depth
- **create_branch** — Create a new branch from an existing one
- **create_commit** — Commit multiple file changes to a branch using unified diffs or search/replace instructions
- **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
- **list_work_items** — List work items in a project
- **manage_work_item_link** — Add, remove, or update links between work items
- **create_work_item_attachment** — Upload and attach a file to a work item
- **get_work_item_attachment** — Download an attachment from a work item
- **delete_work_item_attachment** — Delete an attachment from a work item
- **search_code** — Search for code across repositories in a project
- **search_wiki** — Search for content across wiki pages in a project
- **search_work_items** — Search for work items across projects in Azure DevOps
- **list_pipelines** — List pipelines in a project
- **get_pipeline** — Get details of a specific pipeline
- **list_pipeline_runs** — List recent runs for a pipeline with optional filters
- **get_pipeline_run** — Get detailed run information and artifact summaries
- **download_pipeline_artifact** — Download a single artifact file as text
- **pipeline_timeline** — Retrieve the stage and job timeline for a run
- **get_pipeline_log** — Retrieve raw or JSON-formatted log content
- **trigger_pipeline** — Trigger a pipeline run with customizable parameters
- **get_wikis** — List all wikis in a project
- **get_wiki_page** — Get content of a specific wiki page as plain text

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-server-azure-devops": {
    "command": "npx",
    "args": ["-y","@tiberriver256/mcp-server-azure-devops"],
    "env": {
      "AZURE_DEVOPS_ORG_URL": "",
      "AZURE_DEVOPS_AUTH_METHOD": "",
      "AZURE_DEVOPS_PAT": "",
      "AZURE_DEVOPS_DEFAULT_PROJECT": "",
      "AZURE_DEVOPS_API_VERSION": "",
      "AZURE_TENANT_ID": "",
      "AZURE_CLIENT_ID": "",
      "AZURE_CLIENT_SECRET": ""
    }
  }
}
```

**Requires environment variables:** `AZURE_DEVOPS_ORG_URL`, `AZURE_DEVOPS_AUTH_METHOD`, `AZURE_DEVOPS_PAT`, `AZURE_DEVOPS_DEFAULT_PROJECT`, `AZURE_DEVOPS_API_VERSION`, `AZURE_TENANT_ID`, `AZURE_CLIENT_ID`, `AZURE_CLIENT_SECRET` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

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

Tiberriver256/mcp-server-azure-devops exposes Azure DevOps operations through the Model Context Protocol. It covers organization and project discovery, repository inspection and editing, work item management, code and wiki search, and pipeline monitoring.

The repository tools can retrieve files, directories, and repository trees, inspect repository metadata, create branches, and commit multiple changes using unified diffs or search-and-replace instructions. Work item tools retrieve, create, update, search, link, and attach files to work items. Pipeline tools list pipelines, inspect runs, retrieve timelines and logs, and download an individual artifact file as text.

## How it works

The server runs as an MCP process and translates tool requests into Azure DevOps API operations. Its implementation is organized by feature areas, with separate modules and handlers for resources such as projects, repositories, work items, and pipelines.

Authentication can use a Personal Access Token, Azure Identity through the Azure Identity SDK, or an existing Azure CLI login. Azure DevOps Services supports all three methods. Azure DevOps Server deployments use PAT authentication. Some identity and organization-discovery operations, including `get_me` and `list_organizations`, are specific to Azure DevOps Services.

## Setup and configuration

The published package can run through `npx`:

```bash
npx -y @tiberriver256/mcp-server-azure-devops
```

For a source checkout, install dependencies, copy `.env.example` to `.env`, build the project, and start it with `npm start`. `npm run dev` runs the TypeScript source with watch mode for iterative development. Node.js 16 or newer, npm or yarn, an Azure DevOps account, and suitable permissions are required.

Set `AZURE_DEVOPS_ORG_URL` to the organization or server collection URL. Choose `pat`, `azure-identity`, or `azure-cli` with `AZURE_DEVOPS_AUTH_METHOD`; the default is Azure Identity. PAT authentication also requires `AZURE_DEVOPS_PAT`. `AZURE_DEVOPS_DEFAULT_PROJECT` can provide a project when a tool call does not specify one. Service-principal authentication uses `AZURE_TENANT_ID`, `AZURE_CLIENT_ID`, and `AZURE_CLIENT_SECRET`.

Claude Desktop and Cursor can launch the server with an MCP configuration using the `npx` command and environment variables. Azure CLI authentication requires an earlier `az login`.

## Tools and capabilities

- Discover the authenticated user, organizations, projects, repositories, and teams.
- Read repository files, directories, metadata, refs, statistics, and file trees.
- Create branches and commit multiple file changes.
- Create, update, retrieve, search, link, and attach files to work items.
- Search code, wiki pages, and work items.
- List pipelines, inspect runs, retrieve timelines and logs, and download text artifacts.

## Limitations and notes

Azure DevOps Server on-premises requires PAT authentication, while Azure Identity and Azure CLI authentication apply to Azure DevOps Services. Access depends on the permissions of the configured account or token. REST-based tools use API version 7.1 by default, configurable through `AZURE_DEVOPS_API_VERSION`. Logging verbosity can be changed with `LOG_LEVEL`.

_Full upstream README: https://allmcps.com/mcp/tiberriver256-mcp-server-azure-devops/readme_