Overview
devops-mcp exposes Azure DevOps work items to your coding agent as MCP tools — twelve of them:
eight reads for context, four writes for delivery updates.
It is opt-in per project. Answer yes to the Azure DevOps question during
/setup and the server
entry is written into your client config. Projects that don’t opt in see none of these tools.
What it is not
Section titled “What it is not”It holds no Azure DevOps credentials and is not scoped to any one client:
- Your PAT, per request. The token arrives on
x-devops-patand lives in memory for the life of the request. It is never written to storage or to the audit log, so writes carry your name in the work item history rather than a shared service identity. - Your organisation and project, per request.
x-devops-organdx-devops-projectare required. There are no defaults — a missing value is reported as a configuration error, never guessed at.
Relationship to Dev MCP
Section titled “Relationship to Dev MCP”Independent servers. devops-mcp shares no code with
dev-mcp and versions on its own line. It reuses the
same DC_MCP_API_KEY, so one key works across both, and /setup writes its config entry for you.
Start with Setup.