Skip to directory

Azure DevOps MCP

Microsoft (Azure DevOps)

Streamable HTTP (remote); stdio (local)12+ documented tools19

About Azure DevOps MCP

Microsoft's Azure DevOps MCP server gives compatible AI clients access to organization projects, work items, repositories, pull requests, pipelines, test plans, and wikis through hosted or local server modes.

What you can use it for

  • Query work items, iterations, teams, and saved queries
  • Review pull requests and repository/wikis context
  • Inspect pipelines, builds, tests, and releases
  • Prepare standups, sprint plans, or work-item risk summaries grounded in organization data
Connection and setup
Hosting
Remote hosted or local
Transport
Streamable HTTP (remote); stdio (local)
Endpoint
https://mcp.dev.azure.com/{organization}
Authentication
Remote server uses Microsoft Entra OAuth; personal access tokens are not supported remotely. Local server has distinct setup/auth options documented for clients.

Requirements

  • Azure DevOps Services organization with appropriate user/project permissions
  • Remote server requires organization backed by a Microsoft Entra tenant; standalone MSA organizations are unsupported
  • Agent-mode client for tool access
  • Local mode requires Node.js 20+

Setup steps

  1. Prefer remote when the MCP client supports the required Entra OAuth flow; add https://mcp.dev.azure.com/<organization> as a remote HTTP server.
  2. Authenticate through Microsoft Entra in the browser; ensure the signed-in user has access to the Azure DevOps organization and project.
  3. If client OAuth compatibility prevents remote sign-in, consult Microsoft's local-server guide for that client; do not reuse remote configuration for local mode.
  4. Optionally narrow capabilities with X-MCP-Toolsets/X-MCP-Tools and use X-MCP-Readonly where supported.
  5. Verify with a read-only request such as listing projects or fetching a work item.
Tools 12+

Stored rows show representative namespaces and capabilities, not a complete exact tool list. Local/remote variants and enabled Azure DevOps areas, organization context, and permissions affect the exposed catalog.

  • core_list_orgs
    01
  • core_list_projects
    02
  • core_list_project_teams
    03
  • work
    04
  • wit_work_item
    05
  • wit_query
    06
  • wit_query_by_wiql
    07
  • repo
    08
  • pull_request
    09
  • pipeline
    10
  • testplan
    11
  • wiki
    12

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Limitations and notes
  • Remote server requires Microsoft Entra-backed organization; standalone Microsoft accounts are unsupported.
  • Some MCP clients (including Claude Desktop, Claude Code, Cursor, and Codex per overview) may need local server mode because their current remote OAuth flow is incompatible.
  • The organization-specific endpoint is needed especially for guest users; omitting org requires supplying org context in each call.
  • Toolsets restrict exposed tools but do not grant permissions; access remains bounded by signed-in user's Azure DevOps permissions.
  • Mutating tools should require user review; agent mode is required.
Original sources
  • official tool reference

    Microsoft documents local and hosted Azure DevOps MCP variants. Exposed tools depend on server variant, enabled namespaces, organization access, and permissions; the stored namespace examples are not a complete exact tool roster.

  • official documentation

    Microsoft documents local and hosted Azure DevOps MCP variants. Exposed tools depend on server variant, enabled namespaces, organization access, and permissions; the stored namespace examples are not a complete exact tool roster.

Documentation checked 2026-10-28T13:02:00.000Z. Connection has not been runtime tested.

Similar tools