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:

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:

https://<your-devops-server>/<organization>/<project>

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)

{
  "mcpServers": {
    "devops-onprem": {
      "command": "uvx",
      "args": ["mcp-devops-onpremise@latest"],
      "env": {
        "DEVOPS_API_URL": "https://your-devops-server/your-organization/your-project",
        "DEVOPS_USERNAME": "DOMAIN\\your-username",
        "DEVOPS_PASSWORD": "your-password"
      }
    }
  }
}

With PAT

{
  "mcpServers": {
    "devops-onprem": {
      "command": "uvx",
      "args": ["mcp-devops-onpremise@latest"],
      "env": {
        "DEVOPS_API_URL": "https://your-devops-server/your-organization/your-project",
        "DEVOPS_PAT": "your-personal-access-token"
      }
    }
  }
}

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