Azure DevOps

io.github.billg118Published by GitHub account billg118v0.1.54Updated Nov 5, 2026

Azure DevOps MCP server: projects, repos, work items, pull requests, pipelines, and wikis.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Community MCP server that lets an AI assistant read and change Azure DevOps projects, repos, work items, pull requests, pipelines and wikis.

What you can do
  • Browse organizations, projects, repositories, file trees and file contents
  • Search code, wiki pages and work items across projects
  • Create and update work items, links, comments and attachments
  • Create branches and commits, and open, comment on or update pull requests
  • Inspect pipelines, runs, timelines, logs and artifacts, and trigger runs
  • Read wiki pages and check pull request status checks and policy evaluations
When to use it
Useful when an assistant should work directly inside Azure DevOps: triaging and updating work items, reviewing pull requests and their checks, searching code or wikis, or inspecting pipeline failures. The README positions it as a fit for Azure DevOps Server (on-premises) and older versions, and points cloud users to Microsoft's official server first.
Requirements
Runs locally via npx with Node.js 16+ and npm. Needs an Azure DevOps account with access, the AZURE_DEVOPS_ORG_URL variable, and one of: a PAT in AZURE_DEVOPS_PAT, Azure Identity credentials, or an Azure CLI login. AZURE_DEVOPS_AUTH_METHOD and AZURE_DEVOPS_DEFAULT_PROJECT are optional; service principals also use AZURE_TENANT_ID, AZURE_CLIENT_ID and AZURE_CLIENT_SECRET. On-premises servers accept PAT only.
Before you install
The PAT in AZURE_DEVOPS_PAT and any AZURE_CLIENT_SECRET are secrets; scope the token narrowly. Many tools write to Azure DevOps: creating and updating work items, branches, commits, pull requests, comments and links, deleting attachments, and triggering pipeline runs, which may consume build minutes or deploy. Attachment tools read from and write to the local filesystem. Data goes to the Azure DevOps endpoint you configure.

Installation

In SourceWeft

  1. Open Azure DevOps in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Azure DevOps MCP Server

A Model Context Protocol (MCP) server implementation for Azure DevOps, allowing AI assistants to interact with Azure DevOps APIs through a standardized protocol.

Looking for the official server? Microsoft maintains a product-supported Azure DevOps MCP at microsoft/azure-devops-mcp. If you use Azure DevOps Services (cloud), start there.

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 for more context. See ROADMAP.md for where this server differentiates and what is planned.

Overview

This server implements the Model Context Protocol (MCP) 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:

  • Access and manage projects, work items, repositories, and more
  • Create and update work items, branches, and pull requests
  • Execute common DevOps workflows through natural language
  • Access repository content via standardized resource URIs
  • Safely authenticate and interact with Azure DevOps resources

Server Structure

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:

  • Projects
  • Work Items
  • Repositories
  • Pull Requests
  • Branches
  • Pipelines

Core Components

  • AzureDevOpsServer: Main server class that initializes the MCP server and registers tools
  • Feature Modules: Organized by feature area (work-items, projects, repositories, etc.)
  • Request Handlers: Each feature module provides request identification and handling functions
  • Tool Handlers: Modular functions for each Azure DevOps operation
  • Configuration: Environment-based configuration for organization URL, PAT, etc.

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.

Getting Started

Prerequisites

  • Node.js (v16+)
  • npm or yarn
  • Azure DevOps account with appropriate access
  • Authentication credentials (see Authentication Guide 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:

bash
npx -y @billg118/mcp-server-azure-devops

Running locally (from source)

From a checkout of this repository:

bash
npm cicp .env.example .env   # then edit valuesnpm run buildnpm start              # runs: node dist/index.js

For iterative development (auto-reload):

bash
npm run dev            # runs src/index.ts via tsx watch

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:

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

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

Authentication Methods

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.

Supported Authentication Methods

  1. Personal Access Token (PAT) - Simple token-based authentication
  2. Azure Identity (DefaultAzureCredential) - Flexible authentication using the Azure Identity SDK
  3. Azure CLI - Authentication using your Azure CLI login

Example configuration files for each authentication method are available in the examples directory.

Azure DevOps Server (on-prem) supports PAT authentication only. Azure Identity and Azure CLI are supported for Azure DevOps Services.

Environment Variables

For a complete list of environment variables and their descriptions, see the Authentication Guide.

Key environment variables include:

VariableDescriptionRequiredDefault
AZURE_DEVOPS_AUTH_METHODAuthentication method (pat, azure-identity, or azure-cli) - case-insensitiveNoazure-identity
AZURE_DEVOPS_ORG_URLFull URL to your Azure DevOps organization or Server collection (e.g., https://server:8080/tfs/DefaultCollection)Yes-
AZURE_DEVOPS_PATPersonal Access Token (for PAT auth)Only with PAT auth-
AZURE_DEVOPS_DEFAULT_PROJECTDefault project if none specifiedNo-
AZURE_DEVOPS_API_VERSIONREST api-version for the tools that call the REST API directly (per-release values)No7.1
AZURE_TENANT_IDAzure AD tenant ID (for service principals)Only with service principals-
AZURE_CLIENT_IDAzure AD application ID (for service principals)Only with service principals-
AZURE_CLIENT_SECRETAzure AD client secret (for service principals)Only with service principals-
LOG_LEVELLogging level (debug, info, warn, error)Noinfo

Troubleshooting Authentication

For detailed troubleshooting information for each authentication method, see the Authentication Guide.

Common issues include:

  • Invalid or expired credentials
  • Insufficient permissions
  • Network connectivity problems
  • Configuration errors

Authentication Implementation Details

For technical details about how authentication is implemented in the Azure DevOps MCP server, see the Authentication Guide and the source code in the src/auth directory.

Available Tools

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.

User Tools

  • get_me: Get details of the authenticated user (id, displayName, email) (Azure DevOps Services only)

Organization Tools

  • list_organizations: List all accessible organizations (Azure DevOps Services only)

Project Tools

  • 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

Repository Tools

  • 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

Work Item Tools

  • 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 Tools

  • 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

Pipelines Tools

  • 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

Wiki Tools

  • get_wikis: List all wikis in a project
  • get_wiki_page: Get content of a specific wiki page as plain text

Pull Request Tools

For comprehensive documentation on all tools, see the Tools Documentation.

Contributing

Contributions are welcome! Please see CONTRIBUTING.md for contribution guidelines.

Star History

[Star History Chart]

License

MIT

Source: README.md at commit d5e8305

Tools

49

get_me

Get details of the authenticated user (id, displayName, email)

Takes no parameters.

list_organizations

List all Azure DevOps organizations accessible to the current authentication

Takes no parameters.

list_projects

List all projects in an organization

ParameterstopskipstateFilterorganizationIdcontinuationToken

get_project

Get details of a specific project

ParametersprojectIdorganizationId

get_project_details

Get comprehensive details of a project including process, work item types, and teams

ParametersprojectIdincludeTeamsrequiredincludeFieldsrequiredincludeProcessrequiredorganizationIdexpandTeamIdentityrequiredincludeWorkItemTypesrequired

get_repository

Get details of a specific repository

ParametersprojectIdrepositoryIdrequiredorganizationId

get_repository_details

Get detailed information about a repository including statistics and refs

ParametersprojectIdrefFilterbranchNameincludeRefsrequiredrepositoryIdrequiredorganizationIdincludeStatisticsrequired

list_repositories

List repositories in a project

ParametersprojectIdincludeLinksorganizationId

get_file_content

Get content of a file or directory from a repository

ParameterspathrequiredversionprojectIdversionTyperepositoryIdrequiredorganizationId

get_all_repositories_tree

Displays a hierarchical tree view of files and directories across multiple Azure DevOps repositories within a project, based on their default branches

ParametersdepthrequiredpatternprojectIdorganizationIdrepositoryPattern

get_repository_tree

Displays a hierarchical tree view of files and directories within a single repository starting from an optional path

ParameterspathrequireddepthrequiredprojectIdrepositoryIdrequiredorganizationId

create_branch

Create a new branch from an existing one

ParametersnewBranchrequiredprojectIdrepositoryIdrequiredsourceBranchrequiredorganizationId

create_commit

Create a commit on an existing branch using file changes. - Provide plain branch names (no "refs/heads/"). - ⚠️ Each file path may appear only once per commit request—combine all edits to a file into a single change entry. - Prefer multiple commits when you have sparse or unrelated edits; smaller focused commits keep review context clear. 🎯 RECOMMENDED: Use the SEARCH/REPLACE format (much easier, no line counting!). **Option 1: SEARCH/REPLACE format (EASIEST)** Simply provide the exact text to find and replace: ```json { "changes": [{ "path": "src/api/services/function-call.ts", "search": "return axios.post(apiUrl, payload, requestConfig);", "replace": "return axios.post(apiUrl, payload, requestConfig).then(r => { processResponse(r); return r; });" }] } ``` The server fetches the file, performs the replacement, and generates the diff automatically. No line counting, no hunk headers, no context lines needed! **Option 2: UNIFIED DIFF format (Advanced)** If you prefer full control, provide complete unified diffs: - Each patch MUST have complete hunk headers: @@ -oldStart,oldLines +newStart,newLines @@ - CRITICAL: Every @@ marker MUST include line numbers. Do NOT use @@ without line ranges. - Include 3-5 context lines before and after changes. - For deletions: `--- a/filepath` and `+++ /dev/null` - For additions: `--- /dev/null` and `+++ b/filepath` Example unified diff: ```json { "changes": [{ "patch": "diff --git a/file.yaml b/file.yaml\n--- a/file.yaml\n+++ b/file.yaml\n@@ -4,7 +4,7 @@ spec:\n spec:\n type: ClusterIP\n ports:\n- - port: 8080\n+ - port: 9090\n targetPort: http\n" }] } ```

ParameterschangesrequiredprojectIdbranchNamerequiredrepositoryIdrequiredcommitMessagerequiredorganizationId

list_commits

List recent commits on a branch including file-level diff content for each commit

ParameterstopskipprojectIdbranchNamerequiredrepositoryIdrequiredorganizationId

list_work_items

List work items in a project

ParameterstopskipwiqlfieldsteamIdqueryIdprojectIdorganizationId

get_work_item

Get details of a specific work item

ParametersexpandworkItemIdrequired

create_work_item

Create a new work item

ParameterstagstitlerequiredareaPathparentIdpriorityprojectIdassignedTodescriptionworkItemTyperequirediterationPathorganizationIdadditionalFields

update_work_item

Update an existing work item

ParameterstagsstatetitleareaPathprioritytagsToAddassignedToworkItemIdrequireddescriptiontagsToRemoveiterationPathadditionalFields

get_work_item_comments

Get comments and discussion history for a specific work item

ParameterstoporderrequiredexpandrequiredprojectIdworkItemIdrequiredincludeDeletedcontinuationToken

create_work_item_attachment

Upload a file and attach it to a work item. The file is read from the local filesystem, uploaded to Azure DevOps, and linked to the specified work item.

ParameterscommentfileNamefilePathrequiredworkItemIdrequired

get_work_item_attachment

Download an attachment from Azure DevOps and save it to the local filesystem. The attachment ID can be obtained from the work item relations.

ParametersoutputPathrequiredattachmentIdrequired

delete_work_item_attachment

Delete an attachment from a work item. The attachment ID can be obtained from the work item relations.

ParametersworkItemIdrequiredattachmentIdrequired

search_code

Search for code across repositories in a project

ParameterstoprequiredskiprequiredfiltersprojectIdsearchTextrequiredincludeContentrequiredincludeSnippetrequiredorganizationId

search_wiki

Search for content across wiki pages in a project

ParameterstoprequiredskiprequiredfiltersprojectIdsearchTextrequiredincludeFacetsrequiredorganizationId

search_work_items

Search for work items across projects in Azure DevOps

ParameterstoprequiredskiprequiredfiltersorderByprojectIdsearchTextrequiredincludeFacetsrequiredorganizationId

create_pull_request

Create a new pull request, including reviewers, linked work items, and optional tags

ParameterstagstitlerequiredisDraftprojectIdreviewersdescriptionrepositoryIdrequiredworkItemRefssourceRefNamerequiredtargetRefNamerequiredorganizationIdadditionalProperties

get_pull_request

Get a pull request by ID (no repositoryId required; best for Azure DevOps Server where PR IDs are project-scoped)

ParametersprojectIdrequiredpullRequestIdrequiredorganizationId

list_pull_requests

List pull requests in a repository

ParameterstoprequiredskipstatuscreatorIdprojectIdreviewerIdrepositoryIdrequiredsourceRefNametargetRefNameorganizationId

get_pull_request_comments

Get comments from a specific pull request

ParameterstopthreadIdprojectIdrepositoryIdrequiredpullRequestIdrequiredincludeDeletedorganizationId

add_pull_request_comment

Add a comment to a pull request (repositoryId optional; derived from pullRequestId when omitted)

ParametersstatuscontentrequiredfilePaththreadIdprojectIdlineNumberrepositoryIdpullRequestIdrequiredorganizationIdparentCommentId

update_pull_request

Update an existing pull request with new properties, manage reviewers and work items, and add or remove tags

ParameterstitlestatusaddTagsisDraftprojectIdremoveTagsdescriptionaddReviewersrepositoryIdrequiredpullRequestIdrequiredaddWorkItemIdsorganizationId+3 more

get_pull_request_changes

Get the files changed in a pull request, their unified diffs, source/target branch names, and the status of policy evaluations

ParametersprojectIdrepositoryIdrequiredpullRequestIdrequiredorganizationId

get_pull_request_checks

Summarize the latest status checks and policy evaluations for a pull request. - Surfaces pipeline and run identifiers so you can jump straight to the blocking validation. - Pair with pipeline tools (e.g., get_pipeline_run, pipeline_timeline) to inspect failures in depth.

ParametersprojectIdrepositoryIdrequiredpullRequestIdrequiredorganizationId

update_pull_request_thread_status

Update the status of a comment thread in a pull request (repositoryId optional; derived from pullRequestId when omitted)

ParametersstatusrequiredthreadIdrequiredprojectIdrepositoryIdpullRequestIdrequiredorganizationId

list_pipelines

List pipelines in a project

ParameterstoporderByprojectId

get_pipeline

Get details of a specific pipeline

ParametersprojectIdpipelineIdrequiredpipelineVersion

list_pipeline_runs

List recent runs for a pipeline

ParameterstoprequiredstatebranchresultorderByrequiredcreatedToprojectIdpipelineIdrequiredcreatedFromcontinuationToken

get_pipeline_run

Get details for a specific pipeline run

ParametersrunIdrequiredprojectIdpipelineId

download_pipeline_artifact

Download a file from a pipeline run artifact and return its textual content

ParametersrunIdrequiredprojectIdpipelineIdartifactPathrequired

pipeline_timeline

Retrieve the timeline of stages and jobs for a pipeline run, to reduce the amount of data returned, you can filter by state and result

ParametersrunIdrequiredstateresultprojectIdpipelineIdtimelineId

get_pipeline_log

Retrieve a specific pipeline log using the timeline log identifier

ParameterslogIdrequiredrunIdrequiredformatendLineprojectIdstartLinepipelineId

trigger_pipeline

Trigger a pipeline run

ParametersbranchprojectIdvariablespipelineIdrequiredstagesToSkiptemplateParameters

get_wikis

Get details of wikis in a project

ParametersprojectIdorganizationId

get_wiki_page

Get the content of a wiki page

ParameterswikiIdrequiredpagePathrequiredprojectIdorganizationId

create_wiki

Create a new wiki in the project

ParametersnamerequiredtyperequiredprojectIdmappedPathrequiredrepositoryIdorganizationId

update_wiki_page

Update content of a wiki page

ParameterswikiIdrequiredcommentcontentrequiredpagePathrequiredprojectIdorganizationId

list_wiki_pages

List pages within an Azure DevOps wiki

ParameterswikiIdrequiredprojectIdorganizationId

create_wiki_page

Create a new page in a wiki. If the page already exists at the specified path, it will be updated.

ParameterswikiIdrequiredcommentcontentrequiredpagePathrequiredprojectIdorganizationId

Version history

1
  1. v0.1.54LatestNov 5, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts