unifi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNIFI_API_KEY | Yes | Integration API key | |
| UNIFI_CA_CERT | No | Path to the controller's CA certificate (PEM) | |
| UNIFI_BASE_URL | Yes | Gateway address, e.g. https://192.168.1.1 | |
| UNIFI_SPEC_URL | No | Override the OpenAPI spec URL fetched from the gateway | |
| UNIFI_CACHE_DIR | No | Where the cached spec is written | ~/.cache/unifi-mcp |
| UNIFI_LOG_LEVEL | No | Pino log level (error, warn, info, debug) | error |
| UNIFI_SPEC_FILE | No | Use a local spec file as the bundled fallback | |
| UNIFI_TIMEOUT_MS | No | Per-request timeout in milliseconds | 30000 |
| UNIFI_ALLOW_WRITES | No | Enable write operations via unifi_invoke | false |
| UNIFI_INSECURE_TLS | No | Disable TLS verification — last resort only | false |
| UNIFI_SPEC_FRESHNESS_MS | No | Max age of the cached spec in milliseconds | 86400000 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| unifi_list_entitiesA | List UniFi entities (OpenAPI tags) exposed by this controller, with read/write op counts. Call first. |
| unifi_describe_entityB | Describe one entity: its operations, path/query parameters, and whether each is read (GET) or write. |
| unifi_getC | Invoke a read (GET) operation for an entity. Provide pathParams/query as needed. |
| unifi_invokeA | Invoke any operation by id (including writes). Gated off unless UNIFI_ALLOW_WRITES=true. Post-v1 write path. |
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 4 tools
Each tool has a distinct purpose: list entities, describe one entity, perform read-only GET, and invoke any operation (including writes). There is slight overlap between unifi_get and unifi_invoke for reads, but descriptions clarify safety, making ambiguity low.
All tools follow the pattern unifi_<verb>, with verbs list, describe, get, invoke. The naming is predictable and consistent, with no mixing of styles.
Four tools is appropriate for a dynamic API wrapper: discovery (list, describe) and execution (get, invoke). The number is well-scoped and each tool earns its place.
The tool set covers full lifecycle of API interaction: list available endpoints, describe details, perform safe reads, and invoke any operation (including writes if enabled). No obvious gaps for its purpose.