Azure DevOps MCP server

This Azure DevOps MCP server provides a standardized way for AI assistants to interact with Azure DevOps resources through the Model Context Protocol (MCP). It acts as a bridge between AI models and Azure DevOps APIs, enabling you to manage projects, work items, repositories, and more using natural language.

Installation

Prerequisites

• Node.js (v16+)
• npm or yarn
• Azure DevOps account with appropriate access
• Authentication credentials (Personal Access Token or Azure Identity)

Setting Up with Claude Desktop/Cursor AI

To integrate with Claude Desktop or Cursor AI, add one of the following configurations to your configuration file.

Using Azure Identity Authentication

First, login to Azure CLI:

az login

Then add this configuration:

{
  "mcpServers": {
    "azureDevOps": {
      "command": "npx",
      "args": ["-y", "@tiberriver256/mcp-server-azure-devops"],
      "env": {
        "AZURE_DEVOPS_ORG_URL": "https://dev.azure.com/your-organization",
        "AZURE_DEVOPS_AUTH_METHOD": "azure-identity",
        "AZURE_DEVOPS_DEFAULT_PROJECT": "your-project-name"
      }
    }
  }
}

Using Personal Access Token (PAT) Authentication

{
  "mcpServers": {
    "azureDevOps": {
      "command": "npx",
      "args": ["-y", "@tiberriver256/mcp-server-azure-devops"],
      "env": {
        "AZURE_DEVOPS_ORG_URL": "https://dev.azure.com/your-organization",
        "AZURE_DEVOPS_AUTH_METHOD": "pat",
        "AZURE_DEVOPS_PAT": "<YOUR_PAT>",
        "AZURE_DEVOPS_DEFAULT_PROJECT": "your-project-name"
      }
    }
  }
}

Authentication Options

The server supports multiple authentication methods for connecting to Azure DevOps APIs:

1. Personal Access Token (PAT) - Simple token-based authentication
2. Azure Identity (DefaultAzureCredential) - Authentication using the Azure Identity SDK
3. Azure CLI - Authentication using your Azure CLI login

Configuration Variables

Key environment variables for configuration:

Available Tools

The MCP server provides numerous tools to interact with Azure DevOps resources:

User Management

• get_me: Get details of the authenticated user

Organization Management

• list_organizations: List all accessible organizations

Project Management

• list_projects: List all projects in an organization
• get_project: Get details of a specific project
• get_project_details: Get comprehensive project details

Repository Management

• list_repositories: List all repositories in a project
• get_repository: Get details of a specific repository
• get_repository_details: Get detailed repository information
• get_file_content: Get content of a file or directory

Work Item Management

• get_work_item: Retrieve a work item by ID
• create_work_item: Create a new work item
• update_work_item: Update an existing work item
• list_work_items: List work items in a project
• manage_work_item_link: Add, remove, or update work item links

Search Functionality

• search_code: Search for code across repositories
• search_wiki: Search for content across wiki pages
• search_work_items: Search for work items across projects

Pipeline Management

• list_pipelines: List pipelines in a project
• get_pipeline: Get details of a specific pipeline
• trigger_pipeline: Trigger a pipeline run with parameters

Wiki Management

• get_wikis: List all wikis in a project
• get_wiki_page: Get content of a specific wiki page

Pull Request Management

• create_pull_request: Create a new pull request
• list_pull_requests: List pull requests in a repository
• add_pull_request_comment: Add a comment to a pull request
• get_pull_request_comments: Get comments from a pull request
• update_pull_request: Update an existing pull request

Troubleshooting

Common authentication issues include:

• Invalid or expired credentials
• Insufficient permissions
• Network connectivity problems
• Configuration errors

Adjust the LOG_LEVEL environment variable to "debug" for more detailed logging information.

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.