home / mcp / azure devops mcp server
Provides deep integration with Azure DevOps to manage work items, boards, pipelines, pull requests, wikis, and projects from your MCP client.
Configuration
View docs{
"mcpServers": {
"cakriwut-ado-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"
}
}
}
}You can connect Cline to Azure DevOps with this MCP server to manage work items, boards, pipelines, pull requests, wikis, and projects directly from your editor or IDE. It runs locally as a stdio MCP server and is configured to communicate with your Azure DevOps organization and project using a Personal Access Token (PAT).
Install and start the MCP server, then configure your MCP client to load the new server as a local tool. Once configured, you can perform common Azure DevOps actions from your editor or CLI: retrieve work items, create and update items, search work items, manage boards, trigger pipelines, create and update pull requests, access and edit wiki pages, and list or inspect projects. The server exposes a set of tools you call from your MCP client to interact with Azure DevOps services without leaving your development environment.
Prerequisites ensure you have Node.js and npm, plus access to an Azure DevOps account and a Cline installation.
Installing via Smithery automatically pulls in the MCP server and prepares it for use.
npx -y @smithery/cli install @cakriwut/ado-mcp-server --client claudeManual installation steps if you prefer to set things up yourself.
git clone https://github.com/cakriwut/ado-mcp-server.git
cd ado-mcp-server
npm install
npm run buildCreate and add the MCP server configuration to your client settings to enable Azure DevOps interactions.
{
"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": []
}
}
}Use forward slashes in Windows paths and provide the full absolute path to the built entry point.
Restart your editor or IDE after updating the configuration to ensure the new MCP server is loaded.
After configuring, restart the editor and verify that the Azure DevOps MCP server appears in the list of available MCP servers or capabilities. You can also run the inspector to confirm the server is functioning correctly.
If the server isn’t connecting, verify the path to the built entry point, recheck your Azure DevOps credentials, and review editor logs for error messages.
If authentication fails, ensure your PAT is valid and has all required scopes, and confirm your organization and project names are correct.
To modify or extend the server, work in the src directory, run development builds with a watch workflow, and test changes using the inspector tool. Build final changes before production usage.
The project includes tests for MCP server commands to validate Azure DevOps interactions. Use an environment file with organization, project, and PAT values when running tests.
Retrieve a work item by its ID from Azure DevOps.
Query work items using WIQL to retrieve multiple items.
Create a new work item such as Bug, Task, or User Story.
Update fields on an existing work item.
Search for work items by text across the project.
Add a comment to a specific work item.
Fetch comments for a given work item.
List boards available within the project.
List all pipelines in the project.
Trigger or run a pipeline in the project.
List pull requests in the repository.
Create a new pull request.
Update an existing pull request.
List all wikis in the project.
List pages within a wiki.
Retrieve a wiki page by path.
Create a new wiki.
Create or update a wiki page.
Create a new wiki page.
Search for wiki pages by text.
List all projects in the Azure DevOps organization.