Integration

UniFi Site Manager integration

UniFi Site Manager is Ubiquiti's cloud API for every UniFi deployment linked to one UI account. An agent can list the account's hosts (UniFi OS consoles and self-hosted Network Servers) and read one host, list the sites running the UniFi Network application with their device and client counts, list the devices each host manages with their status and firmware, read ISP performance metrics (latency, packet loss, throughput, uptime) at 5-minute or 1-hour intervals, and read SD-WAN configurations with their deployment status. Every tool only reads: Ubiquiti's API keys are read-only today, and the Cloud Connector routes (a pass-through to each console's local Network and Protect APIs, which can change or restart devices) are not exposed. Authentication is an API key created at unifi.ui.com under Settings, API Keys, sent in the X-API-Key header.

Connect UniFi Site Manager How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in UniFi Site Manager.Built from the 9 UniFi Site Manager tools below, on the connection you add once.

What you can do with UniFi Site Manager

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Host, 2 operations

get_hostGet hostGETAgents: ask firstReads one host (a UniFi OS console or a self-hosted Network Server) by its id from list_hosts: IP address, ownership, cloud-access block flag, backup time, plus its userData and reportedState as the host reports them.
list_hostsList hostsGETAgents: ask firstLists the hosts (UniFi OS consoles and self-hosted Network Servers) linked to the UI account, with IP address, ownership, cloud-access block flag and last connection change. Paged: pass nextToken back to read on.

Isp metric, 2 operations

get_isp_metricsGet isp metricsGETAgents: ask firstReads ISP metrics (latency, packet loss, download and upload kbps, uptime, downtime, ISP name and ASN) for every site of the UI account, per 5-minute (type 5m) or 1-hour (type 1h) period. Bound it with duration, or begin and end timestamps.
query_isp_metricsQuery isp metricsPOSTAgents: ask firstReads ISP metrics for chosen sites only (each by hostId and siteId from list_sites, with an optional time range), at 5-minute (type 5m) or 1-hour (type 1h) periods. Read-only despite the POST.

Sd wan config, 2 operations

get_sd_wan_configGet sd wan configGETAgents: ask firstReads one SD-WAN configuration by id from list_sd_wan_configs: variant (single, failover or distributed), tunnel and routing settings, and its hubs and spokes (host, site, networks, routes, primary WAN, WAN failover).
list_sd_wan_configsList sd wan configsGETAgents: ask firstLists the SD-WAN configurations of the UI account: id, name and type. Pass an id to get_sd_wan_config or get_sd_wan_config_status.

Device, 1 operation

list_devicesList devicesGETAgents: ask firstLists the UniFi devices of the hosts the UI account owns or super-administers, grouped by host: model, IP, MAC, status (online or offline), firmware version and update status. Filter with hostIds[] from list_hosts. Paged with nextToken.

Sd wan config status, 1 operation

get_sd_wan_config_statusGet sd wan config statusGETAgents: ask firstReads the deployment status of one SD-WAN configuration: generation and apply status, errors and warnings, and per hub and spoke the WAN IP and latency, networks, routes and tunnel states.

Site, 1 operation

list_sitesList sitesGETAgents: ask firstLists the sites (from hosts running the UniFi Network application) linked to the UI account, with name, timezone, gateway, device and client counts, ISP, WAN uptime and the caller's permission. Paged: pass nextToken back to read on.

Use UniFi Site Manager from Claude Code, Cursor or Codex

Connect UniFi Site Manager in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its UniFi Site Manager operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect UniFi Site Manager

Create your workspace
Sign up free. Nothing to install.
Connect UniFi Site Manager once
Add your UniFi Site Manager connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.