mcp-unifi-network
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNIFI_HOST | Yes | The console. A pasted browser URL is accepted and split. | |
| UNIFI_MODE | No | `unifios` · `cloud` · `classic`. | inferred |
| UNIFI_SITE | No | Default site. UUID, legacy name or display name. | |
| UNIFI_API_KEY | Yes | Settings → Control Plane → Integrations → Create API Key. | |
| UNIFI_CONF IG | No | JSON alternative to all of the above. | ~/.config/unifi/config.json |
| UNIFI_PASSWORD | No | Legacy tier only. A **local** admin, not SSO. | |
| UNIFI_USERNAME | No | Legacy tier only. A **local** admin, not SSO. | |
| UNIFI_MAX_PAGES | No | Tuning parameter. | 20 |
| UNIFI_CONSOLE_ID | No | Cloud mode: the console id from unifi.ui.com. | |
| UNIFI_PAGE_LIMIT | No | Tuning parameter. | 50 |
| UNIFI_APP_VERSION | No | Pin the version instead of probing at startup. | probed |
| UNIFI_MAX_RETRIES | No | Tuning parameter. | 3 |
| UNIFI_ALLOW_WRITES | No | Register the mutating tools. | false |
| UNIFI_INSECURE_TLS | No | Disable certificate verification, this server only. | false |
| UNIFI_ENABLE_LEGACY | No | Register the `unifi_legacy_*` tools. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| unifi_auth_statusA | Report whether this server can reach a UniFi console, which transport and site it uses, what Network version the console runs, and — when something is missing — exactly what to set. Call this FIRST whenever a tool you expected is not in the list: on this API the available endpoints depend on the console's version, so an absent tool usually means an older console or missing configuration rather than a bug. |
| unifi_list_sitesA | List the sites on this console with ALL THREE of their identifiers: the |
| unifi_get_console_infoA | Report the console's UniFi Network version and which tools it supports. This API gained most of its endpoints in Network 10.0, so on an older console a large part of the tool set simply does not exist. Call this when a tool is missing or returns a 404 — it names the version each capability needs and lists what is gated off here. |
| unifi_list_clientsA | List the clients currently connected to a site — the devices on your network right now, not the historical list. Each entry carries the client |
| unifi_get_clientA | Get the full detail of one connected client by its |
| unifi_list_devicesA | List the UniFi devices adopted by a site — access points, switches, gateways — with their state, model, IP, MAC and firmware. Use |
| unifi_get_deviceA | Get one adopted device in full, including its |
| unifi_get_device_statsA | Get a device's latest telemetry: uptime, CPU and memory utilization, load averages, uplink throughput and per-radio transmit retry rates. This is the current snapshot the console holds, not a time series — there is no history endpoint in this API. |
| unifi_list_vouchersA | List the hotspot guest vouchers on a site, with their code, name, time and data limits, how many guests have used each, and when it activates and expires. An expired voucher is not deleted automatically — filter with |
| unifi_list_networksA | List the networks (VLANs) configured on a site — their name, VLAN id, subnet, DHCP settings and purpose. Read-only: this server does not create or modify networks, because a wrong subnet or VLAN id disconnects every client on it with no undo. Make those changes in the UniFi UI. |
| unifi_list_wlansA | List the WiFi broadcasts (SSIDs) on a site, with the network each is bridged to, its security mode, band and whether it is enabled. Read-only for the same reason as networks: a bad SSID change takes every wireless client offline at once. |
| unifi_list_firewall_zonesA | List the firewall zones on a site — the named groups of networks that zone-based policies are written between. Read these first: a policy references zones by id, so the ids here are what make |
| unifi_list_firewall_policiesA | List the zone-based firewall policies on a site, with their action, source and destination zones, matching criteria and whether each is enabled. Policies are evaluated in order, so pass |
| unifi_requestA | Escape hatch: call any Integration API endpoint directly, for the parts of the API this server does not wrap — switch stacks, LAG, VPN servers, RADIUS profiles, WAN interfaces, device tags, ACL rules, DNS policies and the DPI reference tables. Paths are relative to the API root, so |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| diagnose-client | Work out why one device cannot get on the WiFi — blocked, absent, out of range, or connected and failing higher up. |
| new-devices | List devices seen on the network for the first time recently, with enough identity to judge whether each is expected. |
| network-health | Review subsystem health, device state, firmware, WiFi security posture and blocked clients, and report what actually needs attention. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| unifi-troubleshooting | Read this BEFORE concluding that a device is absent, that nothing is blocked, or that a client has been offline for months. Documents the API behaviours that return a successful, plausible, wrong answer — including why a device refused at the authentication frame appears nowhere in the API, and how to read the access-point logs that do record it. |
TDQS
Scored across 14 tools
Each list_* tool targets a clearly distinct resource (sites, devices, clients, vouchers, networks, WLANS, firewall zones, firewall policies), and get_device vs get_device_stats vs get_client are well separated by their descriptions. The main friction is unifi_auth_status vs unifi_get_console_info, which both diagnose 'why is a tool missing / version mismatch', and the generic unifi_request slightly overlaps every read tool as a fallback.
All tools use a consistent unifi_ prefix with snake_case verb_noun (list_*, get_*, list_firewall_zones), which is easy to scan. Minor deviations are unifi_auth_status (noun phrase) and the bare-verb unifi_request, but neither breaks the pattern.
14 tools is well within the ideal band and each one maps to a distinct resource or diagnostic need; nothing looks redundant or padded. The read-only scope keeps the set tight and every tool earns its place.
The read surface covers the core inventory: sites, devices, device stats, clients, networks, WLANS, vouchers, firewall zones and policies. Gaps exist (no single-site detail, no events/alarms or DPI views, and all mutations are gated behind UNIFI_ALLOW_WRITES), but unifi_request provides a documented GET escape hatch for anything unwrapped.