py-unifi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNIFI_URL | Yes | The HTTPS origin of the UniFi OS console (e.g. https://controller.example) with no trailing slash, path, query, or credentials. | |
| UNIFI_SITE | No | UniFi site identifier. Defaults to 'default'. | default |
| UNIFI_API_KEY | No | Local API key for authentication. Required if not using UNIFI_USERNAME and UNIFI_PASSWORD. Mixed credentials are rejected. | |
| UNIFI_CA_FILE | No | Path to a PEM CA bundle for a private CA. If not provided, the normal system trust configuration is used. | |
| UNIFI_PASSWORD | No | Password for UniFi OS session authentication. Required together with UNIFI_USERNAME if not using UNIFI_API_KEY. | |
| UNIFI_USERNAME | No | Username for UniFi OS session authentication. Required together with UNIFI_PASSWORD if not using UNIFI_API_KEY. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| unifi_list_sitesA | List accessible sites. Offset/limit bound tool output, not the controller fetch. |
| unifi_list_devicesA | List device inventory and raw state codes; site defaults to UNIFI_SITE. Offset/limit bound tool output, not the controller fetch. |
| unifi_list_clientsA | List currently connected clients; site defaults to UNIFI_SITE. Offset/limit bound tool output, not the controller fetch. |
| unifi_list_networksA | List network summaries without keys or VPN configuration; defaults to UNIFI_SITE. Offset/limit bound tool output, not the controller fetch. |
| unifi_get_healthB | Read subsystem health; missing metrics are unknown, not healthy. |
| unifi_get_deviceA | Get allow-listed telemetry for one exact device ID in the selected site. |
| unifi_rename_deviceA | Preview a rename. Execute only with user intent and dry_run=False; requires API key. |
| unifi_locate_deviceA | Preview LED locate start/stop. Execution requires user intent and API key. Start is not auto-stopped; use enabled=False to stop. LED state is not verified. |
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 8 tools
Each tool targets a distinct resource or action: networks, sites, devices, clients, health, device telemetry, device rename, and device locate. There is no meaningful overlap or confusion between tool purposes.
All tools use the unifi_ prefix followed by a clear verb_noun pattern such as list_networks, get_health, rename_device, and locate_device. The naming is uniform and predictable across the entire set.
Eight tools is well-scoped for a UniFi controller MCP server covering inventory lookup, status checks, and common device actions. Each tool serves a clear purpose without unnecessary bloat.
The tool set covers core UniFi operations well: listing sites, networks, devices, clients, checking health, and retrieving device details. Minor gaps exist, such as no network configuration or additional device management actions, but the main workflows are represented.