UniFi MCP Server

Overview Schema Source Related Servers Discussions Admin

connector_network_get

Proxies a GET request to the UniFi Network Application through the Cloud Connector and returns the raw response for console-specific API paths.

Instructions

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

Forwards the request to https://api.ui.com/v1/connector/consoles/{console_id}/proxy/network/{path} and returns the raw response.

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_get"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Network API sub-path, e.g. ``api/s/default/stat/device``
`params`	No	Optional query parameters
`console_id`	Yes	UniFi console/host identifier (from list_hosts)
`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.

Changed7 schema fields changedv0.6.4Oct 27, 2026

addedInput schema / properties / console_id / description

Added value: +"UniFi console/host identifier (from list_hosts)"

addedInput schema / properties / params / description
```
Added value: +"Optional query parameters"
```

addedInput schema / properties / path / description

Added value: +"Network API sub-path, e.g. ``api/s/default/stat/device``"

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

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that this is a read-only GET proxied through Cloud Connector and that the raw upstream response is returned verbatim. It does not cover authentication/permission requirements, error or non-2xx behavior, rate limits, or whether the proxy passes through the console's own authorization constraints.

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?

Two short sentences plus the URL template; the core action is front-loaded and nothing is padding. The embedded URL is dense but it is the most information-rich part for correct invocation.

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

Completeness3/5

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

An output schema exists, so return-value description is unnecessary, and the proxy mechanics are covered. For a low-level passthrough tool with zero annotations, however, guidance on failure modes, permissions, and path formatting (leading slash) is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the URL template adds real value by showing precisely how console_id and path are interpolated (`/consoles/{console_id}/proxy/network/{path}`), clarifying that path is a relative sub-path and that params are query string. controller resolution precedence is left to the schema description.

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

Purpose5/5

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

States a specific verb (proxy a GET request) and resource (Network Application via Cloud Connector), and names the exact upstream URL template so the agent knows what is being called. The GET qualifier cleanly separates it from the connector_network_post/put/patch/delete siblings.

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

Usage Guidelines3/5

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

Usage is only implied by the HTTP method: an agent can infer this is the read path for arbitrary Network API sub-paths under a console. There is no explicit statement of when to prefer this over typed siblings like get_site_details or connector_protect_get, and no mention that it is an escape hatch for endpoints without a dedicated tool.

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

Deploy Server