Azure DevOps MCP server

Integrates with Azure DevOps to enable work item management, wiki interactions, and sprint tracking for software development teams.
Back to servers
Provider
Krishna Amilineni
Release date
Feb 27, 2025
Language
Go
Stats
1 star

The MCP Azure DevOps Bridge is a specialized integration server that connects with Azure DevOps through the Model Context Protocol (MCP). It enables you to seamlessly manage work items, wiki documentation, sprint planning, and handle attachments and discussions directly from your AI assistant.

Installation

Prerequisites

  • Go 1.23 or later
  • Azure DevOps Personal Access Token (PAT)

Installing Go

Windows

Install Go using one of these package managers:

  • Using winget:

    winget install GoLang.Go
    
  • Using Chocolatey:

    choco install golang
    
  • Using Scoop:

    scoop install go
    

Verify installation:

go version

macOS

Install Go using Homebrew:

brew install go

Verify installation:

go version

Building the MCP Server

  1. Clone and build the repository:

    git clone https://github.com/krishh-amilineni/mcp-azuredevops-bridge.git
    cd mcp-azuredevops-bridge
    go build
    
  2. Configure your environment with your Azure DevOps credentials:

    export AZURE_DEVOPS_ORG="your-org"
    export AZDO_PAT="your-pat-token"
    export AZURE_DEVOPS_PROJECT="your-project"
    
  3. Add the server to your Windsurf/Cursor configuration:

    {
      "mcpServers": {
        "azuredevops-bridge": {
          "command": "/full/path/to/mcp-azuredevops-bridge/mcp-azuredevops-bridge",
          "args": [],
          "env": {
            "AZURE_DEVOPS_ORG": "organization",
            "AZDO_PAT": "personal_access_token",
            "AZURE_DEVOPS_PROJECT": "project"
          }
        }
      }
    }
    

Usage Examples

Work Item Management

You can create and manage work items by asking your AI assistant:

"Create a user story for the new authentication feature in Azure DevOps"

Wiki Documentation

Access and modify wiki pages with natural language requests:

"Create a wiki page documenting the API endpoints for our service"
"List all wiki pages in our project wiki"
"Get the content of the 'Getting Started' page from the wiki"
"Show me all available wikis in my Azure DevOps project"

Sprint Planning

Get information about sprints:

"Show me the current sprint's work items and their status"

Attachments and Comments

Add attachments to work items:

"Add this screenshot as an attachment to work item #123"

Features

Work Item Management

  • Create new work items (user stories, bugs, tasks, etc.)
  • Update existing work items
  • Query work items by various criteria
  • Link work items to each other

Wiki Management

  • Create and update wiki pages
  • Search wiki content
  • Retrieve page content and subpages
  • Automatic wiki discovery and smart wiki selection

Sprint Management

  • Get current sprint information
  • List all sprints
  • View sprint statistics

Attachments and Comments

  • Add attachments to work items
  • Retrieve attachments from work items
  • Add and view comments on work items

Advanced Wiki Usage

The bridge includes several tools for working with wikis:

  • list_wiki_pages: Lists all wiki pages, optionally from a specific path
  • get_wiki_page: Retrieves the content of a specific wiki page
  • manage_wiki_page: Creates or updates a wiki page
  • search_wiki: Searches for content across wiki pages
  • get_available_wikis: Lists all available wikis in your Azure DevOps organization

Troubleshooting Wiki Access

If you're having trouble accessing wiki content:

  • Use the get_available_wikis tool to see all available wikis and their IDs
  • Check that your PAT token has appropriate permissions for wiki access
  • Verify that the wiki path is correct (wiki paths are case-sensitive)
  • Enable verbose logging to see detailed request and response information

Security Notes

This integration uses Personal Access Tokens (PAT) for authenticating with Azure DevOps. Ensure your PAT has the appropriate permissions for the operations you need to perform.

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.

Want to 10x your AI skills?

Get a free account and learn to code + market your apps using AI (with or without vibes!).

Nah, maybe later