This MCP server exposes a set of Azure DevOps operations through the Model Context Protocol (MCP). It wraps multiple Azure DevOps areas—Boards, Repos, Pipelines, Artifacts, Test Plans, and more—into a uniform MCP endpoint at /mcp, accessible via Server-Sent Events (SSE). AI agents can discover available tools at runtime and invoke them with structured function calls, enabling automation for creating work items, managing PRs, queuing builds, handling artifacts, and other DevOps tasks without bespoke SDK calls.

To use it, run the server (for example with dotnet) and connect your MCP client to the hosted /mcp endpoint. The server hosts multiple tool namespaces under the MCP surface, each corresponding to an Azure DevOps domain (Boards, Repos, Pipelines, Artifacts, Test Plans, Project Settings, and Search). You can discover available tools at runtime and execute operations such as creating a work item, listing pull requests, queuing a build, or querying work item histories. The design aims to provide a stable, high-level interface while delegating the heavy lifting to the underlying Azure DevOps SDKs and REST APIs behind the scenes.

Prerequisites:

• .NET 10 SDK installed on your machine or host environment
• Git
• Access to an Azure DevOps organization (organization URL and PAT)
• Optional: Docker if you prefer containerized runs

Installation steps (manual install):

1. Clone the repository: git clone https://github.com/J Jordiag/azure-devops-mcp-server.git cd azure-devops-mcp-server

2. Restore and build the solution: dotnet restore dotnet build -c Release

3. Run the MCP server directly (example): dotnet path/to/Dotnet.AzureDevOps.Mcp.Server.dll

   Ensure environment variables are set as needed (see mcp_config)

4. Optional: run via Docker

   • Build image (Dockerfile should expose the /mcp endpoint): docker build -t azure-devops-mcp-server:latest .
   • Run container: docker run -e ASPNETCORE_URLS=http://0.0.0.0:5000 -p 5000:5000 azure-devops-mcp-server:latest

Using with NPX or Node is not applicable here since this is a .NET-based MCP server. If you already use a .NET build pipeline, you can integrate the server startup as part of your CI/CD workflow.

Tips and considerations:

• The server focuses on Azure DevOps operations wrapped as MCP tools; ensure your Azure DevOps organization URL and authentication token (PAT) are correctly configured in the environment variables (AZDO_ORG_URL, AZDO_PAT).
• The MCP endpoint is served over SSE at /mcp; your MCP client should support SSE streaming to fetch tool definitions and invoke them.
• This is a preview release; API surfaces may change. Regularly pull updates from the repository to stay aligned with the latest MCP tool definitions.
• If you run behind a proxy or in a restricted network, configure ASPNETCORE_URLS and any necessary HTTP proxy settings.
• For production deployments, consider securing the endpoint (HTTPS), rate limiting, and proper secret management for PATs.