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.
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
Install Go using Homebrew:
brew install go
Verify installation:
go version
Clone and build the repository:
git clone https://github.com/krishh-amilineni/mcp-azuredevops-bridge.git
cd mcp-azuredevops-bridge
go build
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"
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"
}
}
}
}
You can create and manage work items by asking your AI assistant:
"Create a user story for the new authentication feature in Azure DevOps"
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"
Get information about sprints:
"Show me the current sprint's work items and their status"
Add attachments to work items:
"Add this screenshot as an attachment to work item #123"
The bridge includes several tools for working with wikis:
If you're having trouble accessing wiki content:
get_available_wikis
tool to see all available wikis and their IDsThis 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.
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.
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"
]
}
}
}
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.
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.