Azure DevOps Pull Request MCP Server

What is Azure DevOps Pull Request MCP Server?

A Model Context Protocol (MCP) server that provides tools for interacting with Azure DevOps pull requests. It can retrieve pull request details, fetch thread comments, and create new comment threads at specific code locations. Built with C#/.NET using the ModelContextProtocol NuGet package, it is intended as a learning project for Azure DevOps API integration.

How to use Azure DevOps Pull Request MCP Server?

Clone the repo, build with dotnet build -c Release, then add the server to your VSCode MCP settings JSON with command "dotnet" and args pointing to the DLL. Authentication can be Azure Identity (DefaultAzureCredential, recommended) or PAT (set via AZURE_DEVOPS_PAT env). Run with dotnet run -- --pr-url <URL> (optionally --pat). Available tools: GetPrDetails, GetPrThreads, CreatePrThread.

Key features of Azure DevOps Pull Request MCP Server

• Retrieves pull request details (GetPrDetails)
• Fetches pull request comment threads (GetPrThreads)
• Creates new comment threads at specific code locations (CreatePrThread)
• Supports Azure Identity and Personal Access Token authentication
• Built with C#/.NET using the ModelContextProtocol package
• Communicates via stdio transport

Use cases of Azure DevOps Pull Request MCP Server

• Review a pull request with an AI assistant via MCP
• Get a high-level overview of a PR and examine changed files
• Fetch all existing review comments on a pull request
• Add inline code comments to specific lines during review

FAQ from Azure DevOps Pull Request MCP Server

What does the Azure DevOps Pull Request MCP Server do?

It provides MCP tools to retrieve PR details, get threads/comments, and create comment threads at specific code locations in Azure DevOps.

What are the runtime requirements?

The server requires .NET 8.0 SDK. It communicates via standard I/O (stdio) and uses the ModelContextProtocol NuGet package.

How does authentication work?

Two methods: recommended Azure Identity (DefaultAzureCredential) or legacy Personal Access Token (PAT). The PAT must have Code (Read & Write) and Pull Request Threads (Read & Write) scopes. If no PAT is configured, DefaultAzureCredential is used automatically.

What are the current limitations?

The project is a work in progress. Upcoming features include packaging as a dotnet tool, the ability to respond to existing threads, add comments to existing threads, and better thread management. Currently only creating new threads is supported.

Where does the data live?

The server interacts with Azure DevOps via its REST APIs. No data is stored locally; all pull request data resides in your Azure DevOps organization.