Skip to content
Back to search

mcp-server-azure-devops

An MCP server for Azure DevOps

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Tiberriver256/mcp-server-azure-devops with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Tiberriver256/mcp-server-azure-devops'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/tiberriver256--mcp-server-azure-devops/badge.svg)](/listings/tiberriver256--mcp-server-azure-devops)

HTML

<a href="/listings/tiberriver256--mcp-server-azure-devops"><img src="/api/listings/tiberriver256--mcp-server-azure-devops/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Prerequisites

- Node.js (v16+) - npm or yarn - Azure DevOps account with appropriate access - Authentication credentials (see [Authentication Guide](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/authentication.md) for details): - Personal Access Token (PAT), or - Azure Identity credentials, or - Azure CLI login

Running from npm (npx)

If you just want to run the **published** server package, you **do not** need to clone or build this repository:

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

Running locally (from source)

From a checkout of this repository:

npm ci
cp .env.example .env   # then edit values
npm run build
npm start              # runs: node dist/index.js

For iterative development (auto-reload):

npm run dev            # runs src/index.ts via ts-node-dev

Usage with Claude Desktop/Cursor AI

To integrate with Claude Desktop or Cursor AI, add one of the following configurations to your configuration file.

Azure Identity Authentication

Be sure you are logged in to Azure CLI with `az login` then add the following:

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

Personal Access Token (PAT) Authentication

{
  "mcpServers": {
    "azureDevOps": {
      "command": "npx",
      "args": ["-y", "@tiberriver256/mcp-server-azure-devops"],
      "env": {
        "AZURE_DEVOPS_ORG_URL": "https://dev.azure.com/your-organization",
        "AZURE_DEVOPS_AUTH_METHOD": "pat",
        "AZURE_DEVOPS_PAT": "<YOUR_PAT>",
        "AZURE_DEVOPS_DEFAULT_PROJECT": "your-project-name"
      }
    }
  }
}

Azure DevOps Server (on-prem) requires PAT authentication. Example:

{
  "mcpServers": {
    "azureDevOps": {
      "command": "npx",
      "args": ["-y", "@tiberriver256/mcp-server-azure-devops"],
      "env": {
        "AZURE_DEVOPS_ORG_URL": "https://server:8080/tfs/DefaultCollection",
        "AZURE_DEVOPS_AUTH_METHOD": "pat",
        "AZURE_DEVOPS_PAT": "<YOUR_PAT>",
        "AZURE_DEVOPS_DEFAULT_PROJECT": "your-project-name"
      }
    }
  }
}

For detailed configuration instructions and more authentication options, see the [Authentication Guide](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/authentication.md).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 272 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # Azure DevOps MCP Server
  2. A Model Context Protocol (MCP) server implementation for Azure DevOps, allowing AI assistants to interact with Azure DevOps APIs through a standardized protocol.
  3. > **Looking for the official server?** Microsoft maintains a product-supported Azure DevOps MCP at [microsoft/azure-devops-mcp](https://github.com/microsoft/azure-devops-mcp). If you use Azure DevOps Services (cloud), start there.
  4. >
  5. > This community server remains a good fit when you need **Azure DevOps Server (on-premises)** support — especially older versions that may not work with Microsoft's MCP — or features not yet available in the official server. See [Discussion #237](https://github.com/Tiberriver256/mcp-server-azure-devops/discussions/237) for more context. See [ROADMAP.md](./ROADMAP.md) for where this server differentiates and what is planned.
  6. ## Overview
  7. This server implements the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) 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:
  8. - Access and manage projects, work items, repositories, and more
  9. - Create and update work items, branches, and pull requests
  10. - Execute common DevOps workflows through natural language
  11. - Access repository content via standardized resource URIs
  12. - Safely authenticate and interact with Azure DevOps resources
  13. ## Server Structure
  14. The server is structured around the Model Context Protocol (MCP) for communicating with AI assistants. It provides tools for interacting with Azure DevOps resources including:
  15. - Projects
  16. - Work Items
  17. - Repositories
  18. - Pull Requests
  19. - Branches
  20. - Pipelines
  21. ### Core Components
  22. - **AzureDevOpsServer**: Main server class that initializes the MCP server and registers tools
  23. - **Feature Modules**: Organized by feature area (work-items, projects, repositories, etc.)
  24. - **Request Handlers**: Each feature module provides request identification and handling functions
  25. - **Tool Handlers**: Modular functions for each Azure DevOps operation
  26. - **Configuration**: Environment-based configuration for organization URL, PAT, etc.
  27. The server uses a feature-based architecture where each feature area (like work-items, projects, repositories) is encapsulated in its own module. This makes the codebase more maintainable and easier to extend with new features.
  28. ## Getting Started
  29. ### Prerequisites
  30. - Node.js (v16+)
  31. - npm or yarn
  32. - Azure DevOps account with appropriate access
  33. - Authentication credentials (see [Authentication Guide](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/authentication.md) for details):
  34. - Personal Access Token (PAT), or
  35. - Azure Identity credentials, or
  36. - Azure CLI login
  37. ### Running from npm (npx)
  38. If you just want to run the **published** server package, you **do not** need to clone or build this repository:
  39. ```bash
  40. npx -y @tiberriver256/mcp-server-azure-devops
  41. ```
  42. ### Running locally (from source)
  43. From a checkout of this repository:
  44. ```bash
  45. npm ci
  46. cp .env.example .env # then edit values
  47. npm run build
  48. npm start # runs: node dist/index.js
  49. ```
  50. For iterative development (auto-reload):
  51. ```bash
  52. npm run dev # runs src/index.ts via tsx watch
  53. ```
  54. ### Usage with Claude Desktop/Cursor AI
  55. To integrate with Claude Desktop or Cursor AI, add one of the following configurations to your configuration file.
  56. #### Azure Identity Authentication
  57. Be sure you are logged in to Azure CLI with `az login` then add the following:
  58. ```json
  59. {
  60. "mcpServers": {
  61. "azureDevOps": {
  62. "command": "npx",
  63. "args": ["-y", "@tiberriver256/mcp-server-azure-devops"],
  64. "env": {
  65. "AZURE_DEVOPS_ORG_URL": "https://dev.azure.com/your-organization",
  66. "AZURE_DEVOPS_AUTH_METHOD": "azure-identity",
  67. "AZURE_DEVOPS_DEFAULT_PROJECT": "your-project-name"
  68. }
  69. }
  70. }
  71. }
  72. ```
  73. #### Personal Access Token (PAT) Authentication
  74. ```json
  75. {
  76. "mcpServers": {
  77. "azureDevOps": {
  78. "command": "npx",
  79. "args": ["-y", "@tiberriver256/mcp-server-azure-devops"],
  80. "env": {
  81. "AZURE_DEVOPS_ORG_URL": "https://dev.azure.com/your-organization",
  82. "AZURE_DEVOPS_AUTH_METHOD": "pat",
  83. "AZURE_DEVOPS_PAT": "<YOUR_PAT>",
  84. "AZURE_DEVOPS_DEFAULT_PROJECT": "your-project-name"
  85. }
  86. }
  87. }
  88. }
  89. ```
  90. Azure DevOps Server (on-prem) requires PAT authentication. Example:
  91. ```json
  92. {
  93. "mcpServers": {
  94. "azureDevOps": {
  95. "command": "npx",
  96. "args": ["-y", "@tiberriver256/mcp-server-azure-devops"],
  97. "env": {
  98. "AZURE_DEVOPS_ORG_URL": "https://server:8080/tfs/DefaultCollection",
  99. "AZURE_DEVOPS_AUTH_METHOD": "pat",
  100. "AZURE_DEVOPS_PAT": "<YOUR_PAT>",
  101. "AZURE_DEVOPS_DEFAULT_PROJECT": "your-project-name"
  102. }
  103. }
  104. }
  105. }
  106. ```
  107. For detailed configuration instructions and more authentication options, see the [Authentication Guide](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/authentication.md).
  108. ## Authentication Methods
  109. This server supports multiple authentication methods for connecting to Azure DevOps APIs. For detailed setup instructions, configuration examples, and troubleshooting tips, see the [Authentication Guide](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/authentication.md).
  110. ### Supported Authentication Methods
  111. 1. **Personal Access Token (PAT)** - Simple token-based authentication
  112. 2. **Azure Identity (DefaultAzureCredential)** - Flexible authentication using the Azure Identity SDK
  113. 3. **Azure CLI** - Authentication using your Azure CLI login
  114. Example configuration files for each authentication method are available in the [examples directory](https://github.com/tiberriver256/mcp-server-azure-devops/tree/main/docs/examples).
  115. Azure DevOps Server (on-prem) supports PAT authentication only. Azure Identity and Azure CLI are supported for Azure DevOps Services.
  116. ## Environment Variables
  117. For a complete list of environment variables and their descriptions, see the [Authentication Guide](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/authentication.md#configuration-reference).
  118. Key environment variables include:
  119. | Variable | Description | Required | Default |
  120. | ------------------------------ | ---------------------------------------------------------------------------------- | ---------------------------- | ---------------- |
  121. | `AZURE_DEVOPS_AUTH_METHOD` | Authentication method (`pat`, `azure-identity`, or `azure-cli`) - case-insensitive | No | `azure-identity` |
  122. | `AZURE_DEVOPS_ORG_URL` | Full URL to your Azure DevOps organization or Server collection (e.g., `https://server:8080/tfs/DefaultCollection`) | Yes | - |
  123. | `AZURE_DEVOPS_PAT` | Personal Access Token (for PAT auth) | Only with PAT auth | - |
  124. | `AZURE_DEVOPS_DEFAULT_PROJECT` | Default project if none specified | No | - |
  125. | `AZURE_DEVOPS_API_VERSION` | REST api-version for the tools that call the REST API directly ([per-release values](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/authentication.md#rest-api-version)) | No | `7.1` |
  126. | `AZURE_TENANT_ID` | Azure AD tenant ID (for service principals) | Only with service principals | - |
  127. | `AZURE_CLIENT_ID` | Azure AD application ID (for service principals) | Only with service principals | - |
  128. | `AZURE_CLIENT_SECRET` | Azure AD client secret (for service principals) | Only with service principals | - |
  129. | `LOG_LEVEL` | Logging level (debug, info, warn, error) | No | info |
  130. ## Troubleshooting Authentication
  131. For detailed troubleshooting information for each authentication method, see the [Authentication Guide](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/authentication.md#troubleshooting-authentication-issues).
  132. Common issues include:
  133. - Invalid or expired credentials
  134. - Insufficient permissions
  135. - Network connectivity problems
  136. - Configuration errors
  137. ## Authentication Implementation Details
  138. For technical details about how authentication is implemented in the Azure DevOps MCP server, see the [Authentication Guide](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/authentication.md) and the source code in the `src/auth` directory.
  139. ## Available Tools
  140. The Azure DevOps MCP server provides a variety of tools for interacting with Azure DevOps resources. For detailed documentation on each tool, please refer to the corresponding documentation.
  141. ### User Tools
  142. - `get_me`: Get details of the authenticated user (id, displayName, email) (Azure DevOps Services only)
  143. ### Organization Tools
  144. - `list_organizations`: List all accessible organizations (Azure DevOps Services only)
  145. ### Project Tools
  146. - `list_projects`: List all projects in an organization
  147. - `get_project`: Get details of a specific project
  148. - `get_project_details`: Get comprehensive details of a project including process, work item types, and teams
  149. ### Repository Tools
  150. - `list_repositories`: List all repositories in a project
  151. - `get_repository`: Get details of a specific repository
  152. - `get_repository_details`: Get detailed information about a repository including statistics and refs
  153. - `get_file_content`: Get content of a file or directory from a repository
  154. - `get_repository_tree`: List a repository's file tree from any path and depth
  155. - `create_branch`: Create a new branch from an existing one
  156. - `create_commit`: Commit multiple file changes to a branch using unified diffs or search/replace instructions
  157. ### Work Item Tools
  158. - `get_work_item`: Retrieve a work item by ID
  159. - `create_work_item`: Create a new work item
  160. - `update_work_item`: Update an existing work item
  161. - `list_work_items`: List work items in a project
  162. - `manage_work_item_link`: Add, remove, or update links between work items
  163. - `create_work_item_attachment`: Upload and attach a file to a work item
  164. - `get_work_item_attachment`: Download an attachment from a work item
  165. - `delete_work_item_attachment`: Delete an attachment from a work item
  166. ### Search Tools
  167. - `search_code`: Search for code across repositories in a project
  168. - `search_wiki`: Search for content across wiki pages in a project
  169. - `search_work_items`: Search for work items across projects in Azure DevOps
  170. ### Pipelines Tools
  171. - `list_pipelines`: List pipelines in a project
  172. - `get_pipeline`: Get details of a specific pipeline
  173. - `list_pipeline_runs`: List recent runs for a pipeline with optional filters
  174. - `get_pipeline_run`: Get detailed run information and artifact summaries
  175. - `download_pipeline_artifact`: Download a single artifact file as text
  176. - `pipeline_timeline`: Retrieve the stage and job timeline for a run
  177. - `get_pipeline_log`: Retrieve raw or JSON-formatted log content
  178. - `trigger_pipeline`: Trigger a pipeline run with customizable parameters
  179. ### Wiki Tools
  180. - `get_wikis`: List all wikis in a project
  181. - `get_wiki_page`: Get content of a specific wiki page as plain text
  182. ### Pull Request Tools
  183. - [`create_pull_request`](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/tools/pull-requests.md#create_pull_request) - Create a new pull request
  184. - [`get_pull_request`](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/tools/pull-requests.md#get_pull_request) - Get a pull request by ID
  185. - [`list_pull_requests`](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/tools/pull-requests.md#list_pull_requests) - List pull requests in a repository
  186. - [`add_pull_request_comment`](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/tools/pull-requests.md#add_pull_request_comment) - Add a comment to a pull request
  187. - [`get_pull_request_comments`](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/tools/pull-requests.md#get_pull_request_comments) - Get comments from a pull request
  188. - [`update_pull_request`](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/tools/pull-requests.md#update_pull_request) - Update an existing pull request (title, description, status, draft state, reviewers, work items)
  189. - [`get_pull_request_changes`](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/tools/pull-requests.md#get_pull_request_changes) - List changes in a pull request and policy evaluation status
  190. - [`get_pull_request_checks`](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/docs/tools/pull-requests.md#get_pull_request_checks) - Summarize status checks, policy evaluations, and their related pipelines
  191. For comprehensive documentation on all tools, see the [Tools Documentation](https://github.com/tiberriver256/mcp-server-azure-devops/tree/main/docs/tools).
  192. ## Contributing
  193. Contributions are welcome! Please see [CONTRIBUTING.md](https://github.com/tiberriver256/mcp-server-azure-devops/blob/main/CONTRIBUTING.md) for contribution guidelines.
  194. ## Star History
  195. [![Star History Chart](https://star-history.dera.page/svg?repos=tiberriver256/mcp-server-azure-devops&type=Date)](https://star-history.dera.page/#tiberriver256/mcp-server-azure-devops&Date)
  196. ## License
  197. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.