Azure DevOps work usually means leaving the editor to read a work item and coming back to write the code. Here the item, the board it sits on, the file it refers to and the branch comparison behind it all arrive in the session you are already in.
An Azure DevOps client for one organisation and project, set in the configuration. It covers the work-item side — list, read, create, update — the boards they sit on, and the repository side: which repos exist, the contents of a file, and the difference between two branches.
- Work items listed, read, created and updated
- The boards for the project
- The repositories in the project
- A file read straight out of a repository
- Two branches compared
Node.js v20 LTS or higher, and a personal access token with the scopes the tools use: Code (read, write), Work Items (read, write), Build (read, execute), Wiki (read, write) and Project and Team (read). The organisation name, the token and the project id go in the client config. The build output is not committed, so npm run build is required after cloning.
One command plus a key — npx -y @smithery/cli install @RainyCodeWizard/azure-devops-mcp-server --client claude, then supply credentials