UniFi MCP Server

Overview Schema Source Related Servers Discussions Admin

connector_network_patch

Send a PATCH request to the UniFi Network Application through the Cloud Connector to update network configuration, with optional dry-run preview and confirmation before execution.

Instructions

Proxy a PATCH request to the Network Application via Cloud Connector.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "console_id": "<console_id>",
      "path": "<path>"
    },
    "name": "connector_network_patch"
  }
}

Input Schema

Name	Required	Description
`body`	No	Optional request body
`path`	Yes	Network API sub-path
`confirm`	No	Must be True to execute
`dry_run`	No	Preview without sending
`console_id`	Yes	UniFi console/host identifier
`controller`	No	Controller to run against (see list_controllers). Defaults to the controller chosen with select_controller, then the server default.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.6.4Oct 27, 2026

addedInput schema / properties / body / description
```
Added value: +"Optional request body"
```
addedInput schema / properties / confirm / description
```
Added value: +"Must be True to execute"
```
addedInput schema / properties / console_id / description
```
Added value: +"UniFi console/host identifier"
```
addedInput schema / properties / dry_run / description
```
Added value: +"Preview without sending"
```
addedInput schema / properties / path / description
```
Added value: +"Network API sub-path"
```
removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties

Added value: +{
+  "result": {
+    "anyOf": [
+      {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      {
+        "items": {},
+        "type": "array"
+      }
+    ]
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "result"
+]
```
addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```

Changed1 schema field changedv0.6.0Oct 12, 2026

addedInput schema / properties / controller

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Controller to run against (see list_controllers). Defaults to the controller chosen with select_controller, then the server default."
+}

First observedv0.2.0Jun 27, 2026

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about the mutation being gated on confirm=True, the existence of a dry_run preview, permission/auth requirements, or what happens on failure. 'PATCH' implies a partial mutation but the risk profile and the preview-then-commit protocol are left undisclosed in prose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, so nothing is wasted. It is efficient but so sparse that its brevity reflects under-specification rather than disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a mutating proxy tool with no annotations and six parameters in a large sibling family; the description does not mention the confirm gate, the dry_run preview, or the controller-resolution chain (select_controller → server default), all of which are critical to calling it correctly. The presence of an output schema excuses it from explaining return values, but the omission of the safety flow is a real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all six parameters (including confirm, dry_run, and controller resolution via list_controllers/select_controller) are already documented in the schema. The description adds no meaning beyond that, which is acceptable at the baseline but not better.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (proxy a PATCH request) and resource (Network Application via Cloud Connector), which distinguishes it from the sibling HTTP-method variants connector_network_get/post/put/delete. However, it never explains what a 'Network Application sub-path' is or how PATCH differs semantically from the sibling connector_network_put, so the differentiation relies entirely on the reader's knowledge of HTTP verbs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to reach for this tool versus the POST/PUT/DELETE siblings, and no guidance on the confirm/dry_run workflow that the schema implies is mandatory for execution. The agent must infer everything from the name and parameter defaults.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server