Azure DevOps MCP Server for Cline
This Model Context Protocol (MCP) server provides integration with Azure DevOps, allowing Cline to interact with Azure DevOps services.
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
- Clone this repository:
git clone https://github.com/stefanskiasan/azure-devops-mcp-server.git
cd azure-devops-mcp-server
- Install dependencies:
npm install
- Build the server:
npm run build
Note: The build output (build/ directory) is not included in version control. You must run the build command after cloning the repository.
Configuration
1. Get Azure DevOps Personal Access Token (PAT)
- Go to Azure DevOps and sign in
- Click on your profile picture in the top right
- Select "Security"
- Click "New Token"
- Give your token a name and select the required scopes:
Code (read, write)- For Pull Request operationsWork Items (read, write)- For Work Item managementBuild (read, execute)- For Pipeline operationsWiki (read, write)- For Wiki operationsProject and Team (read)- For Project and Board information
- Copy the generated token
2. Configure 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 following values:
/absolute/path/to/azure-devops-server: The absolute path to where you cloned this repositoryyour-organization: Your Azure DevOps organization nameyour-project-name: Your Azure DevOps project nameyour-personal-access-token: The PAT you generated in step 1
Available Tools
Work Items
get_work_item: Get a work item by IDlist_work_items: Query work items using WIQLcreate_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 projecttrigger_pipeline: Execute a pipeline
Pull Requests
list_pull_requests: List pull requestscreate_pull_request: Create a new pull requestupdate_pull_request: Update a pull requestget_pull_request: Get pull request details
Wiki
get_wikis: List all wikis in the projectget_wiki_page: Get a wiki pagecreate_wiki: Create a new wikiupdate_wiki_page: Create or update a wiki page
Projects
list_projects: List all projects in the Azure DevOps organization
Verification
- 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:
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
Development
To modify or extend the server:
- Make your changes in the
srcdirectory - Run
npm run watchfor development - Build with
npm run buildwhen ready - Test using the inspector:
npm run inspector
License
MIT License - See LICENSE for details
