unifi-network-mcp 0.3.0__tar.gz → 0.3.1__tar.gz

{unifi_network_mcp-0.3.0 → unifi_network_mcp-0.3.1}/.well-known/mcp-server.json

@@ -46,10 +46,14 @@
       "tool": "unifi_tool_index",
       "description": "Returns machine-readable list of all available tools with schemas"
     },
-    "async_operations": {
-      "start_tool": "unifi_async_start",
-      "status_tool": "unifi_async_status",
-      "description": "Background job execution for long-running operations"
+    "execution": {
+      "tool": "unifi_execute",
+      "description": "Execute any discovered tool synchronously"
+    },
+    "batch_operations": {
+      "start_tool": "unifi_batch",
+      "status_tool": "unifi_batch_status",
+      "description": "Parallel batch execution for bulk operations"
     }
   }
 }

{unifi_network_mcp-0.3.0 → unifi_network_mcp-0.3.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: unifi-network-mcp
-Version: 0.3.0
+Version: 0.3.1
 Summary: Unifi Network MCP Server
 License-File: LICENSE
 Requires-Python: >=3.13
@@ -45,7 +45,7 @@ A self-hosted [Model Context Protocol](https://github.com/modelcontextprotocol)
   * [Overview](#overview)
   * [Context Optimization](#context-optimization)
   * [Tool Index](#tool-index)
-  * [Async Operations](#async-operations)
+  * [Tool Execution](#tool-execution)
 * [Runtime Configuration](#runtime-configuration)
 * [Diagnostics (Advanced Logging)](#diagnostics-advanced-logging)
 * [Developer Console (Local Tool Tester)](#developer-console-local-tool-tester)
@@ -268,73 +268,73 @@ The server exposes a special `unifi_tool_index` tool that returns a complete lis
 - Dynamic client configuration
 - IDE autocomplete support
 
-### Async Operations
+### Tool Execution
 
-For long-running operations (device upgrades, bulk configuration changes), the server provides async job execution:
+The server provides two execution modes for discovered tools:
 
-**Start a background job:**
+**Single Tool Execution (synchronous):**
 ```json
 {
-  "name": "unifi_async_start",
+  "name": "unifi_execute",
   "arguments": {
-    "tool": "unifi_upgrade_device",
-    "arguments": {
-      "mac_address": "aa:bb:cc:dd:ee:ff",
-      "confirm": true
-    }
+    "tool": "unifi_list_clients",
+    "arguments": {}
   }
 }
 ```
 
-**Response:**
-```json
-{
-  "jobId": "af33b233cbdc860c"
-}
-```
+**Batch Execution (parallel, async):**
+
+For bulk operations or long-running tasks, use batch mode:
 
-**Check job status:**
 ```json
 {
-  "name": "unifi_async_status",
+  "name": "unifi_batch",
   "arguments": {
-    "jobId": "af33b233cbdc860c"
+    "operations": [
+      {"tool": "unifi_get_client_details", "arguments": {"mac": "aa:bb:cc:dd:ee:ff"}},
+      {"tool": "unifi_get_client_details", "arguments": {"mac": "11:22:33:44:55:66"}}
+    ]
   }
 }
 ```
 
-**Response (running):**
+**Response:**
 ```json
 {
-  "status": "running",
-  "started": 1234567890.123
+  "jobs": [
+    {"index": 0, "tool": "unifi_get_client_details", "jobId": "af33b233cbdc860c"},
+    {"index": 1, "tool": "unifi_get_client_details", "jobId": "bf44c344dcde971d"}
+  ],
+  "message": "Started 2 operation(s). Use unifi_batch_status to check progress."
 }
 ```
 
-**Response (completed):**
+**Check batch status:**
 ```json
 {
-  "status": "done",
-  "result": {...},
-  "started": 1234567890.123,
-  "finished": 1234567891.456
+  "name": "unifi_batch_status",
+  "arguments": {
+    "jobIds": ["af33b233cbdc860c", "bf44c344dcde971d"]
+  }
 }
 ```
 
-**Response (error):**
+**Response:**
 ```json
 {
-  "status": "error",
-  "error": "Device not found",
-  "started": 1234567890.123,
-  "finished": 1234567891.456
+  "jobs": [
+    {"jobId": "af33b233cbdc860c", "status": "done", "result": {...}},
+    {"jobId": "bf44c344dcde971d", "status": "done", "result": {...}}
+  ]
 }
 ```
 
 **Notes:**
+- Use `unifi_execute` for single operations (returns result directly)
+- Use `unifi_batch` + `unifi_batch_status` for parallel/bulk operations
 - Jobs are stored in-memory only (no persistence)
 - Job IDs are unique per server session
-- Failed jobs capture exception details in the `error` field
 
 ### Using with Claude Desktop
 
@@ -361,22 +361,32 @@ Practical examples showing programmatic usage:
 ```python
 from mcp import ClientSession, stdio_client
 
-# Query tool index
-result = await session.call_tool("unifi_tool_index", {})
+# Discover tools
+tools = await session.call_tool("unifi_tool_index", {})
+
+# Execute a single tool (returns result directly)
+result = await session.call_tool("unifi_execute", {
+    "tool": "unifi_list_clients",
+    "arguments": {}
+})
 
-# Use async jobs for long operations
-job = await session.call_tool("unifi_async_start", {
-    "tool": "unifi_upgrade_device",
-    "arguments": {"mac_address": "...", "confirm": True}
+# Batch execution for parallel operations
+batch = await session.call_tool("unifi_batch", {
+    "operations": [
+        {"tool": "unifi_get_client_details", "arguments": {"mac": "..."}},
+        {"tool": "unifi_get_device_details", "arguments": {"mac": "..."}}
+    ]
 })
 
-# Check job status
-status = await session.call_tool("unifi_async_status", {"jobId": job["jobId"]})
+# Check batch status
+status = await session.call_tool("unifi_batch_status", {
+    "jobIds": [j["jobId"] for j in batch["jobs"]]
+})
 ```
 
 **Three complete examples:**
 - `query_tool_index.py` - Discover available tools
-- `use_async_jobs.py` - Background job management
+- `use_async_jobs.py` - Batch operations and status checking
 - `programmatic_client.py` - Build custom Python clients
 
 See [`examples/python/README.md`](examples/python/README.md) for complete examples.
@@ -393,15 +403,18 @@ The server advertises its capabilities via an MCP identity file at [`.well-known
   "capabilities": {
     "tools": true,
     "tool_index": true,
-    "async_operations": true
+    "batch_operations": true
   },
   "features": {
     "tool_index": {
       "tool": "unifi_tool_index"
     },
-    "async_operations": {
-      "start_tool": "unifi_async_start",
-      "status_tool": "unifi_async_status"
+    "execution": {
+      "tool": "unifi_execute"
+    },
+    "batch_operations": {
+      "start_tool": "unifi_batch",
+      "status_tool": "unifi_batch_status"
     }
   }
 }
@@ -522,6 +535,43 @@ The server merges settings from **environment variables**, an optional `.env` fi
 | `UNIFI_CONTROLLER_TYPE` | Controller API path type: `auto` (detect), `proxy` (UniFi OS), `direct` (standalone). Default `auto` |
 | `UNIFI_MCP_HTTP_ENABLED` | Set `true` to enable optional HTTP SSE server (default `false`) |
 | `UNIFI_AUTO_CONFIRM` | Set `true` to auto-confirm all mutating operations (skips preview step). Ideal for workflow automation (n8n, Make, Zapier). Default `false` |
+| `UNIFI_TOOL_REGISTRATION_MODE` | Tool loading mode: `lazy` (default), `eager`, or `meta_only`. See [Context Optimization](#context-optimization) |
+| `UNIFI_ENABLED_CATEGORIES` | Comma-separated list of tool categories to load (eager mode). See table below |
+| `UNIFI_ENABLED_TOOLS` | Comma-separated list of specific tool names to register (eager mode) |
+
+### Tool Categories (for UNIFI_ENABLED_CATEGORIES)
+
+When using eager mode with category filtering, these are the valid category names:
+
+| Category | Description | Example Tools |
+|----------|-------------|---------------|
+| `clients` | Client listing, blocking, guest auth | `unifi_list_clients`, `unifi_block_client` |
+| `config` | Configuration management | - |
+| `devices` | Device listing, reboot, locate, upgrade | `unifi_list_devices`, `unifi_reboot_device` |
+| `events` | Events and alarms | `unifi_list_events`, `unifi_list_alarms` |
+| `firewall` | Firewall rules and groups | `unifi_list_firewall_rules`, `unifi_create_firewall_rule` |
+| `hotspot` | Vouchers for guest network | `unifi_list_vouchers`, `unifi_create_voucher` |
+| `network` | Network/VLAN management | `unifi_list_networks`, `unifi_create_network` |
+| `port_forwards` | Port forwarding rules | `unifi_list_port_forwards` |
+| `qos` | QoS/traffic shaping rules | `unifi_list_qos_rules`, `unifi_create_qos_rule` |
+| `routing` | Static routes (V1 API) | `unifi_list_routes`, `unifi_create_route` |
+| `stats` | Statistics and metrics | `unifi_get_client_stats`, `unifi_get_device_stats` |
+| `system` | System info, health, settings | `unifi_get_system_info`, `unifi_get_network_health` |
+| `traffic_routes` | Policy-based routing (V2 API) | `unifi_list_traffic_routes` |
+| `usergroups` | Bandwidth profiles/user groups | `unifi_list_usergroups`, `unifi_create_usergroup` |
+| `vpn` | VPN servers and clients | `unifi_list_vpn_servers`, `unifi_list_vpn_clients` |
+
+**Example usage:**
+```bash
+# Load only client and system tools
+export UNIFI_TOOL_REGISTRATION_MODE=eager
+export UNIFI_ENABLED_CATEGORIES=clients,system
+
+# Or load specific tools only
+export UNIFI_ENABLED_TOOLS=unifi_list_clients,unifi_list_devices,unifi_get_system_info
+```
+
+**Note:** Tools may also be filtered by the `permissions` section in config.yaml (e.g., `clients.update: false` blocks mutating client tools).
 
 ### Controller Type Detection
 
@@ -844,6 +894,37 @@ See [docs/permissions.md](docs/permissions.md) for complete documentation includ
 * `unifi_force_reconnect_client`
 * `unifi_authorize_guest`
 * `unifi_unauthorize_guest`
+* `unifi_set_client_ip_settings`
+
+### Events & Alarms
+
+* `unifi_list_events`
+* `unifi_list_alarms`
+* `unifi_archive_alarm`
+* `unifi_archive_all_alarms`
+* `unifi_get_event_types`
+
+### Routing (Static Routes)
+
+* `unifi_list_routes`
+* `unifi_get_route_details`
+* `unifi_create_route`
+* `unifi_update_route`
+* `unifi_list_active_routes`
+
+### Hotspot (Vouchers)
+
+* `unifi_list_vouchers`
+* `unifi_get_voucher_details`
+* `unifi_create_voucher`
+* `unifi_revoke_voucher`
+
+### User Groups
+
+* `unifi_list_usergroups`
+* `unifi_get_usergroup_details`
+* `unifi_create_usergroup`
+* `unifi_update_usergroup`
 
 ### Statistics & Alerts
 
@@ -1020,9 +1101,9 @@ uv run python devtools/dev_console.py
 
 # You'll see a menu of all tools including:
 # - unifi_tool_index (list all tools with schemas)
-# - unifi_async_start (start background jobs)
-# - unifi_async_status (check job status)
-# - All 60+ UniFi tools (clients, devices, networks, etc.)
+# - unifi_execute (run any discovered tool)
+# - unifi_batch / unifi_batch_status (parallel operations)
+# - All 80+ UniFi tools (clients, devices, networks, etc.)
 ```
 
 **4. Test with Python examples:**

{unifi_network_mcp-0.3.0 → unifi_network_mcp-0.3.1}/README.md

@@ -29,7 +29,7 @@ A self-hosted [Model Context Protocol](https://github.com/modelcontextprotocol)
   * [Overview](#overview)
   * [Context Optimization](#context-optimization)
   * [Tool Index](#tool-index)
-  * [Async Operations](#async-operations)
+  * [Tool Execution](#tool-execution)
 * [Runtime Configuration](#runtime-configuration)
 * [Diagnostics (Advanced Logging)](#diagnostics-advanced-logging)
 * [Developer Console (Local Tool Tester)](#developer-console-local-tool-tester)
@@ -252,73 +252,73 @@ The server exposes a special `unifi_tool_index` tool that returns a complete lis
 - Dynamic client configuration
 - IDE autocomplete support
 
-### Async Operations
+### Tool Execution
 
-For long-running operations (device upgrades, bulk configuration changes), the server provides async job execution:
+The server provides two execution modes for discovered tools:
 
-**Start a background job:**
+**Single Tool Execution (synchronous):**
 ```json
 {
-  "name": "unifi_async_start",
+  "name": "unifi_execute",
   "arguments": {
-    "tool": "unifi_upgrade_device",
-    "arguments": {
-      "mac_address": "aa:bb:cc:dd:ee:ff",
-      "confirm": true
-    }
+    "tool": "unifi_list_clients",
+    "arguments": {}
   }
 }
 ```
 
-**Response:**
-```json
-{
-  "jobId": "af33b233cbdc860c"
-}
-```
+**Batch Execution (parallel, async):**
+
+For bulk operations or long-running tasks, use batch mode:
 
-**Check job status:**
 ```json
 {
-  "name": "unifi_async_status",
+  "name": "unifi_batch",
   "arguments": {
-    "jobId": "af33b233cbdc860c"
+    "operations": [
+      {"tool": "unifi_get_client_details", "arguments": {"mac": "aa:bb:cc:dd:ee:ff"}},
+      {"tool": "unifi_get_client_details", "arguments": {"mac": "11:22:33:44:55:66"}}
+    ]
   }
 }
 ```
 
-**Response (running):**
+**Response:**
 ```json
 {
-  "status": "running",
-  "started": 1234567890.123
+  "jobs": [
+    {"index": 0, "tool": "unifi_get_client_details", "jobId": "af33b233cbdc860c"},
+    {"index": 1, "tool": "unifi_get_client_details", "jobId": "bf44c344dcde971d"}
+  ],
+  "message": "Started 2 operation(s). Use unifi_batch_status to check progress."
 }
 ```
 
-**Response (completed):**
+**Check batch status:**
 ```json
 {
-  "status": "done",
-  "result": {...},
-  "started": 1234567890.123,
-  "finished": 1234567891.456
+  "name": "unifi_batch_status",
+  "arguments": {
+    "jobIds": ["af33b233cbdc860c", "bf44c344dcde971d"]
+  }
 }
 ```
 
-**Response (error):**
+**Response:**
 ```json
 {
-  "status": "error",
-  "error": "Device not found",
-  "started": 1234567890.123,
-  "finished": 1234567891.456
+  "jobs": [
+    {"jobId": "af33b233cbdc860c", "status": "done", "result": {...}},
+    {"jobId": "bf44c344dcde971d", "status": "done", "result": {...}}
+  ]
 }
 ```
 
 **Notes:**
+- Use `unifi_execute` for single operations (returns result directly)
+- Use `unifi_batch` + `unifi_batch_status` for parallel/bulk operations
 - Jobs are stored in-memory only (no persistence)
 - Job IDs are unique per server session
-- Failed jobs capture exception details in the `error` field
 
 ### Using with Claude Desktop
 
@@ -345,22 +345,32 @@ Practical examples showing programmatic usage:
 ```python
 from mcp import ClientSession, stdio_client
 
-# Query tool index
-result = await session.call_tool("unifi_tool_index", {})
+# Discover tools
+tools = await session.call_tool("unifi_tool_index", {})
+
+# Execute a single tool (returns result directly)
+result = await session.call_tool("unifi_execute", {
+    "tool": "unifi_list_clients",
+    "arguments": {}
+})
 
-# Use async jobs for long operations
-job = await session.call_tool("unifi_async_start", {
-    "tool": "unifi_upgrade_device",
-    "arguments": {"mac_address": "...", "confirm": True}
+# Batch execution for parallel operations
+batch = await session.call_tool("unifi_batch", {
+    "operations": [
+        {"tool": "unifi_get_client_details", "arguments": {"mac": "..."}},
+        {"tool": "unifi_get_device_details", "arguments": {"mac": "..."}}
+    ]
 })
 
-# Check job status
-status = await session.call_tool("unifi_async_status", {"jobId": job["jobId"]})
+# Check batch status
+status = await session.call_tool("unifi_batch_status", {
+    "jobIds": [j["jobId"] for j in batch["jobs"]]
+})
 ```
 
 **Three complete examples:**
 - `query_tool_index.py` - Discover available tools
-- `use_async_jobs.py` - Background job management
+- `use_async_jobs.py` - Batch operations and status checking
 - `programmatic_client.py` - Build custom Python clients
 
 See [`examples/python/README.md`](examples/python/README.md) for complete examples.
@@ -377,15 +387,18 @@ The server advertises its capabilities via an MCP identity file at [`.well-known
   "capabilities": {
     "tools": true,
     "tool_index": true,
-    "async_operations": true
+    "batch_operations": true
   },
   "features": {
     "tool_index": {
       "tool": "unifi_tool_index"
     },
-    "async_operations": {
-      "start_tool": "unifi_async_start",
-      "status_tool": "unifi_async_status"
+    "execution": {
+      "tool": "unifi_execute"
+    },
+    "batch_operations": {
+      "start_tool": "unifi_batch",
+      "status_tool": "unifi_batch_status"
     }
   }
 }
@@ -506,6 +519,43 @@ The server merges settings from **environment variables**, an optional `.env` fi
 | `UNIFI_CONTROLLER_TYPE` | Controller API path type: `auto` (detect), `proxy` (UniFi OS), `direct` (standalone). Default `auto` |
 | `UNIFI_MCP_HTTP_ENABLED` | Set `true` to enable optional HTTP SSE server (default `false`) |
 | `UNIFI_AUTO_CONFIRM` | Set `true` to auto-confirm all mutating operations (skips preview step). Ideal for workflow automation (n8n, Make, Zapier). Default `false` |
+| `UNIFI_TOOL_REGISTRATION_MODE` | Tool loading mode: `lazy` (default), `eager`, or `meta_only`. See [Context Optimization](#context-optimization) |
+| `UNIFI_ENABLED_CATEGORIES` | Comma-separated list of tool categories to load (eager mode). See table below |
+| `UNIFI_ENABLED_TOOLS` | Comma-separated list of specific tool names to register (eager mode) |
+
+### Tool Categories (for UNIFI_ENABLED_CATEGORIES)
+
+When using eager mode with category filtering, these are the valid category names:
+
+| Category | Description | Example Tools |
+|----------|-------------|---------------|
+| `clients` | Client listing, blocking, guest auth | `unifi_list_clients`, `unifi_block_client` |
+| `config` | Configuration management | - |
+| `devices` | Device listing, reboot, locate, upgrade | `unifi_list_devices`, `unifi_reboot_device` |
+| `events` | Events and alarms | `unifi_list_events`, `unifi_list_alarms` |
+| `firewall` | Firewall rules and groups | `unifi_list_firewall_rules`, `unifi_create_firewall_rule` |
+| `hotspot` | Vouchers for guest network | `unifi_list_vouchers`, `unifi_create_voucher` |
+| `network` | Network/VLAN management | `unifi_list_networks`, `unifi_create_network` |
+| `port_forwards` | Port forwarding rules | `unifi_list_port_forwards` |
+| `qos` | QoS/traffic shaping rules | `unifi_list_qos_rules`, `unifi_create_qos_rule` |
+| `routing` | Static routes (V1 API) | `unifi_list_routes`, `unifi_create_route` |
+| `stats` | Statistics and metrics | `unifi_get_client_stats`, `unifi_get_device_stats` |
+| `system` | System info, health, settings | `unifi_get_system_info`, `unifi_get_network_health` |
+| `traffic_routes` | Policy-based routing (V2 API) | `unifi_list_traffic_routes` |
+| `usergroups` | Bandwidth profiles/user groups | `unifi_list_usergroups`, `unifi_create_usergroup` |
+| `vpn` | VPN servers and clients | `unifi_list_vpn_servers`, `unifi_list_vpn_clients` |
+
+**Example usage:**
+```bash
+# Load only client and system tools
+export UNIFI_TOOL_REGISTRATION_MODE=eager
+export UNIFI_ENABLED_CATEGORIES=clients,system
+
+# Or load specific tools only
+export UNIFI_ENABLED_TOOLS=unifi_list_clients,unifi_list_devices,unifi_get_system_info
+```
+
+**Note:** Tools may also be filtered by the `permissions` section in config.yaml (e.g., `clients.update: false` blocks mutating client tools).
 
 ### Controller Type Detection
 
@@ -828,6 +878,37 @@ See [docs/permissions.md](docs/permissions.md) for complete documentation includ
 * `unifi_force_reconnect_client`
 * `unifi_authorize_guest`
 * `unifi_unauthorize_guest`
+* `unifi_set_client_ip_settings`
+
+### Events & Alarms
+
+* `unifi_list_events`
+* `unifi_list_alarms`
+* `unifi_archive_alarm`
+* `unifi_archive_all_alarms`
+* `unifi_get_event_types`
+
+### Routing (Static Routes)
+
+* `unifi_list_routes`
+* `unifi_get_route_details`
+* `unifi_create_route`
+* `unifi_update_route`
+* `unifi_list_active_routes`
+
+### Hotspot (Vouchers)
+
+* `unifi_list_vouchers`
+* `unifi_get_voucher_details`
+* `unifi_create_voucher`
+* `unifi_revoke_voucher`
+
+### User Groups
+
+* `unifi_list_usergroups`
+* `unifi_get_usergroup_details`
+* `unifi_create_usergroup`
+* `unifi_update_usergroup`
 
 ### Statistics & Alerts
 
@@ -1004,9 +1085,9 @@ uv run python devtools/dev_console.py
 
 # You'll see a menu of all tools including:
 # - unifi_tool_index (list all tools with schemas)
-# - unifi_async_start (start background jobs)
-# - unifi_async_status (check job status)
-# - All 60+ UniFi tools (clients, devices, networks, etc.)
+# - unifi_execute (run any discovered tool)
+# - unifi_batch / unifi_batch_status (parallel operations)
+# - All 80+ UniFi tools (clients, devices, networks, etc.)
 ```
 
 **4. Test with Python examples:**

{unifi_network_mcp-0.3.0 → unifi_network_mcp-0.3.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "unifi-network-mcp"
-version = "0.3.0"
+version = "0.3.1"
 description = "Unifi Network MCP Server"
 readme = "README.md"
 requires-python = ">=3.13"

{unifi_network_mcp-0.3.0 → unifi_network_mcp-0.3.1}/src/config/config.yaml

@@ -12,13 +12,43 @@ server:
   port: 3000
   log_level: INFO
 
-  # Tool registration mode (New in v0.2.0)
+  # Tool registration mode
   # Options: eager, lazy, meta_only
-  # - eager: Register all 67 tools immediately (~5,000 tokens) - Best for dev console, automation
-  # - lazy: Register 3 meta-tools, load others on-demand (~225 tokens) - RECOMMENDED for LLMs
-  # - meta_only: Register only 3 meta-tools, manual discovery (~225 tokens) - Maximum control
+  # - eager: Register all tools immediately - Best for dev console, automation
+  # - lazy: Register meta-tools, load others on-demand - RECOMMENDED for LLMs
+  # - meta_only: Register only meta-tools, manual discovery - Maximum context savings
   tool_registration_mode: ${oc.env:UNIFI_TOOL_REGISTRATION_MODE,lazy}
 
+  # Tool filtering (optional, for eager mode)
+  # Use these to limit which tools are registered for automation/n8n workflows
+  #
+  # enabled_categories: Only load tools from these categories (module names in src/tools/)
+  #   Valid values:
+  #     - clients        # Client listing, blocking, guest auth
+  #     - config         # Configuration management
+  #     - devices        # Device listing, reboot, locate, upgrade
+  #     - events         # Events and alarms
+  #     - firewall       # Firewall rules and groups
+  #     - hotspot        # Vouchers for guest network
+  #     - network        # Network/VLAN management
+  #     - port_forwards  # Port forwarding rules
+  #     - qos            # QoS/traffic shaping rules
+  #     - routing        # Static routes (V1 API)
+  #     - stats          # Statistics and metrics
+  #     - system         # System info, health, settings
+  #     - traffic_routes # Policy-based routing (V2 API)
+  #     - usergroups     # Bandwidth profiles/user groups
+  #     - vpn            # VPN servers and clients
+  #   Example: "clients,devices,system" or ["clients", "devices", "system"]
+  #
+  # enabled_tools: Only register these specific tools (use with enabled_categories or alone)
+  #   Example: "unifi_list_clients,unifi_list_devices" or ["unifi_list_clients", "unifi_list_devices"]
+  #
+  # Note: Tools may also be filtered by the permissions section below (e.g., update: false)
+  # If neither is set, all tools are registered (default behavior)
+  enabled_categories: ${oc.env:UNIFI_ENABLED_CATEGORIES,null}
+  enabled_tools: ${oc.env:UNIFI_ENABLED_TOOLS,null}
+
   http:
     enabled: ${oc.env:UNIFI_MCP_HTTP_ENABLED,false}
   diagnostics: