UniFi Fabric MCP Server

UniFi Fabric MCP Server

Ask your AI assistant to check and manage your UniFi network.

📦 Installation · ▶️ Watch demo · ⚙️ How it works · 🛡️ Security · 📚 More info

UniFi Fabric MCP Server connects your AI assistant to your UniFi network. Find offline devices, dig into Wi-Fi problems, review cameras, or change settings just by asking.

It works through UniFi Fabrics, which put your sites and companies under one organization in UniFi Site Manager. Join your consoles to a fabric, create a fabric API key, and you're set. One key covers the whole organization, and the server runs on your own computer or server. Everything goes through Ubiquiti's cloud, so it never needs to reach a controller on your local network.

What you can do

Ask your assistant to help with tasks such as:

• “List my UniFi sites and the devices in each one.”
• “Which devices are offline, and what should I investigate?”
• “Show me the recent events from my Protect cameras.”
• “Show me the floor plans in my InnerSpace project.”

You can also manage networks, Wi-Fi and firewall policies. See tool usage and the tools reference for details.

Features

• 792 tools, loaded on demand. Discovery mode gives your assistant a small search-and-call toolset instead of flooding its context with the whole catalog; the full catalog is one setting away.
• Deep Network and Protect coverage, plus InnerSpace. Networks, Wi-Fi, VPN, firewall, clients, devices, cameras and floor plans; see tool families for what is and is not covered.
• Multi-site and multi-organization. One fabric key covers every site in the organization, and you can configure several keys to manage many organizations from one server. See the MSP guide.
• Ready for shared deployments. Run it over HTTPS behind a gateway: request headers can carry each caller's own API keys (the server stores none) and tighten write policy or tool families per request, so one server can safely serve many users. See header key mode.
• Write controls. allow, dry-run or deny globally, with per-family and per-tool exceptions.
• Everything is a switch. Expose only the tool families you want, hide individual tools, run discovery mode or advertise the full catalog, and opt into redaction and audit logging; all of it is environment settings, no code changes. See the configuration guide.
• Secret redaction and audit logging. Mask credential fields in responses and log every write attempt. See the configuration guide.
• Any MCP client, any transport. stdio locally; HTTPS and SSE for servers, with bearer-token or OAuth authentication and TLS served by the server itself (bring your own certificate), up to mutual TLS. See authentication and TLS.

Installation

1. Join your fabric and create an API key

1. Sign in to UniFi Site Manager. In the Sites sidebar under Fabrics, create a fabric (Create New) if you don't have one, and make sure the sites with your consoles are in it. New to fabrics? See Ubiquiti's video and announcement.
2. Select your fabric, then open API Keys and select Create New API Key.
3. Enable at least Site Manager and Network scopes; add Protect for cameras. Choose the sites the key can access.
4. Copy the key and store it securely. It is shown only once.

Treat the key like a password: each client stores it in plain text in its own configuration file, so keep those files private.

2. Connect your assistant

[!NOTE]

The package commands below use the currently published 0.7.1 release. This README

describes 0.7.1 source. Upgrading from 0.7.0? See the migration guide

before changing settings.

The setups below run the server with uvx (from uv), which fetches everything it needs — no Python setup required. Prefer pip? See the client setup guide.

Claude Code

With Claude Code 2.1.275 or later, run:

/plugin marketplace add swkstudios/unifi-fabric-mcp-server

/plugin install unifi-fabric@unifi-fabric

Enter your API key when prompted. Or skip the plugin and add the server directly from a terminal (the first line prompts for your key):

printf 'UniFi API key: '; read -rs UNIFI_API_KEY; echo; export UNIFI_API_KEY

claude mcp add unifi-fabric -e UNIFI_API_KEY="$UNIFI_API_KEY" -- uvx --from unifi-fabric-mcp-server==0.7.1 unifi-fabric-mcp

Claude Desktop

Open Settings > Developer > Edit Config and merge the following into the configuration:

{

"mcpServers": { "unifi-fabric": { "command": "/absolute/path/to/uvx", "args": ["--from", "unifi-fabric-mcp-server==0.7.1", "unifi-fabric-mcp"], "env": { "UNIFI_API_KEY": "your-api-key-here" } } } }

Replace the command path with the output of which uvx on macOS or where uvx on Windows, and replace the key placeholder. Quit Claude Desktop completely and reopen it.

Alternatively, download the Claude Desktop extension (.mcpb) and open it; Claude Desktop prompts for your API key during installation.

Codex

From a terminal (the first line prompts for your key):

printf 'UniFi API key: '; read -rs UNIFI_API_KEY; echo

codex mcp add unifi-fabric --env UNIFI_API_KEY="$UNIFI_API_KEY" -- uvx --from unifi-fabric-mcp-server==0.7.1 unifi-fabric-mcp

This stores the key in ~/.codex/config.toml. Run codex mcp list to check the registration.

Google Antigravity

Export the key before starting agy — that keeps it out of config files (Antigravity does not expand ${VAR} in env values):

printf 'UniFi API key: '; read -rs UNIFI_API_KEY; echo; export UNIFI_API_KEY

agy mcp add unifi-fabric -- uvx --from unifi-fabric-mcp-server==0.7.1 unifi-fabric-mcp agy

When Antigravity is started from the Dock (Antigravity 2.0 and the IDE), it cannot see exported variables; store the key in the c