Azure DevOps On Premises

io.github.zwitbaum

MCP server for on-premises Azure DevOps Server and TFS: repos, pull requests, work items, and wiki.

Cloud Infrastructure Collaboration Devops

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "io.github.zwitbaum-mcp-devops-on-prem": {4      "command": "uvx",5      "args": [6        "mcp-devops-onpremise==2.1.0"7      ],8      "env": {9        "DEVOPS_API_URL": "<value>",10        "DEVOPS_USERNAME": "<value>",11        "DEVOPS_PASSWORD": "<secret>",12        "DEVOPS_PAT": "<secret>",13        "DEVOPS_TOKEN": "<secret>"14      }15    }16  }17}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

uvx mcp-devops-onpremise==2.1.0

Credentials from the publisher

DEVOPS_API_URL — Full Azure DevOps Server project URL, e.g. https://server/org/project
DEVOPS_USERNAME — NTLM username, usually DOMAIN\username
DEVOPS_PASSWORD — NTLM password
DEVOPS_PAT — Personal Access Token for PAT authentication
DEVOPS_TOKEN — OAuth bearer token for bearer-token authentication

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1DEVOPS_API_URL=<value> DEVOPS_USERNAME=<value> DEVOPS_PASSWORD=<secret> DEVOPS_PAT=<secret> DEVOPS_TOKEN=<secret> claude mcp add io.github.zwitbaum-mcp-devops-on-prem -- uvx mcp-devops-onpremise==2.1.0

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.zwitbaum-mcp-devops-on-prem": {4      "command": "uvx",5      "args": [6        "mcp-devops-onpremise==2.1.0"7      ],8      "env": {9        "DEVOPS_API_URL": "<value>",10        "DEVOPS_USERNAME": "<value>",11        "DEVOPS_PASSWORD": "<secret>",12        "DEVOPS_PAT": "<secret>",13        "DEVOPS_TOKEN": "<secret>"14      }15    }16  }17}

claude_desktop_config.json

Local · pypiPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 2.1.0
API key: DEVOPS_API_URL, DEVOPS_USERNAME, DEVOPS_PASSWORD, DEVOPS_PAT, DEVOPS_TOKEN
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Azure DevOps On Premises?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Azure DevOps On Premises need an API key?

The publisher lists these environment variables: DEVOPS_API_URL, DEVOPS_USERNAME, DEVOPS_PASSWORD, DEVOPS_PAT, DEVOPS_TOKEN.

What transport does Azure DevOps On Premises use?

Azure DevOps On Premises runs locally over stdio.

When was Azure DevOps On Premises last checked?

Last checked 2026-10-28. MCP server for on-premises Azure DevOps Server and TFS: repos, pull requests, work items, and wiki.

From the publisher

Documentation

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:

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.

Method	Description
NTLM (username + password)	Most common for on-prem/VPN. Usually the simplest first setup and best fallback if other options fail.
PAT (Personal Access Token)	Use when PAT is enabled and allowed. Tokens can expire, and token-based auth may be blocked by policy. Advantage: you do not store your account password in config.
OAuth Bearer Token	Advanced option for CI/CD pipelines. Requires OAuth 2.0 configured on your DevOps Server and a token source defined by your administrators.

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

Tool	Description	Read-only
`devops_pull_request_get`	Retrieve a pull request by ID, including linked work items and commit SHAs for diffing	✅
`devops_pull_request_write`	Create or update pull requests, update reviewers, or cast your PR vote	❌
`devops_pull_request_list_threads`	Returns a hierarchical list of non-deleted comment threads and their text comments	✅
`devops_pull_request_list_thread_comments`	List non-deleted text comments in a specific thread	✅
`devops_pull_request_create_comment`	Create a new thread with an initial comment (general or inline on a file/line)	❌
`devops_pull_request_reply_comment`	Reply to an existing comment thread	❌
`devops_pull_request_update_thread`	Update the status of a comment thread	❌
`devops_pull_request_update_comment`	Update the text of an existing comment	❌
`devops_pull_request_delete_comment`	Delete a comment from a pull request thread	❌

Repositories

Tool	Description	Read-only
`devops_repository_list`	List all repositories in the project	✅
`devops_repository_get`	Retrieve repository details by name or ID	✅
`devops_repository_commit_changes`	List files changed in a specific commit	✅
`devops_repository_diffs_commits`	Get the difference between two commits (changed file paths)	✅
`devops_repository_item_content`	Get raw file content at a specific commit or branch	✅
`devops_get_item_content_diff`	Get line-level textual diff of a file between two commits (added lines prefixed `+`, removed `-`)	✅

Work Items

Tool	Description	Read-only
`devops_work_item_get`	Retrieve a work item (PBI, bug, task) by numeric ID. Returns a compact object with key fields, attachments (files and inline images), and linked items (work items, pull requests, commits)	✅
`devops_work_item_attachment_get`	Download a work item attachment by its GUID, either saving locally or returning base64-encoded content	✅
`devops_work_item_type_get`	Get the definition of a work item type by name (e.g. `Bug`, `User Story`)	✅
`devops_work_item_query_by_wiql`	Execute a WIQL (Work Item Query Language) query and return matching work items	✅
`devops_work_item_create`	Create a new work item with typed fields; Html is the default format	❌
`devops_work_item_update`	Update fields on a work item using JSON Patch (add / replace / remove)	❌
`devops_work_item_delete`	Delete a work item, moves to Recycle Bin by default; use `destroy=True` for permanent deletion (requires project permission)	❌
`devops_work_item_undelete`	Restore a soft-deleted work item from the Recycle Bin	❌
`devops_work_item_link_update`	Add or remove a relation link between two work items (parent, child, related, successor, predecessor, etc.)	❌
`devops_work_item_artifact_link_update`	Add or remove an artifact link (Pull Request, Build, Commit, Branch, Changeset) on a work item	❌
`devops_work_item_comment_list`	List comments on a work item with configurable page size and format	✅
`devops_work_item_comment_add`	Add a comment to a work item	❌
`devops_work_item_comment_update`	Update an existing comment on a work item	❌
`devops_work_item_comment_delete`	Delete a comment from a work item	❌

Search

Tool	Description	Read-only
`devops_code_search`	Search source code with optional repository, path, and branch filters	✅
`devops_work_item_search`	Search work items with optional area, type, state, and assigned-to filters	✅
`devops_wiki_search`	Search wiki pages with an optional wiki filter	✅

Wiki

Tool	Description	Read-only
`devops_wiki_page_get`	Get wiki page metadata and optional content by wiki ID and page ID	✅
`devops_wiki_page_create_or_update`	Create or update a wiki page under a specified parent page	❌
`devops_wiki_page_update`	Update an existing wiki page by ID	❌
`devops_wiki_page_delete`	Delete an existing wiki page by ID	❌

Development

# Install dev dependencies
uv sync --group dev

# Run linting
uv run ruff check src/
uv run black --check src/

# Run tests
uv run pytest tests/

Azure DevOps On Premises

io.github.zwitbaum

MCP server for on-premises Azure DevOps Server and TFS: repos, pull requests, work items, and wiki.

Cloud Infrastructure Collaboration Devops

Add to Cursor Add to VS Code Run on PlugMCP

GitHub Website

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "io.github.zwitbaum-mcp-devops-on-prem": {4      "command": "uvx",5      "args": [6        "mcp-devops-onpremise==2.1.0"7      ],8      "env": {9        "DEVOPS_API_URL": "<value>",10        "DEVOPS_USERNAME": "<value>",11        "DEVOPS_PASSWORD": "<secret>",12        "DEVOPS_PAT": "<secret>",13        "DEVOPS_TOKEN": "<secret>"14      }15    }16  }17}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

uvx mcp-devops-onpremise==2.1.0

Credentials from the publisher

DEVOPS_API_URL — Full Azure DevOps Server project URL, e.g. https://server/org/project
DEVOPS_USERNAME — NTLM username, usually DOMAIN\username
DEVOPS_PASSWORD — NTLM password
DEVOPS_PAT — Personal Access Token for PAT authentication
DEVOPS_TOKEN — OAuth bearer token for bearer-token authentication

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1DEVOPS_API_URL=<value> DEVOPS_USERNAME=<value> DEVOPS_PASSWORD=<secret> DEVOPS_PAT=<secret> DEVOPS_TOKEN=<secret> claude mcp add io.github.zwitbaum-mcp-devops-on-prem -- uvx mcp-devops-onpremise==2.1.0

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.zwitbaum-mcp-devops-on-prem": {4      "command": "uvx",5      "args": [6        "mcp-devops-onpremise==2.1.0"7      ],8      "env": {9        "DEVOPS_API_URL": "<value>",10        "DEVOPS_USERNAME": "<value>",11        "DEVOPS_PASSWORD": "<secret>",12        "DEVOPS_PAT": "<secret>",13        "DEVOPS_TOKEN": "<secret>"14      }15    }16  }17}

claude_desktop_config.json

Local · pypiPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 2.1.0
API key: DEVOPS_API_URL, DEVOPS_USERNAME, DEVOPS_PASSWORD, DEVOPS_PAT, DEVOPS_TOKEN
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Azure DevOps On Premises?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Azure DevOps On Premises need an API key?

The publisher lists these environment variables: DEVOPS_API_URL, DEVOPS_USERNAME, DEVOPS_PASSWORD, DEVOPS_PAT, DEVOPS_TOKEN.

What transport does Azure DevOps On Premises use?

Azure DevOps On Premises runs locally over stdio.

When was Azure DevOps On Premises last checked?

Last checked 2026-10-28. MCP server for on-premises Azure DevOps Server and TFS: repos, pull requests, work items, and wiki.

From the publisher

Documentation

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

This MCP server closes that gap and enables smooth integration with on-premise DevOps systems.

Key Advantages

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

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.

Method	Description
NTLM (username + password)	Most common for on-prem/VPN. Usually the simplest first setup and best fallback if other options fail.
PAT (Personal Access Token)	Use when PAT is enabled and allowed. Tokens can expire, and token-based auth may be blocked by policy. Advantage: you do not store your account password in config.
OAuth Bearer Token	Advanced option for CI/CD pipelines. Requires OAuth 2.0 configured on your DevOps Server and a token source defined by your administrators.

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

Tool	Description	Read-only
`devops_pull_request_get`	Retrieve a pull request by ID, including linked work items and commit SHAs for diffing	✅
`devops_pull_request_write`	Create or update pull requests, update reviewers, or cast your PR vote	❌
`devops_pull_request_list_threads`	Returns a hierarchical list of non-deleted comment threads and their text comments	✅
`devops_pull_request_list_thread_comments`	List non-deleted text comments in a specific thread	✅
`devops_pull_request_create_comment`	Create a new thread with an initial comment (general or inline on a file/line)	❌
`devops_pull_request_reply_comment`	Reply to an existing comment thread	❌
`devops_pull_request_update_thread`	Update the status of a comment thread	❌
`devops_pull_request_update_comment`	Update the text of an existing comment	❌
`devops_pull_request_delete_comment`	Delete a comment from a pull request thread	❌

Repositories

Tool	Description	Read-only
`devops_repository_list`	List all repositories in the project	✅
`devops_repository_get`	Retrieve repository details by name or ID	✅
`devops_repository_commit_changes`	List files changed in a specific commit	✅
`devops_repository_diffs_commits`	Get the difference between two commits (changed file paths)	✅
`devops_repository_item_content`	Get raw file content at a specific commit or branch	✅
`devops_get_item_content_diff`	Get line-level textual diff of a file between two commits (added lines prefixed `+`, removed `-`)	✅

Work Items

Tool	Description	Read-only
`devops_work_item_get`	Retrieve a work item (PBI, bug, task) by numeric ID. Returns a compact object with key fields, attachments (files and inline images), and linked items (work items, pull requests, commits)	✅
`devops_work_item_attachment_get`	Download a work item attachment by its GUID, either saving locally or returning base64-encoded content	✅
`devops_work_item_type_get`	Get the definition of a work item type by name (e.g. `Bug`, `User Story`)	✅
`devops_work_item_query_by_wiql`	Execute a WIQL (Work Item Query Language) query and return matching work items	✅
`devops_work_item_create`	Create a new work item with typed fields; Html is the default format	❌
`devops_work_item_update`	Update fields on a work item using JSON Patch (add / replace / remove)	❌
`devops_work_item_delete`	Delete a work item, moves to Recycle Bin by default; use `destroy=True` for permanent deletion (requires project permission)	❌
`devops_work_item_undelete`	Restore a soft-deleted work item from the Recycle Bin	❌
`devops_work_item_link_update`	Add or remove a relation link between two work items (parent, child, related, successor, predecessor, etc.)	❌
`devops_work_item_artifact_link_update`	Add or remove an artifact link (Pull Request, Build, Commit, Branch, Changeset) on a work item	❌
`devops_work_item_comment_list`	List comments on a work item with configurable page size and format	✅
`devops_work_item_comment_add`	Add a comment to a work item	❌
`devops_work_item_comment_update`	Update an existing comment on a work item	❌
`devops_work_item_comment_delete`	Delete a comment from a work item	❌

Search

Tool	Description	Read-only
`devops_code_search`	Search source code with optional repository, path, and branch filters	✅
`devops_work_item_search`	Search work items with optional area, type, state, and assigned-to filters	✅
`devops_wiki_search`	Search wiki pages with an optional wiki filter	✅

Wiki

Tool	Description	Read-only
`devops_wiki_page_get`	Get wiki page metadata and optional content by wiki ID and page ID	✅
`devops_wiki_page_create_or_update`	Create or update a wiki page under a specified parent page	❌
`devops_wiki_page_update`	Update an existing wiki page by ID	❌
`devops_wiki_page_delete`	Delete an existing wiki page by ID	❌

Development

# Install dev dependencies
uv sync --group dev

# Run linting
uv run ruff check src/
uv run black --check src/

# Run tests
uv run pytest tests/