ado-mcp

A Model Context Protocol (MCP) server, written in Go, that exposes the Azure DevOps REST API (plus 7pace Timetracker) as tools an LLM client (Claude Desktop/Code, Cursor, and others) can call.

It aims for broad coverage of Azure DevOps: 274 tools across 34 toolsets, plus 7 workflow prompts (surfaced as slash commands by MCP clients), spanning projects, work items, Git/pull requests, pipelines, releases, test plans, boards, artifacts, wiki, graph/identity, security, service hooks, dashboards, audit, distributed task (variable groups/environments/agent pools/deployment groups), service connections, branch policies, code/work-item/wiki search, process customization, member entitlement, notifications, extensions, TFVC, advanced security alerts, approvals and checks, identities, operations, profile, composite macros, statistics/surveys, favorites, delivery plans, a local notes store, and 7pace time tracking.

A built-in workflow: keep engineering notes (stored locally in SQLite under your config directory) tagged by project/env/service/version/repo/branch/users, with a real time range, free-text search, and discoverable dimension values. Notes can optionally sync with 7pace. See the notes toolset and the new_note prompt.

Features

• Typed tools with schemas: every tool has an auto-generated JSON Schema for its input and output, inferred from Go structs, with per-field descriptions. Inputs are validated before a handler runs.
• Read-only switch: ADO_READONLY=true hides every mutating tool, so the server can be safely pointed at production.
• Toolset filtering: enable only the areas you need with ADO_TOOLSETS to keep the tool list focused.
• Multi-host aware: transparently routes to the Azure DevOps service hosts (dev.azure.com, vssps, vsrm, feeds, auditservice, almsearch, vsaex, extmgmt, advsec).
• Built on the official SDK: uses modelcontextprotocol/go-sdk (v1).
• Response caching: GET responses are cached in memory for a short TTL (ADO_CACHE_TTL, default 30s) and any write instantly invalidates the cache, so repeated reads within a task are fast without risking stale data after a mutation.

Documentation map

Each page goes one level deeper than the last:

1. Install — get the ado binary onto your machine.
2. Configuration — environment variables and MCP client setup.
3. CLI — the ado mcp / ado test / ado note command tree.
4. Toolsets — the 34 toolsets and what each covers, for picking an ADO_TOOLSETS subset.
5. Tools — every individual tool, grouped by toolset, with its full description.
6. Prompts — the built-in slash-command workflows and composite macro tools.
7. Architecture — how the server is put together internally.
8. Development — building, testing, linting, and smoke-testing the protocol.

New to the project? Start at Install and follow the numbers down. Looking for one specific tool? Jump straight to Tools — every page stands on its own.

This site is open source. Improve this page.