From unifi-network
Manages UniFi network infrastructure: devices, clients, firewall, VPN, routing, WLANs, and traffic flows via 177 MCP tools. Lazy-loaded tool discovery with permission-gated mutations and preview-then-confirm safety model.
How this skill is triggered — by the user, by Claude, or both
Slash command
/unifi-network:unifi-networkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You have access to a UniFi Network MCP server that lets you query and manage a UniFi Network Controller. It provides 177 tools covering devices, clients, firewall, VPN, routing, WLANs, Traffic Flows, statistics, and more.
You have access to a UniFi Network MCP server that lets you query and manage a UniFi Network Controller. It provides 177 tools covering devices, clients, firewall, VPN, routing, WLANs, Traffic Flows, statistics, and more.
The server uses lazy loading by default — only meta-tools are registered initially. Use them to find and call any tool:
| Meta-Tool | Purpose |
|---|---|
unifi_tool_index | Discover tools by name/description; use category, search, or include_schemas to filter |
unifi_execute | Call any tool by name (essential in lazy mode) |
unifi_batch | Run multiple tools in parallel |
unifi_batch_status | Check async batch job status |
Workflow: Call unifi_tool_index to find the right tool, then unifi_execute to call it. For multiple independent queries, use unifi_batch — it's significantly faster than sequential calls.
The server is "secure by default" because it controls real network infrastructure.
Read operations — always available. All list_*, get_*, and query tools work without special permissions.
Mutations — permission-gated with mixed defaults:
If a mutation fails with a permission error, tell the user the env var to set: UNIFI_POLICY_NETWORK_<CATEGORY>_<ACTION>=true
Confirmation flow — every mutation uses preview-then-confirm:
confirm=true → executes the mutationAlways preview first and show the user before confirming.
All tools return: {"success": true, "data": ...}, {"success": false, "error": "..."}, or {"success": true, "requires_confirmation": true, "preview": ...}. Always check success first.
Redacted secrets: Secret fields — WLAN passphrases (x_passphrase), VPN private/preshared keys, whole VPN config blobs (imported WireGuard/OpenVPN config files), and SNMP community strings — come back as ***REDACTED*** by default. When the user genuinely needs the value (e.g. "what's the guest WiFi password?"), pass include_sensitive=true to the read tool. On an update, send only the fields you are changing — to keep a secret unchanged, omit it; never echo ***REDACTED*** back, which is rejected so the placeholder can't overwrite the real secret.
unifi_list_devices returns a device_category field that accurately classifies devices:
ap — real access points (excludes USP Smart Power strips that report as uap type)switch — switchesgateway — UDM/USG gatewayspdu — smart power strips, UPS deviceswan — cable internet (UCI) devicesUse device_category (not type) when counting or filtering devices. The device_type filter parameter uses this classification.
Additional enriched fields: upgradable (bool), connection_network (VLAN name), uplink (topology), load_avg_1, mem_pct, model_eol.
unifi_batch for parallel queries (biggest efficiency win)unifi_lookup_by_ip — faster than listing all clients when you know the IPunifi_get_top_clients — fastest way to find bandwidth hogsunifi_get_traffic_flows — query historical Insights > Flows records when the user asks who talked to what, which ports/protocols were used, or where traffic wentunifi_get_network_health for quick "is everything OK?"device_category field, not type, for accurate AP/switch/PDU countsUsername and password are required (local admin credentials, not Ubiquiti SSO). API key support exists but is experimental — limited to read-only operations and a subset of tools.
To configure, run /unifi-network:unifi-network-setup or set env vars manually:
UNIFI_NETWORK_HOST=192.168.1.1
UNIFI_NETWORK_USERNAME=admin
UNIFI_NETWORK_PASSWORD=your-password
If the user also has cameras or door access control, other UniFi MCP plugins are available:
unifi-protect — security cameras, NVR, recordings, smart detectionsunifi-access — door locks, credentials, visitors, access policiesCameras and access readers appear as network clients — use unifi_lookup_by_ip to cross-reference if troubleshooting connectivity for those devices.
For the complete list of all 177 tools organized by category with descriptions, tips, and common scenarios, read references/network-tools.md.
npx claudepluginhub sirkirby/unifi-mcp --plugin unifi-networkManages Ubiquiti UniFi networks via unifly Rust CLI: VLANs, SSIDs, firewalls, NAT, DHCP reservations, clients, devices, events, stats, DPI, backups, raw API.
Manages UniFi network infrastructure: inspect clients/devices/sites/WiFi configs/firewall rules/DPI stats/events; actions like block/reconnect/forget clients, restart/locate devices.
Manage UniFi firewall policies via natural language — create, modify, review rules, content filters, and traffic policies. Automatically snapshots state before mutations for rollback.