Azure DevOps MCP by Tiberriver256
A community MCP server for Azure DevOps work items, code and builds, with PAT authentication for on-premises Azure DevOps Server
- 400 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- A PAT or Azure sign-in opens the organization to the agent: it creates branches and commits and changes pull requests and work items
- The trigger_pipeline tool starts builds and deployments with parameters the agent chooses
- Attachments and pipeline logs may contain secrets and end up in the model context
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/azure-devops-mcp-by-tiberriver256Detects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- A PAT or Azure sign-in opens the organization to the agent: it creates branches and commits and changes pull requests and work items
- The trigger_pipeline tool starts builds and deployments with parameters the agent chooses
- Attachments and pipeline logs may contain secrets and end up in the model context
This is third-party code. Review the repository files before installing.
What it does
The server connects an agent to Azure DevOps through its REST API: projects, work items, repositories, branches, pull requests, pipelines and wikis. You connect it to Claude Desktop or Cursor, and it starts through npx. It is a community project by Tiberriver256 with support for on-premises Azure DevOps Server. Microsoft’s official server targets cloud-based Azure DevOps Services. Tools are split by area. In repositories the agent reads files and the tree, creates branches and commits changes as a unified diff or as search and replace instructions. It creates, updates and links work items and adds attachments. For pipelines there are listings, runs, a stage and job timeline, logs, artifact download and triggering with parameters. In pull requests the agent creates a request, writes and reads comments and looks at changes, checks and policy evaluation. Search covers code, wikis and work items. On-premises Azure DevOps Server uses a personal access token (PAT). Cloud-based Services also supports Azure Identity and an Azure CLI session.
Who it is for. For teams that keep tasks, code and builds in Azure DevOps and want to drive them from Claude Desktop or Cursor, especially with an on-premises Azure DevOps Server.
Good fit when
- You need to create or update a work item and link it to another one straight from the chat
- A pull request needs a look at its changes and policy checks plus a comment
- A pipeline run failed and you want to read its timeline and log
- Azure DevOps Server runs in your own network, including an older version that Microsoft's official server may not support
- You need to find code across several repositories of a project or a wiki page
Not a fit when
- You work in the cloud Azure DevOps Services and want a server supported by the product team: Microsoft maintains an official one, and the documentation suggests starting there
- You need a server mode that hides write tools: none is provided, and access is limited by account or PAT permissions
- You need tokenless sign-in to an on-premises Azure DevOps Server: it supports PAT only
Example request
Show the failed build pipeline runs from this week, read the log of the latest one and create a bug work item linking to the runMCP
- Transport
- stdio
- Authentication
- key is optional
Environment variables
AZURE_DEVOPS_ORG_URLrequired- Address of the Azure DevOps organization or the on-premises server collection.
AZURE_DEVOPS_AUTH_METHOD- Sign-in method: pat, azure-identity or azure-cli, azure-identity by default.
AZURE_DEVOPS_PATsecret- Personal access token, needed only with the pat method.
AZURE_DEVOPS_DEFAULT_PROJECT- Default project when a request names none.
AZURE_DEVOPS_API_VERSION- REST API version for tools that call it directly, 7.1 by default.
AZURE_CLIENT_SECRETsecret- Azure AD application secret, needed only for service principals together with AZURE_TENANT_ID and AZURE_CLIENT_ID.
Limitations
Running the package requires Node.js, npm and an Azure DevOps account with the necessary permissions. On-premises Server supports PAT only. Set the organization or collection address through `AZURE_DEVOPS_ORG_URL`, and enter the token locally in client settings.
REST API versions depend on the Server release. Direct calls default to 7.1, so configure `AZURE_DEVOPS_API_VERSION` using the project’s table, such as 7.0 for Server 2022. At 6.0 and below, one setting cannot cover all stable and preview endpoints, and some tools may fail.
There is no separate read-only mode. Account permissions limit changes to code and work items and the triggering of builds. Configure approvals in the client; tool results may be sent to its model.
How to disable. Remove the azureDevOps entry from the Claude Desktop or Cursor configuration and restart the client. If you issued a PAT just for this server, revoke it in the Azure DevOps settings: while the token is alive it works outside the agent as well.
FAQ
How do I connect Azure DevOps MCP to Claude Desktop or Cursor?
Add an azureDevOps entry to mcpServers with the command npx and the arguments -y @tiberriver256/mcp-server-azure-devops, and in env set AZURE_DEVOPS_ORG_URL, AZURE_DEVOPS_AUTH_METHOD and, if needed, AZURE_DEVOPS_DEFAULT_PROJECT. There is no need to clone the repository.
How does this server differ from Microsoft's official Azure DevOps MCP?
Microsoft’s official server targets cloud-based Azure DevOps Services. Tiberriver256’s project also connects to on-premises Azure DevOps Server with PAT authentication. Older releases require an appropriate API version and separate checks of the tools you need.
How do I sign in to Azure DevOps Server on my own server?
Use the pat method: set AZURE_DEVOPS_AUTH_METHOD to pat, put the token in AZURE_DEVOPS_PAT and the collection address in AZURE_DEVOPS_ORG_URL, for example https://server:8080/tfs/DefaultCollection.
How do I sign in to cloud Azure DevOps without a token?
Run az login and set AZURE_DEVOPS_AUTH_METHOD to azure-identity, which is the default, or to azure-cli. For service principals add AZURE_TENANT_ID, AZURE_CLIENT_ID and AZURE_CLIENT_SECRET.
Can the agent trigger pipelines and change code through this server?
Yes. The trigger_pipeline tool starts a run with parameters, create_commit commits changes to several files, create_branch creates a branch, and update_pull_request changes status and reviewers. Account permissions limit access, so issue the PAT with the minimum scopes needed.
Discussion
No questions or reviews yet.
Related
MCP serversAzure DevOps MCP server
Azure DevOps MCP Server
Official Microsoft MCP server for Azure DevOps: work items, repositories, builds, test plans, and wiki from the agent
Microsoft's official MCP server for Azure: the agent sees subscription resources and works with Azure services on your behalf
Azure Skills
Azure Skills Plugin
Microsoft's official plugin: Azure skills plus the Azure MCP Server and Foundry MCP wired in for real cloud actions
A Bitbucket Cloud MCP server with six generic tools that reach any repository or pull request REST API path
GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent
The remote MCP server of Devopness, a platform that builds infrastructure and deploys apps in your own cloud accounts
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Azure DevOps MCP by Tiberriver256 (this card) | no | key is optional | 400 | |
| Azure DevOps MCP server | yes | OAuth | 2,081 | Microsoft’s official server for cloud-based Azure DevOps Services; Tiberriver256’s variant also supports on-premises Server through PAT |
| Jira, Confluence, Bitbucket and Jenkins MCP | no | API key | 1 | a local server for corporate Jira, Confluence, Bitbucket Server and Jenkins |
README in short
The code uses MIT. `get_me` and `list_organizations` work only with cloud-based Services. Removing the MCP connection or revoking a PAT stops access but does not undo existing commits, work items or runs.