Projects, repositories, code search and commit history are live today; the write-side tools are still marked work in progress in the project's own list. If your toolchain is .NET, the draw is distribution — a dotnet tool install rather than another runtime to keep current.
A C# MCP server for Azure DevOps that talks over stdio and installs as a .NET global tool from NuGet. Seven tools are live: list the projects you can reach, list a project's repositories, read the details of one project or one repository, search code across a project's repositories, and read commits — a list, or one commit in full. Work items, boards, pipelines, pull requests and wiki tools appear in the project's own tool list marked as work in progress, so today the surface is navigation, code search and commit history.
- Every project the account can reach, and the full detail of any one of them
- A project's repositories, and the detail of a single repository
- Code search across all repositories in a project
- Commits for a repository as a list, and any single commit with its author, date and message
- Installation as a dotnet global tool, the same way a .NET shop installs the rest of its tooling
Your Azure DevOps organisation URL and a personal access token, both set in the client's configuration, plus a default project if you would rather not name one every time. The tool itself comes from NuGet, so a .NET install is the only runtime in the loop.
One command plus a key — dotnet tool install --global mcpserver.azuredevops.stdio, then supply credentials