Cursor Azure DevOps MCP Server

Azure DevOps Cursor IDE MCP server plugin

Local serverstdioTypeScript

What is the Cursor Azure DevOps MCP server?

Most developer tooling work still happens through a UI a human drives. Cursor Azure DevOps MCP server moves it into the conversation instead. Azure DevOps Cursor IDE MCP server plugin.

The short version

A Model Context Protocol (MCP) server for integrating Azure DevOps with Cursor IDE. This tool allows Claude AI in Cursor to interact with Azure DevOps, providing access to projects, work items, repositories, and pull requests.

  • Get Azure DevOps projects
  • Retrieve work items by ID
  • Fetch multiple work items
  • List repositories in a project
  • Get pull requests for a repository
  • View pull request details and threads

Getting it running

Installation goes through your MCP client rather than a global install: point it at cursor-azure-devops-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 14 tools. What each one is for:

  • azure_devops_projects — Get all projects
  • azure_devops_work_item — Get a specific work item
  • azure_devops_work_items — Get multiple work items
  • azure_devops_repositories — Get repositories for a project
  • azure_devops_pull_requests — Get pull requests from a repository
  • azure_devops_pull_request_by_id — Get a specific pull request
  • azure_devops_pull_request_threads — Get threads from a pull request
  • azure_devops_work_item_attachments — Get attachments for a work item
  • azure_devops_work_item_comments — Get comments for a work item
  • azure_devops_pull_request_changes — Get detailed PR code changes
  • azure_devops_pull_request_file_content — Get content of a specific file in a pull request
  • azure_devops_branch_file_content — Get file content directly from a branch

What it needs from you

Configuration is passed through the environment: AZURE_DEVOPS_ORG_URL, AZURE_DEVOPS_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Cursor Azure DevOps.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Cursor Azure DevOps's toolset — azure_devops_projects, azure_devops_work_item, azure_devops_work_items and 11 more — is a fair guide to whether it matches your workflow. It is maintained by maximtitovich; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Cursor Azure DevOps's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
azure_devops_projectsGet all projects
azure_devops_work_itemGet a specific work item
azure_devops_work_itemsGet multiple work items
azure_devops_repositoriesGet repositories for a project
azure_devops_pull_requestsGet pull requests from a repository
azure_devops_pull_request_by_idGet a specific pull request
azure_devops_pull_request_threadsGet threads from a pull request
azure_devops_work_item_attachmentsGet attachments for a work item
azure_devops_work_item_commentsGet comments for a work item
azure_devops_pull_request_changesGet detailed PR code changes
azure_devops_pull_request_file_contentGet content of a specific file in a pull request
azure_devops_branch_file_contentGet file content directly from a branch
azure_devops_create_pr_commentCreate a comment on a pull request
azure_devops_test_plansList all test plans for a project

How to install the Cursor Azure DevOps MCP server

{
  "mcpServers": {
    "cursor-azure-devops": {
      "command": "npx",
      "args": ["-y", "cursor-azure-devops-mcp"],
      "env": {
        "AZURE_DEVOPS_ORG_URL": "your-value",
        "AZURE_DEVOPS_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
AZURE_DEVOPS_ORG_URLEndpoint or connection string the server talks to.Yes
AZURE_DEVOPS_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Cursor Azure DevOps to azure devops projects.
  • Use Cursor Azure DevOps to azure devops work item.
  • Use Cursor Azure DevOps to azure devops work items.

Frequently asked questions

It enables Claude AI in Cursor IDE to interact with Azure DevOps, giving it access to projects, work items, repositories, pull requests, and test management data.