
Azure DevOps On-Premises
io.github.zwitbaumPublished by GitHub account zwitbaumv2.1.0Updated Oct 24, 2026
MCP server for on-premises Azure DevOps Server and TFS: repos, pull requests, work items, and wiki.
Overview
MCP server for on-premises Azure DevOps Server and TFS that lets an assistant browse repositories, review pull requests, manage work items and edit wikis.
- What you can do
- List repositories, read file content and commit changes, and get line-level diffs between commits
- Get, create and update pull requests, vote as a reviewer, and read, add, reply to, edit or delete comment threads
- Query, create, update, delete, restore and link work items, including attachments and comments
- Search code, work items and wiki pages with filters
- Read, create, update and delete wiki pages
- When to use it
- Useful when your team runs Azure DevOps Server or TFS on-premises, especially behind a VPN with Windows domain credentials, and you want an assistant to help with code review, work item triage or documentation. The official Microsoft server targets cloud Azure DevOps only.
- Requirements
- Runs locally via uvx (Python 3.10+ and uv). Requires DEVOPS_API_URL set to the full project URL, plus one authentication method: DEVOPS_USERNAME and DEVOPS_PASSWORD for NTLM, DEVOPS_PAT, or DEVOPS_TOKEN for OAuth bearer. Network access to the DevOps server, including over VPN.
Installation
In SourceWeft
- Open Azure DevOps On-Premises in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
MCP DevOps On-Premise
Model Context Protocol MCP server for on-premises Azure DevOps that lets AI assistants browse repositories, review pull requests, manage work items, and interact with wikis.
Overview
Many organizations use on-premise DevOps solutions such as TFS or Azure DevOps Server in their projects. Integrating these systems with modern agentic AI tools and LLMs can be difficult. The official Microsoft Azure DevOps MCP server does not support these environments and is unlikely to support them in the future.
This MCP server closes that gap and enables smooth integration with on-premise DevOps systems.
This project is under active development, with features continuously added to meet current requirements. Community needs are highly valued — if you miss any features, please submit an Issue. User-requested features are fast-tracked and will be prioritized and added as soon as possible.
Key Advantages
One of the most important features of this MCP server is NTLM authentication support. NTLM is required by many on-premises and enterprise environments where users authenticate with Windows domain credentials, either directly or over VPN. Most MCP servers for Azure DevOps target only cloud-hosted Azure DevOps Services with token-based auth and cannot connect to these environments.
- NTLM authentication (Windows domain credentials) for on-prem and VPN-based setups where no other auth method works.
- PAT and OAuth bearer token authentication as alternatives when available.
- Enables secure access to on-prem DevOps systems from MCP-compatible AI tools such as GitHub Copilot, Claude Desktop, Cursor, Windsurf, and others.
- Works in restricted or offline environments without exposing sensitive data to external services.
- Retrieves commit diffs with clear added/removed lines, similar to the DevOps UI.
- Helps keep and track project documentation alongside code changes.
- Automates common tasks such as work item management and code review processes.
Getting Started
Prerequisites
Python 3.10+ and uv are required. If not yet installed, see installation guide.
Quick Install
Click one of the buttons below to install directly in your IDE. You will be prompted for credentials:
[Install in VS Code] [Install in VS Code Insiders] [Install in Cursor]
For other platforms, see Manual Installation in the Getting Started guide.
Manual Installation
The MCP server can be installed manually in the following AI tools: VS Code, Visual Studio, Cursor, Goose, LM Studio, Amp, Claude Code, Claude Desktop, Codex, Gemini CLI, OpenCode, Qodo Gen, Warp, Windsurf, GitHub Copilot CLI, GitHub Copilot Coding Agent, and others.
For step-by-step instructions, see Manual Installation in the Getting Started guide.
Configuration
The DEVOPS_API_URL must point to your full project URL:
The server supports three authentication methods. If you are unsure which one to use, start with NTLM because it is the most common for on-prem/VPN setups.
For detailed setup instructions for each method, see Authentication in the Getting Started guide.
With NTLM (username + password)
With PAT
If you used a permanent install, replace
"command": "uvx"with"command": "mcp-devops-onpremise"and remove the"args"line.
Updating
All configuration examples use mcp-devops-onpremise@latest, which instructs uvx to fetch the latest version automatically on every run.
For permanent installs and release notes, see Updating in the Getting Started guide.
Available Tools
Pull Requests
Repositories
Work Items
Search
Wiki
Development
Source: README.md at commit c4a145a
Tools
0Version history
1- v2.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts