Azure DevOps MCP server

This MCP server facilitates integration between Cline and Azure DevOps, allowing you to manage work items, boards, pipelines, pull requests, wikis, and projects directly from the Cline interface.

Prerequisites

• Node.js (v20 LTS or higher)
• npm (comes with Node.js)
• A Cline installation
• Azure DevOps account with access tokens

Installation

Installing via Smithery

To install Azure DevOps Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @stefanskiasan/azure-devops-mcp-server --client claude

Manual Installation

1. Clone the repository:

git clone https://github.com/stefanskiasan/azure-devops-mcp-server.git
cd azure-devops-mcp-server

2. Install dependencies:

npm install

3. Build the server:

npm run build

Note: You must run the build command after cloning the repository, as the build output isn't included in version control.

Configuration

Getting an Azure DevOps Personal Access Token (PAT)

1. Go to Azure DevOps and sign in
2. Click on your profile picture in the top right
3. Select "Security"
4. Click "New Token"
5. Give your token a name and select these required scopes:
   • Code (read, write) - For Pull Request operations
   • Work Items (read, write) - For Work Item management
   • Build (read, execute) - For Pipeline operations
   • Wiki (read, write) - For Wiki operations
   • Project and Team (read) - For Project and Board information
6. Copy the generated token

Configuring Cline MCP Settings

Add the server configuration to your Cline MCP settings file:

• For VSCode extension: %APPDATA%/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json
• For Claude desktop app: %LOCALAPPDATA%/Claude/claude_desktop_config.json

Add the following configuration to the mcpServers object:

{
  "mcpServers": {
    "azure-devops": {
      "command": "node",
      "args": ["/absolute/path/to/azure-devops-server/build/index.js"],
      "env": {
        "AZURE_DEVOPS_ORG": "your-organization",
        "AZURE_DEVOPS_PAT": "your-personal-access-token",
        "AZURE_DEVOPS_PROJECT": "your-project-name"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Replace the placeholder values with your actual information:

• /absolute/path/to/azure-devops-server: The absolute path to where you cloned the repository
• your-organization: Your Azure DevOps organization name
• your-project-name: Your Azure DevOps project name
• your-personal-access-token: The PAT you generated earlier

Available Tools

Work Items

• get_work_item: Get a work item by ID
• list_work_items: Query work items using WIQL
• create_work_item: Create a new work item (Bug, Task, User Story)
• update_work_item: Update an existing work item

Boards

• get_boards: Get available boards in the project

Pipelines

• list_pipelines: List all pipelines in the project
• trigger_pipeline: Execute a pipeline

Pull Requests

• list_pull_requests: List pull requests
• create_pull_request: Create a new pull request
• update_pull_request: Update a pull request
• get_pull_request: Get pull request details

Wiki

• get_wikis: List all wikis in the project
• get_wiki_page: Get a wiki page
• create_wiki: Create a new wiki
• update_wiki_page: Create or update a wiki page

Projects

• list_projects: List all projects in the Azure DevOps organization

Verification

After adding the configuration:

1. Restart Cline (or VSCode)
2. The Azure DevOps MCP server should now be listed in Cline's capabilities
3. Verify the installation using the MCP Inspector:

npm run inspector

Troubleshooting

If the server isn't connecting:

• Check that the path in your MCP settings is correct
• Verify your Azure DevOps credentials
• Check the Cline logs for any error messages

If you get authentication errors:

• Verify your PAT hasn't expired
• Ensure the PAT has all necessary scopes
• Double-check the organization and project names

For other issues:

• Run the inspector tool to verify the server is working correctly
• Check the server logs for any error messages

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.