GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
MCP server for on-premises Azure DevOps Server and TFS: repos, pull requests, work items, and wiki.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
DEVOPS_API_URL, DEVOPS_USERNAME, DEVOPS_PASSWORD, DEVOPS_PAT, DEVOPS_TOKENValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"devops-on-prem": {
"command": "uvx",
"args": [
"mcp-devops-onpremise"
],
"env": {
"DEVOPS_API_URL": "your-value",
"DEVOPS_USERNAME": "your-value",
"DEVOPS_PASSWORD": "your-value",
"DEVOPS_PAT": "your-value",
"DEVOPS_TOKEN": "your-value"
}
}
}
}Run this in your terminal
claude mcp add devops-on-prem --env DEVOPS_API_URL=your-value --env DEVOPS_USERNAME=your-value --env DEVOPS_PASSWORD=your-value --env DEVOPS_PAT=your-value --env DEVOPS_TOKEN=your-value -- uvx mcp-devops-onpremiseFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"devops-on-prem": {
"command": "uvx",
"args": [
"mcp-devops-onpremise"
],
"env": {
"DEVOPS_API_URL": "your-value",
"DEVOPS_USERNAME": "your-value",
"DEVOPS_PASSWORD": "your-value",
"DEVOPS_PAT": "your-value",
"DEVOPS_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"devops-on-prem": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-devops-onpremise"
],
"env": {
"DEVOPS_API_URL": "your-value",
"DEVOPS_USERNAME": "your-value",
"DEVOPS_PASSWORD": "your-value",
"DEVOPS_PAT": "your-value",
"DEVOPS_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
DEVOPS_USERNAME envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account zwitbaum, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: DEVOPS_API_URL, DEVOPS_PASSWORD, DEVOPS_PAT, DEVOPS_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (2.1.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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 • Getting Started • Updating • Available Tools • Development
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.
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.
Python 3.10+ and uv are required. If not yet installed, see installation guide.
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.
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.
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.
{
"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" } } } }
{
"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.
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.
| 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 | ❌ |
| 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 -) | ✅ |
| 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 | ❌ |
| 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 | ✅ |
| 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
Only the beginning is shown; read the rest in the repo