UniFi MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNIFI_HOST | Yes | UniFi Controller URL (e.g., https://192.168.1.1) | |
| UNIFI_SITE | No | UniFi site name | default |
| UNIFI_PASSWORD | Yes | UniFi Controller password | |
| UNIFI_USERNAME | Yes | UniFi Controller username | |
| UNIFI_VERIFY_SSL | No | Verify SSL certificates (true/false) | true |
| UNIFI_IS_UNIFI_OS | No | Using UniFi OS device like UDM/UDM Pro (true/false) | 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_devicesB | Get all UniFi network devices (access points, switches, gateways) |
| restart_deviceB | Restart a UniFi network device by its MAC address |
| get_clientsC | Get all currently connected clients on the UniFi network |
| block_clientC | Block a client from accessing the network |
| unblock_clientB | Unblock a previously blocked client |
| disconnect_clientC | Force disconnect a client from the network |
| get_sitesB | Get all UniFi sites configured on the controller |
| get_site_healthB | Get health status for the current site |
| get_networksB | Get all network configurations for the current site |
| get_device_activityC | Get activity for a specific device including connected clients and their traffic |
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 10 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, block_client and disconnect_client serve different functions (blocking vs. disconnecting), while get_clients, get_devices, get_networks, and get_sites each target specific resource types. The actions and resources are well-defined and non-overlapping.
All tool names follow a consistent verb_noun pattern using snake_case, such as block_client, get_clients, and restart_device. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.
With 10 tools, the server is well-scoped for managing a UniFi network. Each tool serves a clear purpose in client, device, network, and site management, with no redundant or trivial tools. The count aligns well with the domain's typical operations.
The tool set covers core CRUD and lifecycle operations for UniFi management, including monitoring (get_*), control (block/disconnect/restart), and site handling. A minor gap exists in update operations for configurations (e.g., updating network settings), but agents can work around this with the provided tools for most workflows.