UniFi MCP Server

Overview Schema Source Related Servers Discussions Admin

connector_network_put

Send a PUT request to a UniFi Network API sub-path through the Cloud Connector, with optional body, dry-run preview, and confirmation before execution.

Instructions

Proxy a PUT 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_put"
  }
}

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. It implies a mutating write via PUT, but it does not mention the required confirm parameter, the dry_run preview option, authentication needs, or the effect of the operation, leaving important safety behavior to the schema fields.

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?

The description is a single front-loaded sentence with no wasted words. It is efficient, though its brevity contributes to missing usage and behavioral context.

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?

For a six-parameter mutation proxy with no annotations, the description is under-specified. The output schema covers return values, but the description does not explain when to use this PUT tool, how confirm/dry_run affect execution, or how controller defaults apply.

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 the input schema already documents all six parameters, including confirm, dry_run, controller, body, path, and console_id. The description adds no parameter-specific meaning beyond what the schema provides, which is the baseline case for fully documented parameters.

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?

The description states a specific action and resource: proxy a PUT request to the Network Application via Cloud Connector. The HTTP method distinguishes it from sibling tools such as connector_network_post, connector_network_patch, connector_network_get, and connector_network_delete, though it does not explicitly name those alternatives.

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?

The description gives no explicit guidance on when to use this PUT proxy versus connector_network_patch or connector_network_post. PUT semantics imply replacement or update usage, but the agent must infer that without stated conditions or exclusions.

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

Deploy Server