@azure-devops/mcp 2.9.0-nightly.20260813 → 2.9.0-nightly.20260814

package/README.md

@@ -1,32 +1,32 @@
-# ⭐ Azure DevOps MCP Server
+# Azure DevOps MCP Server
 
 > [!WARNING]
 > We recently completed a full tool consolidation that includes renaming of existing tools. Please see the [Toolset documentation](docs/TOOLSET.md) for the complete list of new tool names.
 >
 > If this is a breaking change for your agents or skills, you can temporarily pin the version to `@azure-devops/mcp@2.8.1`
 
-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.
+This project gives AI agents access to Azure DevOps through the Model Context Protocol (MCP). Use the hosted remote server for the simplest setup, or run the local server when you need a `stdio` connection.
 
-## 📄 Table of Contents
+## Table of Contents
 
 > [!IMPORTANT]
 > We recommend using the [Remote MCP Server](https://learn.microsoft.com/en-us/azure/devops/mcp-server/remote-mcp-server) instead of this local server. It requires no installation and gets new features first.
 >
-> [Learn more](#-remote-mcp-server-recommended)
-
-1. [📺 Overview](#-overview)
-2. [🏆 Expectations](#-expectations)
-3. [🚀 Remote MCP Server (Recommended)](#-remote-mcp-server-recommended)
-4. [⚙️ Supported Tools](#️-supported-tools)
-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)
-11. [📌 Contributing](#-contributing)
-
-## 📺 Overview
+> [Learn more](#remote-mcp-server-recommended)
+
+1. [Overview](#overview)
+2. [Design](#design)
+3. [Remote MCP Server (Recommended)](#remote-mcp-server-recommended)
+4. [Supported Tools](#supported-tools)
+5. [Local MCP Server Installation (Optional)](#local-mcp-server-installation-optional)
+6. [Using Domains (Local Server)](#using-domains-local-server)
+7. [Project and Team Defaults (Local Server)](#project-and-team-defaults-local-server)
+8. [Troubleshooting](#troubleshooting)
+9. [Examples and Best Practices](#examples-and-best-practices)
+10. [Frequently Asked Questions](#frequently-asked-questions)
+11. [Contributing](#contributing)
+
+## Overview
 
 The Azure DevOps MCP Server brings Azure DevOps context to your agents. Try prompts like:
 
@@ -43,23 +43,21 @@ The Azure DevOps MCP Server brings Azure DevOps context to your agents. Try prom
 - "Update the wiki page '/Getting Started' with new onboarding instructions"
 - "Get the content of the wiki page '/API/Authentication' from the Documentation wiki"
 
-## 🏆 Expectations
+## Design
 
-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.
+Each tool handles a focused Azure DevOps task. The server provides a thin layer over the REST APIs, while the AI agent handles higher-level reasoning.
 
-## 🚀 Remote MCP Server (Recommended)
+## Remote MCP Server (Recommended)
 
 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).
 
-Over time, the Remote MCP Server will replace this local MCP Server. We will continue to support the local server for now, but future investments will primarily focus on the remote experience.
-
-We encourage all users of the local MCP Server to begin migrating to the Remote MCP Server.
+The remote server will eventually replace the local server. The local server remains supported, but new development will focus on the remote server. Existing local server users should begin planning their migration.
 
 If you encounter issues with tools, need support, or have a feature request, you can report an issue using the [Remote MCP Server issue template](https://github.com/microsoft/azure-devops-mcp/issues/new?template=remote-mcp-server-issue.md). During the preview period, we will track Remote MCP Server issues through this repository.
 
-### Quick start with `.vscode/mcp.json`
+### Quick Start
 
-Use this configuration to connect directly to the Azure DevOps-hosted endpoint using streamable HTTP transport:
+Create `.vscode/mcp.json` in your project and add this configuration. Replace `{organization}` with your Azure DevOps organization name.
 
 ```json
 {
@@ -73,42 +71,35 @@ Use this configuration to connect directly to the Azure DevOps-hosted endpoint u
 }
 ```
 
-See [documentation](https://learn.microsoft.com/en-us/azure/devops/mcp-server/remote-mcp-server?view=azure-devops#mcpjson-configuration) for additional configuration options.
+See the [remote server configuration documentation](https://learn.microsoft.com/en-us/azure/devops/mcp-server/remote-mcp-server?view=azure-devops#mcpjson-configuration) for more 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
+## Supported Tools
 
 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).
+For the complete list of local tools, see [TOOLSET.md](./docs/TOOLSET.md).
 
-## 🔌 Local MCP Server Installation (Optional)
+## 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.
 
-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, Codex, Claude Code, Cursor, Opencode, and Kilocode.
+These steps use Visual Studio Code and GitHub Copilot. For other supported clients, including Visual Studio 2022, Codex, Claude Code, Cursor, OpenCode, and Kilo Code, see the [getting started guide](./docs/GETTINGSTARTED.md).
 
 ### Prerequisites
 
-1. Install [VS Code](https://code.visualstudio.com/download) or [VS Code Insiders](https://code.visualstudio.com/insiders)
-2. Install [Node.js](https://nodejs.org/en/download) 20+
-3. Open VS Code in an empty folder
+1. Install [VS Code](https://code.visualstudio.com/download) or [VS Code Insiders](https://code.visualstudio.com/insiders).
+2. Install [Node.js 20 or later](https://nodejs.org/en/download).
+3. Open your project in VS Code.
 
 ### Installation
 
-#### 🧨 Install from Public Feed
-
-This installation method is the easiest for all users of Visual Studio Code.
-
-🎥 [Watch this quick start video to get up and running in under two minutes!](https://youtu.be/EUmFM6qXoYk)
-
-##### Steps
+#### Install from npm
 
-In your project, add a `.vscode\mcp.json` file with the following content:
+1. Create `.vscode/mcp.json` in your project.
+2. Add this configuration:
 
 ```json
 {
@@ -129,49 +120,24 @@ In your project, add a `.vscode\mcp.json` file with the following content:
 }
 ```
 
-🔥 To stay up to date with the latest features, you can use our nightly builds. Simply update your `mcp.json` configuration to use `@azure-devops/mcp@next`. Here is an updated example:
+3. Save the file, then start the `ado` server from the MCP view in VS Code.
+4. Open GitHub Copilot Chat and switch to [Agent mode](https://code.visualstudio.com/blogs/2025/02/24/introducing-copilot-agent-mode).
+5. Select the Azure DevOps tools, then try a prompt such as `List ADO projects`.
+6. When prompted, sign in with a Microsoft account that has access to the selected Azure DevOps organization.
 
-```json
-{
-  "inputs": [
-    {
-      "id": "ado_org",
-      "type": "promptString",
-      "description": "Azure DevOps organization name  (e.g. 'contoso')"
-    }
-  ],
-  "servers": {
-    "ado": {
-      "type": "stdio",
-      "command": "npx",
-      "args": ["-y", "@azure-devops/mcp@next", "${input:ado_org}"]
-    }
-  }
-}
-```
-
-Save the file, then click 'Start'.
-
-![start mcp server](./docs/media/start-mcp-server.gif)
-
-In chat, switch to [Agent Mode](https://code.visualstudio.com/blogs/2025/02/24/introducing-copilot-agent-mode).
+To use nightly builds, replace `@azure-devops/mcp` with `@azure-devops/mcp@next` in the configuration.
 
-Click "Select Tools" and choose the available tools.
+For better tool selection, add `.github/copilot-instructions.md` to your project with this instruction:
 
-![configure mcp server tools](./docs/media/configure-mcp-server-tools.gif)
-
-Open GitHub Copilot Chat and try a prompt like `List ADO projects`. The first time an ADO tool is executed browser will open prompting to login with your Microsoft account. Please ensure you are using credentials matching selected Azure DevOps organization.
-
-> 💥 We strongly recommend creating a `.github\copilot-instructions.md` in your project. This will enhance your experience using the Azure DevOps MCP Server with GitHub Copilot Chat.
-> To start, just include "`This project uses Azure DevOps. Always check to see if the Azure DevOps MCP server has a tool relevant to the user's request`" in your copilot instructions file.
-
-See the [getting started documentation](./docs/GETTINGSTARTED.md) to use our MCP Server with other tools such as Visual Studio 2022, Codex, Claude Code, and Cursor.
+```text
+This project uses Azure DevOps. Always check whether the Azure DevOps MCP server has a tool relevant to the user's request.
+```
 
-## 🌏 Using Domains (local)
+## Using Domains (Local Server)
 
-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.
+The local server includes many tools. Domains let you load only the tool groups you need, which keeps the tool list manageable and helps clients with tool limits. Available domains are `core`, `work`, `work-items`, `search`, `test-plans`, `repositories`, `wiki`, `pipelines`, and `advanced-security`.
 
-For example, use `"-d", "core", "work", "work-items"` to load only Work Item related tools (see the example below).
+Add `-d` followed by the domains to the server arguments. For example, this configuration loads only work item-related tools:
 
 ```json
 {
@@ -192,15 +158,13 @@ For example, use `"-d", "core", "work", "work-items"` to load only Work Item rel
 }
 ```
 
-Domains that are available are: `core`, `work`, `work-items`, `search`, `test-plans`, `repositories`, `wiki`, `pipelines`, `advanced-security`
+Always include `core` so the agent can retrieve project information.
 
-We recommend that you always enable `core` tools so that you can fetch project level information.
+> If you omit `-d`, the server loads all domains.
 
-> By default all domains are loaded
+## Project and Team Defaults (Local Server)
 
-## 🐥 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.
+Set default Azure DevOps project and team values in `.vscode/mcp.json` so tools can skip selection prompts.
 
 ### Example `.vscode/mcp.json`
 
@@ -220,43 +184,37 @@ You can also configure default Azure DevOps project and team values from `.vscod
 }
 ```
 
-## 📝 Troubleshooting
+## Troubleshooting
 
 See the [Troubleshooting guide](./docs/TROUBLESHOOTING.md) for help with common issues and logging.
 
-## 🎩 Examples & Best Practices
-
-Explore example prompts in our [Examples documentation](./docs/EXAMPLES.md).
+## Examples
 
-For best practices and tips to enhance your experience with the MCP Server, refer to the [How-To guide](./docs/HOWTO.md).
+See the [examples](./docs/EXAMPLES.md) for sample prompts.
 
-## 🙋‍♀️ Frequently Asked Questions
+## Frequently Asked Questions
 
 For answers to common questions about the Azure DevOps MCP Server, see the [Frequently Asked Questions](./docs/FAQ.md).
 
-## 📌 Contributing
+## Contributing
 
-We welcome contributions! During preview, please file issues for bugs, enhancements, or documentation improvements.
+We welcome contributions. During preview, file issues for bugs, enhancements, or documentation improvements.
 
 See our [Contributions Guide](./CONTRIBUTING.md) for:
 
-- 🛠️ Development setup
-- ✨ Adding new tools
-- 📝 Code style & testing
-- 🔄 Pull request process
+- Development setup
+- Adding new tools
+- Code style and testing
+- Pull request process
 
-> ⚠️ Please read the [Contributions Guide](./CONTRIBUTING.md) before creating a pull request.
+Read the [Contributions Guide](./CONTRIBUTING.md) before creating a pull request.
 
-## 🤝 Code of Conduct
+## Code of Conduct
 
 This project follows the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
 For questions, see the [FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [open@microsoft.com](mailto:open@microsoft.com).
 
-## 📈 Project Stats
-
-[![Star History Chart](https://api.star-history.com/svg?repos=microsoft/azure-devops-mcp&type=Date)](https://star-history.com/#microsoft/azure-devops-mcp)
-
-## 🏆 Hall of Fame
+## Hall of Fame
 
 Thanks to all contributors who make this project awesome! ❤️
 

package/dist/version.js

@@ -1 +1 @@
-export const packageVersion = "2.9.0-nightly.20260813";
+export const packageVersion = "2.9.0-nightly.20260814";

package/package.json

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