UniFi MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNIFI_URL | Yes | Your UniFi controller URL (e.g., https://192.168.1.1 or https://api.ui.com for cloud) | |
| UNIFI_API_KEY | No | Your API key (required if not using username/password) | |
| UNIFI_SITE_ID | No | Your UniFi site identifier | default |
| UNIFI_TIMEOUT | No | Request timeout in milliseconds | 30000 |
| UNIFI_API_TYPE | No | API mode: local, cloud-v1, or cloud-ea | cloud-ea |
| UNIFI_PASSWORD | No | UniFi password (required if not using API key) | |
| UNIFI_USERNAME | No | UniFi username (required if not using API key) | |
| UNIFI_LOCAL_HOST | No | Local host for local mode (e.g., 192.168.1.1) | |
| UNIFI_LOCAL_VERIFY_SSL | No | Whether to verify SSL for local mode | true |
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-apiA | Execute any UniFi Network API operation. Specify the spec path (e.g. /v1/sites/{siteId}/devices) and optional path params, query params, or body. HTTP method is auto-detected. Use unifi-api-schema to discover available paths. |
| unifi-api-schemaA | Discover available UniFi Network API operations from the OpenAPI spec. Call with no args for a tag overview, with tag to list operations in that tag, or with path for full parameter and request body details. |
| unifi-legacy-client-statsA | Get client bandwidth statistics from the legacy UniFi controller API. Returns per-client tx_bytes, rx_bytes, tx_rate, rx_rate for all active clients. Uses the old controller API endpoint (/proxy/network/api/s/{site}/stat/sta) which is not in the Integration API OpenAPI spec. This is the only way to get per-client bandwidth data on UniFi OS devices. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/bakhshb/unifi-mcp-openapi'
If you have feedback or need assistance with the MCP directory API, please join our Discord server