azure-devops-mcp
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
Runs with mockssource: GitHubTypeScriptMITcommit 52072ff41bb8
TypeScript, MIT licensed.
azure-devops-mcp runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Project builds and all 1349 tests pass with Node.js v20.20.2. The MCP server binary reports version 2.10.0 and responds to --help with all options (organization, domains, authentication, tenant). The dist/ directory contains compiled JS output.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18 is too old (project requires >=20), causing engine warnings and preventing optional dependency @azure/msal-node-extensions from resolving3 minutes
- Install time
- 3 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test exited 0, 1349 passed across 21 suites; node dist/index.js --version returned 2.10.0; node dist/index.js --help printed usage
- Model tokens used
- 47,688
- Exact commit tested
- 52072ff41bb8
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Tests: 1349 passed, 1349 total Time: 2.165 s, estimated 4 s === Dist files === auth.js index.js logger.js oauth.js org-tenants.js All verified. Here's the final result: tokens used 47,688 All verified. Here's the final result:
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 3 minutes, faster than the median of the 26 comparable projects Argusic has measured.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 27 TypeScript projects Argusic has installed and timed, azure-devops-mcp was the 10th fastest to reach a running state, and 20 of 27 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.03 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/azure-devops-mcp)Questions
- Does azure-devops-mcp run?
- azure-devops-mcp runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test azure-devops-mcp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 52072ff41bb8. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test azure-devops-mcp?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does azure-devops-mcp take to install?
- 3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does azure-devops-mcp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing azure-devops-mcp?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does azure-devops-mcp compare with the alternatives?
- Of the 27 TypeScript projects Argusic has installed and timed, azure-devops-mcp was the 10th fastest to reach a running state, and 20 of 27 reached one at all.
- Where is the evidence for azure-devops-mcp?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.