MCP Azure DevOps Server
A Model Context Protocol (MCP) server for Azure DevOps integration, enabling AI assistants to interact with Azure DevOps Work Items, Git Repositories, Pull Requests, and Pipelines.
Quick Start
Get up and running in 3 steps:
1. Clone and configure
git clone https://github.com/viamus/mcp-azure-devops.git
cd mcp-azure-devops
Edit src/Viamus.Azure.Devops.Mcp.Server/appsettings.json with your Azure DevOps credentials:
{
"AzureDevOps": {
"OrganizationUrl": "https://dev.azure.com/your-organization",
"PersonalAccessToken": "your-personal-access-token",
"DefaultProject": "your-project-name"
}
}
Need a PAT? See Creating a Personal Access Token below.
2. Run the server
Option A - Docker (recommended):
docker compose up -d
# Server runs at http://localhost:8080
Option B - .NET CLI:
dotnet run --project src/Viamus.Azure.Devops.Mcp.Server
# Server runs at http://localhost:5000
3. Verify it's working
# Docker
curl http://localhost:8080/health
# .NET CLI
curl http://localhost:5000/health
You should see: Healthy
Automated Installation (Windows)
For Windows users, a PowerShell script is available that automates the entire setup process:
# Download and run the installer (as Administrator)
irm https://raw.githubusercontent.com/viamus/mcp-azure-devops/main/install-mcp-azure-devops.ps1 -OutFile install-mcp-azure-devops.ps1
.\install-mcp-azure-devops.ps1 `
-OrganizationUrl "https://dev.azure.com/your-organization" `
-PersonalAccessToken "your-pat-token" `
-DefaultProject "your-project-name"
The script will automatically:
- Install .NET 10 SDK (if not present)
- Install Node.js (if not present)
- Install Claude Code CLI (if not present)
- Clone the repository
- Configure your Azure DevOps credentials
- Register the MCP server with Claude Code (HTTP transport)
After installation, start the server:
cd $env:USERPROFILE\mcp-azure-devops
dotnet run --project src/Viamus.Azure.Devops.Mcp.Server
About
This project implements an MCP server that exposes tools for querying and managing Work Items and Git Repositories in Azure DevOps. It can be used with any compatible MCP client, such as Claude Desktop, Claude Code, or other assistants that support the protocol.
Available Tools
Work Item Tools
| Tool | Description |
|---|---|
get_work_item | Gets details of a specific work item by ID |
get_work_items | Gets multiple work items by IDs (batch retrieval) |
query_work_items | Queries work items using WIQL (Work Item Query Language) |
get_work_items_by_state | Filters work items by state (Active, New, Closed, etc.) |
get_work_items_assigned_to | Gets work items assigned to a specific user |
get_child_work_items | Gets child work items of a parent work item |
get_recent_work_items | Gets recently changed work items |
search_work_items | Searches work items by title text |
add_work_item_comment | Adds a comment to a specific work item |
Git Repository Tools
| Tool | Description |
|---|---|
get_repositories | Lists all Git repositories in a project |
get_repository | Gets details of a specific repository by name or ID |
get_branches | Lists all branches in a repository |
get_repository_items | Browses files and folders at a specific path in a repository |
get_file_content | Gets the content of a specific file in a repository |
search_repository_files | Searches for files by path pattern in a repository |
Pull Request Tools
| Tool | Description |
|---|---|
get_pull_requests | Lists pull requests with optional filters (status, creator, reviewer, branches) |
get_pull_request | Gets details of a specific pull request by ID |
get_pull_request_threads | Gets comment threads for a pull request |
search_pull_requests | Searches pull requests by text in title or description |
query_pull_requests | Advanced query with multiple combined filters |
Pipeline/Build Tools
| Tool | Description |
|---|---|
get_pipelines | Lists all pipelines (build definitions) in a project |
get_pipeline | Gets details of a specific pipeline by ID |
get_pipeline_runs | Gets recent runs (builds) for a specific pipeline |
get_build | Gets details of a specific build by ID |
get_builds | Lists builds with optional filters (status, result, branch, requester) |
get_build_logs | Gets the list of log files for a build |
get_build_log_content | Gets the content of a specific build log |
get_build_timeline | Gets the timeline (stages, jobs, tasks) for a build |
query_builds | Advanced query with multiple combined filters |
Prerequisites
| Requirement | Version | Notes |
|---|---|---|
| .NET SDK | 10.0+ | Required for local development |
| Docker | Latest | Recommended for running |
| Azure DevOps Account | - | With Personal Access Token |
Creating a Personal Access Token (PAT)
- Go to your Azure DevOps organization:
https://dev.azure.com/{your-org} - Click on User Settings (gear icon) > Personal Access Tokens
- Click + New Token
- Configure:
- Name:
MCP Server(or any name you prefer) - Expiration: Choose based on your needs
- Scopes: Select the following permissions:
- Name:
| Scope | Permission | Required for |
|---|---|---|
| Work Items | Read & Write | Work item operations |
| Code | Read | Git repositories and Pull Requests |
| Build | Read | Pipelines and Builds |
- Click Create and copy the token immediately (you won't see it again!)
Running Options
Option 1: Docker Compose (Recommended)
Best for: Production use, quick setup without .NET installed
docker compose up -d
Server URL: http://localhost:8080
Useful commands:
docker compose logs -f # View logs
docker compose down # Stop the server
docker compose up -d --build # Rebuild and start
Option 2: .NET CLI
Best for: Development, debugging
dotnet run --project src/Viamus.Azure.Devops.Mcp.Server
Server URL: http://localhost:5000
Option 3: Self-Contained Executable
Best for: Deployment without .NET runtime
# Windows
dotnet publish src/Viamus.Azure.Devops.Mcp.Server -c Release -r win-x64 -o ./publish/win-x64
# Linux
dotnet publish src/Viamus.Azure.Devops.Mcp.Server -c Release -r linux-x64 -o ./publish/linux-x64
# macOS (Intel)
dotnet publish src/Viamus.Azure.Devops.Mcp.Server -c Release -r osx-x64 -o ./publish/osx-x64
# macOS (Apple Silicon)
dotnet publish src/Viamus.Azure.Devops.Mcp.Server -c Release -r osx-arm64 -o ./publish/osx-arm64
Then run the executable directly:
# Windows
./publish/win-x64/Viamus.Azure.Devops.Mcp.Server.exe
# Linux/macOS
./publish/linux-x64/Viamus.Azure.Devops.Mcp.Server
Client Configuration
Claude Desktop
Option A - Using CLI (recommended):
claude mcp add azure-devops --transport http http://localhost:8080
Option B - Manual configuration:
Edit claude_desktop_config.json:
- Windows:
%APPDATA%\Claude\claude_desktop_config.json - macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"azure-devops": {
"url": "http://localhost:8080"
}
}
}
Claude Code
Run from your project directory:
claude mcp add azure-devops --transport http http://localhost:8080
Or add manually to .claude/settings.json:
{
"mcpServers": {
"azure-devops": {
"type": "http",
"url": "http://localhost:8080"
}
}
}
Note: Use port
5000if running with .NET CLI, or8080if running with Docker.
Usage Examples
After configuring the MCP client, you can ask questions like:
Work Items
- "List the active work items in project X"
- "What bugs are assigned to me?"
- "Show me the details of work item #1234"
- "What work items were changed in the last 7 days?"
- "Search for work items with 'login' in the title"
- "Add a comment to work item #1234 saying the bug was fixed"
Git Repositories
- "List all repositories in project X"
- "Show me the branches in the 'my-app' repository"
- "What files are in the /src folder of the 'backend' repository?"
- "Get the content of the README.md file from the 'frontend' repository"
- "Search for all .cs files in the 'api' repository"
- "Show me the content of /src/Program.cs from the 'main' branch"
Pull Requests
- "Show me all active pull requests in the 'my-repo' repository"
- "Get details of pull request #123"
- "What comments are on PR #456?"
- "Search for pull requests related to 'authentication'"
- "Show me PRs targeting the 'main' branch"
- "List PRs created by user@email.com"
Pipelines and Builds
- "List all pipelines in the project"
- "Show me the recent builds for pipeline 'CI-Build'"
- "What's the status of build #789?"
- "Show me failed builds from the last week"
- "Get the logs for build #456"
- "Show me the timeline of build #123"
- "What builds are currently in progress?"
Troubleshooting
Common Issues
Health check returns error or connection refused
-
Verify the server is running:
# Docker docker compose ps # Check if port is in use netstat -an | grep 8080 # or 5000 -
Check logs for errors:
# Docker docker compose logs # .NET CLI - errors appear in terminal
Authentication failed / 401 Unauthorized
- Verify your PAT is correct in
appsettings.json - Check PAT hasn't expired in Azure DevOps
- Ensure PAT has required scopes (Work Items, Code, Build)
- Verify the organization URL is correct (no trailing slash)
Project not found
- Verify
AZURE_DEVOPS_DEFAULT_PROJECTmatches exact project name - Or pass the project name explicitly in your queries
- Check PAT has access to the project
Docker: Container exits immediately
- Check if
appsettings.jsonhas the required Azure DevOps configuration - View logs:
docker compose logs - Ensure ports 8080 is not in use by another application
.NET CLI: dotnet run fails
- Verify .NET 10 SDK is installed:
dotnet --version - Restore packages:
dotnet restore - Check if
appsettings.jsonhas the correct Azure DevOps settings
Project Structure
mcp-azure-devops/
├── src/
│ └── Viamus.Azure.Devops.Mcp.Server/
│ ├── Configuration/ # App configuration classes
│ ├── Models/ # DTOs and data models
│ ├── Services/ # Azure DevOps SDK integration
│ ├── Tools/ # MCP tool implementations
│ ├── Program.cs # Entry point
│ ├── appsettings.json # App settings
│ └── Dockerfile # Container definition
├── tests/
│ └── Viamus.Azure.Devops.Mcp.Server.Tests/
│ ├── Models/ # DTO tests
│ └── Tools/ # Tool behavior tests
├── .github/ # GitHub templates
├── .env.example # Environment template (Docker)
├── docker-compose.yml # Docker orchestration
├── CONTRIBUTING.md # Contributor guide
├── CODE_OF_CONDUCT.md # Community guidelines
├── SECURITY.md # Security policy
└── LICENSE # MIT License
API Reference
Work Item DTOs
WorkItemDto
Complete work item details including all standard fields and custom fields.
WorkItemSummaryDto
Lightweight representation with essential fields (Id, Title, Type, State, Priority) for list views.
WorkItemCommentDto
Represents a comment on a work item with author and timestamp.
Git DTOs
RepositoryDto
Repository details including Id, Name, DefaultBranch, URLs, Size, and project information.
BranchDto
Branch information including Name, ObjectId (commit), and creator details.
GitItemDto
Represents a file or folder in a repository with Path, ObjectId, GitObjectType, and IsFolder flag.
GitFileContentDto
File content with Path, Content (text), IsBinary flag, Encoding, and Size.
Pull Request DTOs
PullRequestDto
Complete pull request details including:
- PullRequestId, Title, Description
- SourceBranch, TargetBranch
- Status (Active, Abandoned, Completed)
- CreatedBy, CreationDate, ClosedDate
- Reviewers list, MergeStatus, IsDraft
- Repository and Project information
PullRequestReviewerDto
Reviewer information including DisplayName, Vote (-10 to 10), IsRequired, and HasDeclined status.
PullRequestThreadDto
Comment thread with Id, Status (Active, Fixed, etc.), FilePath, LineNumber, and Comments list.
PullRequestCommentDto
Individual comment with Id, Content, Author, timestamps, and CommentType.
Pipeline/Build DTOs
PipelineDto
Pipeline (build definition) details including Id, Name, Folder, ConfigurationType, and QueueStatus.
BuildDto
Comprehensive build information including:
- Id, BuildNumber, Status, Result
- SourceBranch, SourceVersion
- RequestedBy, RequestedFor
- QueueTime, StartTime, FinishTime
- Definition details, LogsUrl, Reason, Priority
BuildLogDto
Build log metadata with Id, Type, Url, LineCount, and timestamps.
BuildTimelineRecordDto
Timeline record (stage, job, or task) with Id, ParentId, Type, Name, State, Result, timing information, and error/warning counts.
Development
Running Tests
# Run all tests
dotnet test
# Run specific test class
dotnet test --filter "FullyQualifiedName~WorkItemToolsTests"
# Run with coverage
dotnet test --collect:"XPlat Code Coverage"
Building
# Debug build
dotnet build
# Release build
dotnet build -c Release
Contributing
We welcome contributions! Please see CONTRIBUTING.md for:
- Development setup
- Coding standards
- How to add new MCP tools
- Pull request guidelines
License
This project is licensed under the MIT License.