Azure DevOps MCP
About
Integrates with Azure DevOps, allowing interaction with its services. Requires a Personal Access Token (PAT) for authentication.
Details
- Author
- cakriwut
- Categories
- Developer Tools, Other, Infrastructure, Project Management
Jump to
Setup
Install Azure DevOps MCP in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/cakriwut/ado-mcp-server
Follow the installation instructions in the repository README, then restart your MCP client.
Azure DevOps MCP (ADO-MCP-Server) for Cline
This Model Context Protocol (MCP) server provides integration with Azure DevOps, allowing Cline and Roo Code to interact with Azure DevOps services.
The project repository is located at:https://github.com/cakriwut/ado-mcp-server
- Node.js (v20 LTS or higher)
- npm (comes with Node.js)
- A Cline installation
- Azure DevOps account with access tokens
To install Azure DevOps MCP Server (ADO-MCP-Server) automatically viaSmithery:
npx -y @smithery/cli install @cakriwut/ado-mcp-server --client claude
git clone https://github.com/cakriwut/ado-mcp-server.git cd ado-mcp-server
Note: The build output (build/directory) is not included in version control. You must run the build command after cloning the repository.
1. Get Azure DevOps Personal Access Token (PAT)
Add the server configuration to your MCP settings file:
Configuration file location:%APPDATA%/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json
Configuration file location:%LOCALAPPDATA%/Claude/claude_desktop_config.json
Add the following configuration to themcpServersobject:
{ "mcpServers": { "azure-devops-mcp-server": { "command": "node", "args": ["C:/absolute/path/to/ado-mcp-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": [] } } }
- C:/absolute/path/to/ado-mcp-server: The absolute path to where you cloned this repository (use forward slashes)
- your-organization: Your Azure DevOps organization name
- your-project-name: Your Azure DevOps project name
- your-personal-access-token: The PAT you generated in step 1
- Use forward slashes (/) in the path, not backslashes ()
- Provide the full absolute path to the build/index.js file
- Restart Roo Code or Cline after making changes to the configuration
- 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
- search_work_items: Search for work items using text search
- add_work_item_comment: Add a comment to a work item
- get_work_item_comments: Get comments from a work item
- get_boards: Get available boards in the project
- list_pipelines: List all pipelines in the project
- trigger_pipeline: Execute a pipeline
- list_pull_requests: List pull requests
- create_pull_request: Create a new pull request
- update_pull_request: Update a pull request
- get_wikis: List all wikis in the project
- list_wiki_pages: List pages in a wiki
- get_wiki_page: Get a wiki page by path
- create_wiki: Create a new wiki
- update_wiki_page: Create or update a wiki page
- create_wiki_page: Create a new wiki page
- search_wiki_page: Search for pages in a wiki by text
- list_projects: List all projects in the Azure DevOps organization
ADO-MCP-Server includes a command-line interface that allows you to interact with Azure DevOps directly from the terminal. The CLI is available asazure-devops-cliafter building the project.
Before using the CLI, set up your environment variables:
# PowerShell $env:AZURE_DEVOPS_ORG = "your-organization" $env:AZURE_DEVOPS_PROJECT = "your-project-name" $env:AZURE_DEVOPS_PAT = "your-personal-access-token"
# Get a work item by ID node .\build\cli\index.js work-item get -i 42 # Search for work items node .\build\cli\index.js work-item search -s "bug" # Create a new task node .\build\cli\index.js work-item create -t "Task" -d '[{"op":"add","path":"/fields/System.Title","value":"New Task"}]' # Add a comment to a work item node .\build\cli\index.js work-item add-comment -i 42 -t "This is a comment added via CLI" # Get comments from a work item node .\build\cli\index.js work-item get-comments -i 42
# List all wikis in the project node .\build\cli\index.js wiki list # Get a wiki page node .\build\cli\index.js wiki page -w <wikiIdentifier> -p "/path/to/page" --include-content # Search wiki pages node .\build\cli\index.js wiki search -w <wikiIdentifier> -s "search term"
For more detailed CLI usage examples, seedocs/wiki-cli-usage.mdanddocs/command-list.md.
- Restart Cline (or VSCode) after adding the configuration
- The Azure DevOps MCP server should now be listed in Cline's capabilities
- You can verify the installation using the MCP Inspector:
- Check that the path in your MCP settings is correct
- Verify your Azure DevOps credentials
- Check the Cline logs for any error messages
- Verify your PAT hasn't expired
- Ensure the PAT has all necessary scopes
- Double-check the organization and project names
- Run the inspector tool to verify the server is working correctly
- Check the server logs for any error messages
- Make your changes in thesrcdirectory
- Runnpm run watchfor development
- Build withnpm run buildwhen ready
- Test using the inspector:npm run inspector
The project includes test scripts for all MCP Server Commands. These tests help verify that the server can communicate with Azure DevOps correctly.
-
Make sure you have a valid.envfile in the root directory with the following variables:
AZURE_DEVOPS_ORG=your-organization AZURE_DEVOPS_PROJECT=your-project AZURE_DEVOPS_PAT=your-personal-access-token
For a quick test of your Azure DevOps connection:
This runs a simple JavaScript test that only tests the list_projects command.
For a more comprehensive test of all MCP Server Commands:
This runs a simple JavaScript test that tests all the main commands in one file.
To run tests for specific command categories:
npm run test:work-item # Test Work Item Tools npm run test:board # Test Board Tools npm run test:wiki # Test Wiki Tools npm run test:project # Test Project Tools npm run test:pipeline # Test Pipeline Tools npm run test:pull-request # Test Pull Request Tools
See thetests/README.mdfile for more information about the tests.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
Manage Azure DevOps projects, work items, builds, and releases.
Interact with Azure DevOps for managing projects, pipelines, and repositories.
Integrate with Azure DevOps services to manage work items, repositories, and pipelines.
An MCP server for Azure DevOps, enabling AI assistants to interact with Azure DevOps APIs.
Integrate Azure DevOps with Cursor IDE. Provides over 60 tools using PAT authentication, no CLI needed.
An MCP server for Azure DevOps with tools for project management, work items, pull requests, builds, tests, and more.
All Azure MCP tools in a single server. The Azure MCP Server implements the MCP specification to create a seamless connection between AI agents and Azure services. Azure MCP Server can be used alone or with the GitHub Copilot for Azure extension in VS Code.
An engineering governance and safety control plane for AI coding agents to enforce strict SDLC discipline, quality gates, and security branch protections.
Interact with Azure DevOps Work Items using the Azure DevOps REST API.
Provides comprehensive integration with Azure DevOps services.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
