@azure-devops/mcp 2.0.0-nightly.20250825 → 2.0.0-nightly.20250827

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -15,10 +15,11 @@ This TypeScript project provides a **local** MCP server for Azure DevOps, enabli
15
15
  2. [🏆 Expectations](#-expectations)
16
16
  3. [⚙️ Supported Tools](#️-supported-tools)
17
17
  4. [🔌 Installation & Getting Started](#-installation--getting-started)
18
- 5. [📝 Troubleshooting](#-troubleshooting)
19
- 6. [🎩 Examples & Best Practices](#-examples--best-practices)
20
- 7. [🙋‍♀️ Frequently Asked Questions](#️-frequently-asked-questions)
21
- 8. [📌 Contributing](#-contributing)
18
+ 5. [🌏 Using Domains](#-using-domains)
19
+ 6. [📝 Troubleshooting](#-troubleshooting)
20
+ 7. [🎩 Examples & Best Practices](#-examples--best-practices)
21
+ 8. [🙋‍♀️ Frequently Asked Questions](#️-frequently-asked-questions)
22
+ 9. [📌 Contributing](#-contributing)
22
23
 
23
24
  ## 📺 Overview
24
25
 
@@ -242,6 +243,37 @@ Open GitHub Copilot Chat and try a prompt like `List ADO projects`.
242
243
 
243
244
  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.
244
245
 
246
+ ## 🌏 Using Domains
247
+
248
+ 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.
249
+
250
+ For example, use `"-d", "core", "work", "work-items"` to load only Work Item related tools (see the example below).
251
+
252
+ ```json
253
+ {
254
+ "inputs": [
255
+ {
256
+ "id": "ado_org",
257
+ "type": "promptString",
258
+ "description": "Azure DevOps organization name (e.g. 'contoso')"
259
+ }
260
+ ],
261
+ "servers": {
262
+ "ado": {
263
+ "type": "stdio",
264
+ "command": "mcp-server-azuredevops",
265
+ "args": ["${input:ado_org}", "-d", "core", "work", "work-items"]
266
+ }
267
+ }
268
+ }
269
+ ```
270
+
271
+ Domains that are available are: `core`, `work`, `work-items`, `search`, `test-plans`, `repositories`, `wiki`, `builds`, `releases`, `advanced-security`
272
+
273
+ We recommend that you always enable `core` tools so that you can fetch project level information.
274
+
275
+ > By default all domains are loaded
276
+
245
277
  ## 📝 Troubleshooting
246
278
 
247
279
  See the [Troubleshooting guide](./docs/TROUBLESHOOTING.md) for help with common issues and logging.
package/dist/version.js CHANGED
@@ -1 +1 @@
1
- export const packageVersion = "2.0.0-nightly.20250825";
1
+ export const packageVersion = "2.0.0-nightly.20250827";
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@azure-devops/mcp",
3
- "version": "2.0.0-nightly.20250825",
3
+ "version": "2.0.0-nightly.20250827",
4
4
  "description": "MCP server for interacting with Azure DevOps",
5
5
  "license": "MIT",
6
6
  "author": "Microsoft Corporation",