Azure DevOps

Provides native Azure DevOps actions via MCP for Cursor, enabling natural language control of work items, PRs, builds, releases, and more.
  • typescript

0

GitHub Stars

typescript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "erealexandru-azure-devops-mcp-server-for-cursor": {
      "command": "node",
      "args": [
        "C:/PATH/TO/YOUR/ADOMCPLocalServer/dist/index.js"
      ],
      "env": {
        "AZURE_DEVOPS_ORG": "YOUR_ORG_NAME",
        "AZURE_DEVOPS_PAT": "YOUR_TOKEN"
      }
    }
  }
}

You can control Azure DevOps from Cursor using an MCP server that translates natural language into Azure DevOps actions. This makes it easy to manage work items, PRs, builds, releases, and more without memorizing commands—you just chat and command naturally.

How to use

Interact with the MCP server from Cursor by opening a chat and typing your request in plain English. You can ask it to show work items, create a bug for an issue, review pull requests, run builds, and manage sprints. The server handles the translation to Azure DevOps actions and returns results directly in the chat.

How to install

Prerequisites: you need Node.js installed on your computer to run the MCP server locally.

Step 1: Clone the project inside Cursor

# In Cursor, clone the project into your workspace
# Step 1
# (This is the command shown conceptually as part of the setup)

Step 2: Install dependencies and build the project

npm install
npm run build

Step 3: Prepare your Azure DevOps token

  • Create a personal access token in Azure DevOps with the necessary scopes.
  • Save the token securely; you will use it in the .env file.

Step 4: Create the environment file in the project root

AZURE_DEVOPS_ORG=your-organization-name
AZURE_DEVOPS_PAT=your-token-from-step-3

Step 5: Connect the MCP server to Cursor

  • In Cursor, add a new MCP server with this configuration (adjust the path to your system):
{
  "mcpServers": {
    "azure_devops": {
      "command": "node",
      "args": ["C:/PATH/TO/YOUR/ADOMCPLocalServer/dist/index.js"]
    }
  }
}

How to install

Step 6: Restart Cursor to apply changes and verify the connection.

Additional setup and testing

After restarting, verify the server shows a connected status in Cursor's Tools & Integration section. Then test by asking for a simple action, such as listing Azure DevOps projects.

Test example in Cursor terminal:

node test-connection.js

Available tools

list_projects

List Azure DevOps projects accessible with your token.

list_work_items

Show work items for a given project or query.

create_work_item_bug

Create a bug work item with a provided title and description.

show_prs_review

Show pull requests that are awaiting your review.

run_build

Trigger or view the status of CI builds.

release_deploy

Deploy a release to a specified environment.

sprint_progress

Show progress and burn-down/status of a sprint.

check_release_readiness

Check readiness for a release, including status of related items.

test_management_status

Show test plans, suites, and results.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational