UniFi MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTH_MODE | No | env (default, reads the var above) or gateway (credential arrives per-request via the X-UniFi-Api-Key header, injected by the Conduit gateway). | env |
| LOG_LEVEL | No | debug | info (default) | warn | error. | info |
| MCP_TRANSPORT | No | stdio (default) or http. | stdio |
| UNIFI_API_KEY | No | UniFi Cloud Site Manager API key. | |
| CONDUIT_S2S_SECRET | No | When set, the HTTP transport requires a valid X-Gateway-S2S header (Conduit sidecar auth) on every /mcp request. |
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 | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| unifi_list_sitesA | List every UniFi site (from hosts running the UniFi Network application) visible to this API key's UI.com account. Each entry includes the site and host IDs, site metadata (name, timezone, gateway MAC), aggregate statistics (device/client counts, network performance), and the caller's permission level on that site. |
| unifi_list_hostsA | List every host (UniFi console or network-server application) associated with this API key's UI.com account. Includes hardware ID, current IP address, ownership/block status, and registration/backup timestamps. |
| unifi_get_hostA | Get detailed information about a single host by ID (as returned by unifi_list_hosts). |
| unifi_list_devicesA | List UniFi devices managed by hosts this API key's account owns or super-admins, grouped by host. Each device includes its MAC address, IP address, model, firmware status, and adoption/uptime info. PII-bearing (device MAC/hostname/IP) - admin-gated. |
| unifi_get_isp_metricsA | Get WAN/ISP health and traffic metrics for every site linked to this API key's account, at 5-minute or 1-hour granularity. 5-minute data is retained at least 24h; 1-hour data at least 30 days. Provide either |
| unifi_query_isp_metricsA | Get WAN/ISP health and traffic metrics for specific host/site pairs and time ranges. A filtered read, not a mutation, despite being a POST on UniFi's API. If the API key lacks access to a requested site, the response reports status:partialSuccess for a mixed result or fails outright if none are accessible. |
| unifi_list_sdwan_configsA | List every SD-WAN configuration associated with this API key's account (id, name, type only). |
| unifi_get_sdwan_configA | Get the full topology for one SD-WAN configuration: variant, advanced settings, and every hub/spoke including their site/host IDs, attached network IDs, and routed subnets (CIDR). Network-topology data - admin-gated. |
| unifi_get_sdwan_config_statusA | Get deployment status for one SD-WAN configuration: generation/apply status, and per-hub/spoke details including WAN IPs, latency, routes, and any errors or warnings. Network-topology data - admin-gated. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools are clearly distinct by resource type (sites, hosts, devices, SD-WAN configs, ISP metrics). The only potential confusion is between unifi_get_isp_metrics and unifi_query_isp_metrics, which both fetch WAN/ISP metrics—though one is account-wide and the other is a filtered query, the overlap could cause misselection.
All tools follow a consistent unifi_<verb>_<noun> snake_case pattern, with list for plural collections and get for singular resources. The minor deviation is query_isp_metrics using 'query' instead of 'get' for a similar read operation, slightly breaking the otherwise predictable pattern.
Nine tools is a well-scoped count for a UniFi network-management server. Each tool covers a distinct resource area (sites, hosts, devices, SD-WAN, ISP metrics) without unnecessary bloat or overlap.
The tool surface provides solid read-only coverage for the core UniFi resources, including listing and detail retrieval for hosts and SD-WAN configs, plus metrics for ISP health. Minor gaps exist—no singular site or device detail endpoints and no client-level information—but agents can work around these using the existing list operations.