azure-devops

This MCP server integrates Azure DevOps with Cline, exposing a set of tools to interact with your Azure DevOps organization and project. The server runs as a Node.js process and exposes capabilities under categories like Work Items, Boards, Pipelines, Pull Requests, Wiki, and Projects. You can use commands such as get_work_item, list_work_items, create_work_item, update_work_item, get_boards, list_pipelines, trigger_pipeline, list_pull_requests, create_pull_request, update_pull_request, get_pull_request, get_wikis, get_wiki_page, create_wiki, update_wiki_page, and list_projects to read from or modify your Azure DevOps resources. To enable and use the server, configure the MCP settings with the provided node command path and environment variables for organization, PAT, and project, then restart Cline so the server shows up in the available capabilities. Verify the server with the MCP Inspector tool to ensure it’s connected and responding to commands.

Prerequisites:

• Node.js v20 LTS or higher
• npm (comes with Node.js)
• A Cline installation
• Azure DevOps account with access tokens

Installation steps:

1. Optional Smithery install (automatic): npx -y @smithery/cli install @stefanskiasan/azure-devops-mcp-server --client claude

2. Manual installation: a. Clone the repository: git clone https://github.com/stefanskiasan/azure-devops-mcp-server.git cd azure-devops-mcp-server b. Install dependencies: npm install c. Build the server (if applicable): 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 is added to the MCP settings file as described in the README, including the command and path to the built server, plus the required environment variables.

Tips and notes:

• The MCP server requires a valid Azure DevOps Personal Access Token (PAT) with appropriate scopes (Code, Work Items, Build, Wiki, Projects).
• The build output path must be absolute in the MCP configuration, e.g., /absolute/path/to/azure-devops-server/build/index.js.
• After editing the MCP settings, restart Cline (or the VSCode integration) so the Azure DevOps MCP server is recognized.
• If you encounter authentication errors, verify PAT validity and scopes, and double-check organization and project names.
• Use the MCP Inspector (npm run inspector) to verify connectivity and command availability.
• The server’s environment variables should be kept secure; avoid committing them to public repositories.