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, Pipelines, and Wikis over HTTP or local STDIO.

Note: Flow metrics, WIP analysis, and other analytics features were removed. With ActivatedDate and ClosedDate now exposed on all work item queries, Claude can derive cycle time, lead time, aging, and throughput directly from the data — no pre-built analytics tools needed.

---

For local process setup, multi-organization configuration, PAT replacement, and error recovery, see the STDIO and error handling guide.

Quick Start (HTTP)

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

Option A — .env file (recommended for Docker):

cp .env.example .env
# Edit .env with your Azure DevOps credentials

Option B — appsettings.json (for .NET CLI):

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"
  }
}

For multiple Azure DevOps organizations or PATs, keep one entry per organization and select it in tool calls with the optional organization argument:

{
  "AzureDevOps": {
    "DefaultOrganization": "primary",
    "Organizations": [
      {
        "Name": "primary",
        "OrganizationUrl": "https://dev.azure.com/primary-org",
        "PersonalAccessToken": "primary-pat",
        "DefaultProject": "primary-project"
      },
      {
        "Name": "secondary",
        "OrganizationUrl": "https://dev.azure.com/secondary-org",
        "PersonalAccessToken": "secondary-pat",
        "DefaultProject": "secondary-project"
      }
    ]
  }
}

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 (use reverse proxy for HTTPS in production)

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 receive a JSON response with status: "healthy" and a timestamp. This checks the HTTP host; call an Azure DevOps read tool to validate PAT access.

---

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" `
    -ApiKey "your-secure-api-key"  # Optional: enables API key authentication

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 (HTTPS transport)

For multiple organizations/PATs, run the installer for the primary organization, then add AzureDevOps:Organizations entries to appsettings.json or use the Docker environment variables from .env.example.

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

Both hosts expose the same 49 tools. All tools accept an optional organization selector; see Multiple Organizations / PATs.

Work Item Tools

Tool	Description
get_work_item	Gets details of a specific work item by ID (supports optional includeRelations parameter)
get_work_item_history	Gets activity and state/column transition history, including authors, timestamps, and durations
get_work_items_history	Gets activity and state/column transition history for multiple work item IDs
get_work_items	Gets multiple work items by IDs (batch retrieval, supports optional includeRelations parameter)
get_work_item_relations	Gets the normalized list of relationships (Parent, Child, Related, Predecessor, Successor, Tests, Tested By, Hyperlink, Attachment) associated with a work item
get_work_item_tree	Recursively gets parent and child work items starting from a root work item, up to a specified depth limit. Includes cycle detection
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
get_work_item_comments	Reads comments (discussion history) of a work item, with pagination, sort order, and optional rendered HTML
get_work_item_attachments	Lists file attachments associated with a work item
get_work_item_attachment_content	Downloads an attachment as text or Base64, subject to a byte limit
create_work_item	Creates a new work item (Bug, Task, User Story, etc.) with support for all standard fields, parent linking, and custom fields
update_work_item	Updates an existing work item. Only specified fields are changed; omitted fields remain unchanged
link_work_items	Links an existing work item to parent, child, predecessor, successor, or related work items

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 within a repository
get_pull_request_by_id	Gets details of a pull request by ID only, searching across all repositories in the project
get_pull_request_threads	Gets comment threads for a pull request
create_pull_request_thread	Creates a new comment thread on a pull request, either as a general discussion or inline file comment
add_pull_request_thread_comment	Adds a comment to an existing PR thread, optionally replying to a parent comment
update_pull_request_thread_status	Updates a pull request comment thread status, including close/resolve aliases
search_pull_requests	Searches pull requests by text in title or description
query_pull_requests	Advanced query with multiple combined filters
create_pull_request	Creates a new pull request with title, description, source/target branches, draft flag, reviewers, and linked work items
update_pull_request	Updates an existing pull request title, description, target branch, status, or draft flag

Wiki Tools

Tool	Description
get_wikis	Lists project and code wikis in a project
get_wiki	Gets Wiki metadata by name or ID
get_wiki_page	Gets a page by path, optionally including Markdown content and selecting a version
get_wiki_page_tree	Gets a page hierarchy with one-level or full recursion

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)

1. Go to your Azure DevOps organization: https://dev.azure.com/{your-org}
2. Click on User Settings (gear icon) > Personal Access Tokens
3. Click + New Token
4. Configure:
   • Name: MCP Server (or any name you prefer)
   • Expiration: Choose based on your needs
   • Scopes: Select the following permissions:

Scope	Permission	Required for
Work Items	Read & Write	Get, query, create, update work items and add comments
Code	Read & Write	Git repositories, branches, files, and pull requests (Write required to create PRs)
Build	Read	Pipelines and builds
Wiki	Read (vso.wiki)	Wiki metadata and pages; see the Wiki API scope reference

1. Click Create and copy the token immediately (you won't see it again!)

Multiple Organizations / PATs

The server supports one PAT per configured Azure DevOps organization. Existing single-organization settings still work:

• AzureDevOps:OrganizationUrl
• AzureDevOps:PersonalAccessToken
• AzureDevOps:DefaultProject

For multiple PATs, configure AzureDevOps:Organizations with Name, OrganizationUrl, PersonalAccessToken, and optional DefaultProject. Set AzureDevOps:DefaultOrganization to choose the fallback organization. Tool calls can pass organization as the configured Name, the full organization URL, or the organization slug from https://dev.azure.com/{slug}.

---

Running Options

Option 1: Docker Compose (Recommended)

Best for: Production use, quick setup without .NET installed

1. Create your .env file from the template:

   cp .env.example .env
   # Edit .env with your Azure DevOps credentials
   

   For multiple organizations/PATs, fill AZURE_DEVOPS_ORGANIZATION_0_*, AZURE_DEVOPS_ORGANIZATION_1_*, and AZURE_DEVOPS_DEFAULT_ORGANIZATION in .env.

2. Start the server:

   docker compose up -d
   

Server URL: http://localhost:8080 (internal)

Important: For production, use a reverse proxy (nginx, traefik, or a cloud load balancer) in front of the container to provide HTTPS/TLS termination.

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

HTTPS Support: The server can also run with HTTPS on port 5001, but this may cause certificate validation issues with some MCP clients (e.g., Claude Code). If you need HTTPS locally, configure the development certificate properly:

# Trust the development certificate (first time only)
dotnet dev-certs https --trust

# Run with HTTPS
dotnet run --project src/Viamus.Azure.Devops.Mcp.Server --urls "https://localhost:5001"

For production environments, use a reverse proxy with properly configured TLS certificates instead.

Option 3: Self-Contained Executable

Best for: Deployment without .NET runtime

# Windows
dotnet publish src/Viamus.Azure.Devops.Mcp.Server -c Release --self-contained true -r win-x64 -o ./publish/win-x64

# Linux
dotnet publish src/Viamus.Azure.Devops.Mcp.Server -c Release --self-contained true -r linux-x64 -o ./publish/linux-x64

# macOS (Intel)
dotnet publish src/Viamus.Azure.Devops.Mcp.Server -c Release --self-contained true -r osx-x64 -o ./publish/osx-x64

# macOS (Apple Silicon)
dotnet publish src/Viamus.Azure.Devops.Mcp.Server -c Release --self-contained true -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

Note: For production, use a reverse proxy (nginx, traefik) or Application Gateway to handle TLS termination with your own certificates.

---

Option 4: .NET STDIO

Best for: MCP clients that launch a local process and communicate over stdin/stdout.

The STDIO host uses the same tools, organization/PAT configuration, and error handling as the HTTP server. It does not open a listening port. Build a framework-dependent distribution with the .NET 10 SDK:

dotnet publish src/Viamus.Azure.Devops.Mcp.Stdio -c Release --self-contained false -o ./publish/stdio

Then configure your MCP client's process command. Use an absolute path to the published DLL:

{
  "mcpServers": {
    "azure-devops": {
      "command": "dotnet",
      "args": ["C:/path/to/mcp-azure-devops/publish/stdio/Viamus.Azure.Devops.Mcp.Stdio.dll"],
      "env": {
        "AzureDevOps__OrganizationUrl": "https://dev.azure.com/your-organization",
        "AzureDevOps__PersonalAccessToken": "your-pat",
        "AzureDevOps__DefaultProject": "your-project"
      }
    }
  }
}

Configuration is loaded from appsettings.json beside the executable, with environment variables and command-line settings taking precedence. The client's working directory can be different. Multi-organization settings use the same keys as HTTP, for example AzureDevOps__Organizations__0__Name and AzureDevOps__Organizations__0__PersonalAccessToken. A .env file is not loaded automatically by the .NET hosts; inject those values through the client or its environment.

All runtime logs go to stderr; stdout is reserved for MCP JSON-RPC messages. Publish/build separately before connecting a client so build output cannot enter the protocol stream. Missing or invalid configuration produces a sanitized startup message on stderr and a nonzero exit code. A stale PAT does not prevent initialization or tool discovery; authentication is attempted when a tool needs Azure DevOps.

For a standalone executable that includes the .NET runtime:

dotnet publish src/Viamus.Azure.Devops.Mcp.Stdio -c Release -r win-x64 --self-contained true -o ./publish/stdio-win-x64

Set the client's command to the absolute path of Viamus.Azure.Devops.Mcp.Stdio.exe and omit args.

---

Security

API Key Authentication (HTTP only)

The HTTP server supports optional API key authentication to protect your MCP endpoints. STDIO relies on access to the local process and its private configuration; it does not use ServerSecurity settings. Both hosts separately use PATs to authenticate to Azure DevOps.

Configuration

Add to appsettings.json:

{
  "ServerSecurity": {
    "ApiKey": "your-secret-api-key",
    "RequireApiKey": true
  }
}

Or via environment variables:

# .NET CLI
ServerSecurity__ApiKey=your-secret-key ServerSecurity__RequireApiKey=true dotnet run --project src/Viamus.Azure.Devops.Mcp.Server

# Docker — configure in .env file (see .env.example)
docker compose up -d

For Docker, add to your .env file (see .env.example for the full template):

MCP_API_KEY=your-secret-api-key
MCP_REQUIRE_API_KEY=true

How It Works

• When RequireApiKey is false (default): No authentication required
• When RequireApiKey is true: All requests (except /health) require a valid API key
• The /health endpoint is always accessible without authentication

Providing the API Key

Clients can provide the API key through either header. If both are present, X-API-Key takes precedence.

Option 1 - X-API-Key Header (recommended):

curl -H "X-API-Key: your-secret-key" https://localhost:5001

Option 2 - Authorization: Bearer Header:

curl -H "Authorization: Bearer your-secret-key" https://localhost:5001

Use the configured HTTP/HTTPS URL for your host. These headers contain the MCP API key, not the Azure DevOps PAT.

Generating a Secure API Key

# Using OpenSSL
openssl rand -base64 32

# Using PowerShell
[Convert]::ToBase64String([Security.Cryptography.RandomNumberGenerator]::GetBytes(32))

---

Client Configuration

Claude Code

Without API Key authentication:

claude mcp add azure-devops --transport http http://localhost:5000

With API Key authentication:

claude mcp add azure-devops --transport http http://localhost:5000 --header "X-API-Key: your-secret-api-key"

Note: Use port 5000 (HTTP) if running with .NET CLI, or 8080 (HTTP) if running with Docker locally. For production deployments, configure a reverse proxy with HTTPS.

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"
• "Create a new Bug in project X titled 'Login page crashes on submit'"
• "Create a User Story assigned to John with priority 2 under parent #100"
• "Update work item #1234 to change state to 'Resolved' and assign to Jane"
• "Set the iteration path of work item #567 to 'Project\Sprint 3'"
• "Link user story #567 to predecessor #123 and parent #100"

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"
• "Find pull request #456 anywhere in the project"
• "What comments are on PR #456?"
• "Create a new comment thread on PR #456 saying 'Please review the validation logic'"
• "Add an inline PR comment on /src/App.cs line 42"
• "Search for pull requests related to 'authentication'"
• "Show me PRs targeting the 'main' branch"
• "List PRs created by user@email.com"
• "Create a pull request from 'feature/login' to 'main' titled 'Add login page'"
• "Open a draft PR from my branch to main with a description of the changes"
• "Create a PR and link it to work items #123 and #456"
• "Update PR #456 to change the title and mark it ready for review"
• "Abandon PR #456 in the 'my-repo' repository"

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

Tool error responses

See the operational guide for PAT replacement steps, STDIO diagnostics, and retry guidance. Both transports report failed tool execution with MCP isError: true. Azure DevOps exceptions produce a JSON text content block with stable fields:

{
  "error": "Azure DevOps authentication failed. The PAT may be expired, revoked, or invalid. Replace the PAT for the selected organization, check access, and restart the host if configuration changed.",
  "errorCode": "AZURE_DEVOPS_AUTHENTICATION_FAILED",
  "retryable": false,
  "httpStatusCode": 401
}

Error code	Meaning / action
AZURE_DEVOPS_AUTHENTICATION_FAILED	Check or replace the selected organization's PAT, then restart the process
AZURE_DEVOPS_FORBIDDEN	Check PAT scopes and organization/project permissions
AZURE_DEVOPS_NOT_FOUND	Verify the requested resource, project, and organization
INVALID_ARGUMENT	Correct the tool arguments
AZURE_DEVOPS_CONFLICT	Refresh the resource and resolve conflicting changes
AZURE_DEVOPS_RATE_LIMITED	Wait before attempting another call
AZURE_DEVOPS_UNAVAILABLE	Azure DevOps returned a server error; try again later
AZURE_DEVOPS_API_UNAVAILABLE	Check the organization URL and whether the server supports the required API
AZURE_DEVOPS_TIMEOUT	The operation timed out
AZURE_DEVOPS_NETWORK_ERROR	Check connectivity, organization URL, and proxy settings
CONFIGURATION_ERROR	Correct the organization configuration or selector
UNEXPECTED_ERROR	An unexpected failure occurred; inspect the server's sanitized diagnostic logs

httpStatusCode can be null when no HTTP response was available. retryable identifies transient failures; the server does not automatically repeat tool calls. Client-requested cancellation remains cancellation. Existing validation and missing-resource JSON responses retain their messages, add the error metadata, and now also set MCP isError: true.

A 401 response cannot establish whether a PAT expired, was revoked, or is invalid. The message lists those possibilities rather than asserting expiration; see Microsoft's PAT guidance. Raw exception messages, credentials, and stack traces are excluded from the new error responses. Wiki lookups return an empty/not-found result only when the requested resource returns HTTP 404. API discovery, authentication, and connectivity failures reach the error handler.

Common Issues

1. Verify the server is running:

   # Docker
   docker compose ps
   
   # Check if port is in use
   netstat -an | grep 8080  # Docker
   netstat -an | grep 5000  # .NET CLI
   

2. Check logs for errors:

   # Docker
   docker compose logs
   
   # .NET CLI - errors appear in terminal
   

1. Verify your PAT is correct in appsettings.json
2. Check PAT hasn't expired in Azure DevOps
3. Ensure PAT has required scopes (Work Items, Code, Build)
4. Verify the organization URL is correct (no trailing slash)
5. If using multiple organizations, verify the tool call's organization value matches a configured Name, URL, or Azure DevOps organization slug

If API key authentication is enabled (RequireApiKey: true):

1. Verify the API key is correctly set in your client configuration
2. Check the X-API-Key header is being sent with requests
3. Ensure the API key matches exactly (case-sensitive)
4. The /health endpoint should still work without authentication

# Test health endpoint (should work without API key)
curl http://localhost:5000/health

# Test with API key
curl -H "X-API-Key: your-key" http://localhost:5000

1. Verify AZURE_DEVOPS_DEFAULT_PROJECT matches exact project name
2. Or pass the project name explicitly in your queries
3. Check the selected organization's PAT has access to the project

1. Check if appsettings.json has the required Azure DevOps configuration
2. View logs: docker compose logs
3. Ensure port 8080 is not in use by another application

1. Verify .NET 10 SDK is installed: dotnet --version
2. Restore packages: dotnet restore
3. Check if appsettings.json has the correct Azure DevOps settings

---

Project Structure

mcp-azure-devops/
├── src/
│   ├── Viamus.Azure.Devops.Mcp.Core/
│   │   ├── Configuration/      # Shared Azure DevOps options and safe validation
│   │   ├── Errors/             # Error classification and MCP tool error handling
│   │   ├── Models/             # Shared DTOs
│   │   ├── Services/           # Azure DevOps SDK integration
│   │   └── Tools/              # Work Items, Git, PRs, builds, Wiki
│   ├── Viamus.Azure.Devops.Mcp.Server/
│   │   ├── Configuration/      # HTTP security options
│   │   ├── Middleware/         # API key authentication
│   │   ├── Program.cs          # HTTP entry point
│   │   ├── appsettings.json
│   │   └── Dockerfile
│   └── Viamus.Azure.Devops.Mcp.Stdio/
│       ├── Program.cs          # STDIO entry point
│       ├── StdioHost.cs         # Host setup, executable-relative config, stderr logs
│       └── appsettings.json
├── tests/
│   ├── Viamus.Azure.Devops.Mcp.Server.Tests/
│   │   ├── Configuration/
│   │   ├── Errors/
│   │   ├── Middleware/
│   │   ├── Models/
│   │   ├── Services/
│   │   ├── Tools/
│   │   └── Transport/          # Local HTTP/STDIO protocol integration tests
│   └── Viamus.Azure.Devops.Mcp.Stdio.Tests/
│       ├── StdioHostTests.cs
│       └── StdioProtocolTests.cs
├── docs/stdio-and-error-handling.md
├── .github/
├── .env.example
├── docker-compose.yml
├── install-mcp-azure-devops.ps1
├── CONTRIBUTING.md
├── CODE_OF_CONDUCT.md
├── SECURITY.md
└── 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, EndLineNumber, 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.

---

Links

• Model Context Protocol
• Azure DevOps REST API
• Report an Issue