@azure-devops/mcp 2.7.0-nightly.20260510 → 2.7.0-nightly.20260512

package/README.md

@@ -3,19 +3,19 @@
 > [!IMPORTANT]
 > The Azure DevOps Remote MCP Server is now available in public preview for all organizations. We recommend migrating to the [Remote MCP Server](https://learn.microsoft.com/en-us/azure/devops/mcp-server/remote-mcp-server) going forward.
 >
-> [Learn more](#-remote-mcp-server)
+> [Learn more](#-remote-mcp-server-recommended)
 
-This TypeScript project provides a **local** MCP server for Azure DevOps, enabling you to perform a wide range of Azure DevOps tasks directly from your code editor.
+This project provides Azure DevOps MCP tooling for AI agents, with a **remote-first** onboarding experience and a local server option when you need it.
 
 ## 📄 Table of Contents
 
 1. [📺 Overview](#-overview)
 2. [🏆 Expectations](#-expectations)
-3. [🚀 Remote MCP Server](#-remote-mcp-server)
+3. [🚀 Remote MCP Server (Recommended)](#-remote-mcp-server-recommended)
 4. [⚙️ Supported Tools](#️-supported-tools)
-5. [🔌 Installation & Getting Started](#-installation--getting-started)
-6. [🌏 Using Domains](#-using-domains)
-7. [🐥 Project and Team Defaults](#-project-and-team-defaults)
+5. [🔌 Local MCP Server Installation (Optional)](#-local-mcp-server-installation-optional)
+6. [🌏 Using Domains (local)](#-using-domains-local)
+7. [🐥 Project and Team Defaults (local)](#-project-and-team-defaults-local)
 8. [📝 Troubleshooting](#-troubleshooting)
 9. [🎩 Examples & Best Practices](#-examples--best-practices)
 10. [🙋‍♀️ Frequently Asked Questions](#️-frequently-asked-questions)
@@ -40,9 +40,9 @@ The Azure DevOps MCP Server brings Azure DevOps context to your agents. Try prom
 
 ## 🏆 Expectations
 
-The Azure DevOps MCP Server is built from tools that are concise, simple, focused, and easy to use—each designed for a specific scenario. We intentionally avoid complex tools that try to do too much. The goal is to provide a thin abstraction layer over the REST APIs, making data access straightforward and letting the language model handle complex reasoning.
+The Azure DevOps MCP Server is built around tools that are concise, simple, focused, and easy to use, with each one designed for a specific scenario. We intentionally avoid creating complex tools that try to do too much. The goal is to provide a thin abstraction layer over the REST APIs that makes data access straightforward while allowing the language model to handle the more complex reasoning.
 
-## 🚀 Remote MCP Server
+## 🚀 Remote MCP Server (Recommended)
 
 The Azure DevOps **Remote MCP Server** is now available in [public preview](https://devblogs.microsoft.com/devops/azure-devops-remote-mcp-server-public-preview).
 
@@ -55,13 +55,40 @@ If you encounter issues with tools, need support, or have a feature request, you
 > [!WARNING]
 > Internal Microsoft users of the Remote MCP Server should **not** create issues in this repository. Please use the dedicated Teams channel instead.
 
-For instructions on how to get started with the Remote MCP Server, see the [onboarding documentation](https://learn.microsoft.com/en-us/azure/devops/mcp-server/remote-mcp-server).
+For complete instructions, see the [Remote MCP Server onboarding documentation](https://learn.microsoft.com/en-us/azure/devops/mcp-server/remote-mcp-server?view=azure-devops).
+
+### Quick start with `.vscode/mcp.json`
+
+Use this configuration to connect directly to the Azure DevOps-hosted endpoint using streamable HTTP transport:
+
+```json
+{
+  "servers": {
+    "ado-remote-mcp": {
+      "url": "https://mcp.dev.azure.com/{organization}",
+      "type": "http"
+    }
+  },
+  "inputs": []
+}
+```
+
+See [documentation](https://learn.microsoft.com/en-us/azure/devops/mcp-server/remote-mcp-server?view=azure-devops#mcpjson-configuration) for additional configuration options.
+
+After saving `.vscode/mcp.json`, start the server from the MCP view in VS Code, then run a prompt like `List ADO projects`.
 
 ## ⚙️ Supported Tools
 
-See [TOOLSET.md](./docs/TOOLSET.md) for a comprehensive list.
+See the [Available Tools](https://learn.microsoft.com/en-us/azure/devops/mcp-server/remote-mcp-server?view=azure-devops#available-tools) documentation for the complete list of available remote tools.
+
+For a comprehensive list of local tools, see [TOOLSET.md](./docs/TOOLSET.md).
+
+## 🔌 Local MCP Server Installation (Optional)
+
+> [!IMPORTANT]
+> Start with the Remote MCP Server first. Use the local MCP Server only if your scenario specifically requires a local `stdio` setup.
 
-## 🔌 Installation & Getting Started
+Use this section if you specifically need the local `stdio` server experience. For most users, start with the [Remote MCP Server](#-remote-mcp-server-recommended) section above.
 
 For the best experience, use Visual Studio Code and GitHub Copilot. See the [getting started documentation](./docs/GETTINGSTARTED.md) to use our MCP Server with other tools such as Visual Studio 2022, Claude Code, Cursor, Opencode, and Kilocode.
 
@@ -73,7 +100,7 @@ For the best experience, use Visual Studio Code and GitHub Copilot. See the [get
 
 ### Installation
 
-#### 🧨 Install from Public Feed (Recommended)
+#### 🧨 Install from Public Feed
 
 This installation method is the easiest for all users of Visual Studio Code.
 
@@ -140,7 +167,7 @@ Open GitHub Copilot Chat and try a prompt like `List ADO projects`. The first ti
 
 See the [getting started documentation](./docs/GETTINGSTARTED.md) to use our MCP Server with other tools such as Visual Studio 2022, Claude Code, and Cursor.
 
-## 🌏 Using Domains
+## 🌏 Using Domains (local)
 
 Azure DevOps exposes a large surface area. As a result, our Azure DevOps MCP Server includes many tools. To keep the toolset manageable, avoid confusing the model, and respect client limits on loaded tools, use Domains to load only the areas you need. Domains are named groups of related tools (for example: core, work, work-items, repositories, wiki). Add the `-d` argument and the domain names to the server args in your `mcp.json` to list the domains to enable.
 
@@ -171,7 +198,7 @@ We recommend that you always enable `core` tools so that you can fetch project l
 
 > By default all domains are loaded
 
-## 🐥 Project and Team Defaults
+## 🐥 Project and Team Defaults (local)
 
 You can also configure default Azure DevOps project and team values from `.vscode/mcp.json` using `project` and `team`, so tools can skip selection prompts.
 

package/dist/tools/repositories.js

@@ -144,6 +144,8 @@ function configureRepoTools(server, tokenProvider, connectionProvider, userAgent
             const connection = await connectionProvider();
             const gitApi = await connection.getGitApi();
             const workItemRefs = workItems ? workItems.split(" ").map((id) => ({ id: id.trim() })) : [];
+            const noDataErrorMessage = `Pull request creation returned no data and no matching PR was found. This often means repositoryId=\"${repositoryId}\" was not resolvable. ` +
+                "Try the repository GUID from repo_list_repos_by_project instead of the Project/RepoName slash format.";
             const forkSource = forkSourceRepositoryId
                 ? {
                     repository: {
@@ -170,14 +172,16 @@ function configureRepoTools(server, tokenProvider, connectionProvider, userAgent
                 }
                 else {
                     return {
-                        content: [{ type: "text", text: "Pull request created but API returned no data." }],
+                        content: [{ type: "text", text: noDataErrorMessage }],
+                        isError: true,
                     };
                 }
             }
             const trimmedPullRequest = trimPullRequest(pullRequest, true);
             if (!trimmedPullRequest) {
                 return {
-                    content: [{ type: "text", text: "Pull request created but API returned no data." }],
+                    content: [{ type: "text", text: noDataErrorMessage }],
+                    isError: true,
                 };
             }
             return {

package/dist/tools/wiki.js

@@ -201,9 +201,10 @@ function configureWikiTools(server, tokenProvider, connectionProvider, userAgent
                 if (!resolvedPath) {
                     resolvedPath = "/";
                 }
-                if (!resolvedProject || !resolvedWiki) {
-                    return { content: [{ type: "text", text: "Project and wikiIdentifier must be defined to fetch wiki page content." }], isError: true };
-                }
+                // resolvedProject and resolvedWiki are guaranteed to be defined here:
+                // - the url branch errors out in parseWikiUrl when project/wikiIdentifier are missing
+                // - the pair branch enforces both via the hasPair check above
+                // eslint-disable-next-line @typescript-eslint/no-non-null-assertion
                 const stream = await wikiApi.getPageText(resolvedProject, resolvedWiki, resolvedPath, undefined, undefined, true);
                 if (!stream) {
                     return { content: [{ type: "text", text: "No wiki page content found" }], isError: true };

package/dist/version.js

@@ -1 +1 @@
-export const packageVersion = "2.7.0-nightly.20260510";
+export const packageVersion = "2.7.0-nightly.20260512";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@azure-devops/mcp",
-  "version": "2.7.0-nightly.20260510",
+  "version": "2.7.0-nightly.20260512",
   "mcpName": "microsoft.com/azure-devops",
   "description": "MCP server for interacting with Azure DevOps",
   "license": "MIT",