Users/danhellem/readme update for domains 1 (#468)

This pull request updates documentation and test configuration to
introduce and clarify the concept of "Domains" for the Azure DevOps MCP
Server. The main goal is to help users selectively enable only the
toolsets they need, improving usability and performance. The README
gains a new section explaining Domains, and the integration test
configuration file is removed to avoid confusion and outdated examples.

**Documentation improvements:**

* Added a new "Using Domains" section to the `README.md`, explaining how
to use the `-d` argument to selectively enable named groups of related
tools (domains) for the MCP Server, including example configuration and
a list of available domains.
* Updated the table of contents in `README.md` to include the new "Using
Domains" section, shifting the order of subsequent sections.

**Test configuration cleanup:**

* Removed the outdated `intTest/domains/mcp.json` file, which contained
an example of domain configuration for integration tests.

## GitHub issue number
N/A

## **Associated Risks**

N/A

## ✅ **PR Checklist**

- [x] **I have read the [contribution
guidelines](https://github.com/microsoft/azure-devops-mcp/blob/main/CONTRIBUTING.md)**
- [x] **I have read the [code of conduct
guidelines](https://github.com/microsoft/azure-devops-mcp/blob/main/CODE_OF_CONDUCT.md)**
- [x] Title of the pull request is clear and informative.
- [x] 👌 Code hygiene
- [x] 🔭 Telemetry added, updated, or N/A
- [x] 📄 Documentation added, updated, or N/A
- [x] 🛡️ Automated tests added, or N/A

## 🧪 **How did you test it?**

Manual and Copilot review

Author: danhellem

README.md

@@ -15,10 +15,11 @@ This TypeScript project provides a **local** MCP server for Azure DevOps, enabli
 2. [🏆 Expectations](#-expectations)
 3. [⚙️ Supported Tools](#️-supported-tools)
 4. [🔌 Installation & Getting Started](#-installation--getting-started)
-5. [📝 Troubleshooting](#-troubleshooting)
-6. [🎩 Examples & Best Practices](#-examples--best-practices)
-7. [🙋‍♀️ Frequently Asked Questions](#️-frequently-asked-questions)
-8. [📌 Contributing](#-contributing)
+5. [🌏 Using Domains](#-using-domains)
+6. [📝 Troubleshooting](#-troubleshooting)
+7. [🎩 Examples & Best Practices](#-examples--best-practices)
+8. [🙋‍♀️ Frequently Asked Questions](#️-frequently-asked-questions)
+9. [📌 Contributing](#-contributing)
 
 ## 📺 Overview
 
@@ -242,6 +243,37 @@ Open GitHub Copilot Chat and try a prompt like `List ADO projects`.
 
 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
+
+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.
+
+For example, use `"-d", "core", "work", "work-items"` to load only Work Item related tools (see the example below).
+
+```json
+{
+  "inputs": [
+    {
+      "id": "ado_org",
+      "type": "promptString",
+      "description": "Azure DevOps organization name  (e.g. 'contoso')"
+    }
+  ],
+  "servers": {
+    "ado": {
+      "type": "stdio",
+      "command": "mcp-server-azuredevops",
+      "args": ["${input:ado_org}", "-d", "core", "work", "work-items"]
+    }
+  }
+}
+```
+
+Domains that are available are: `core`, `work`, `work-items`, `search`, `test-plans`, `repositories`, `wiki`, `builds`, `releases`, `advanced-security`
+
+We recommend that you always enable `core` tools so that you can fetch project level information.
+
+> By default all domains are loaded
+
 ## 📝 Troubleshooting
 
 See the [Troubleshooting guide](./docs/TROUBLESHOOTING.md) for help with common issues and logging.

docs/TROUBLESHOOTING.md

@@ -23,7 +23,9 @@
    If tools do not appear, click "Add Context" in Agent Mode and ensure all tools starting with `ado_` are selected.
 
 4. **Too Many Tools Selected (Over 128 Limit)**
-   VS Code supports a maximum of 128 tools. If you exceed this limit, ensure you do not have multiple MCP Servers running. Check both your project's `mcp.json` and your VS Code `settings.json` to confirm that the MCP Server is configured in only one location—not both.
+   Some tools have a default maximum limot of 128 tools. If you exceed this limit, ensure you do not have multiple MCP Servers running. Check both your project's `mcp.json` and your VS Code `settings.json` to confirm that the MCP Server is configured in only one location—not both.
+
+   You can also use [Domains](../README.md?tab=readme-ov-file#-using-domains) as a way to limit the number of tools you load for the Azure DevOps MCP Server.
 
 ## Project-Specific Issues