Unifi MCP Server

Unifi is an MCP integration. UniFi semantic-analysis MCP — fleet health, anomaly detection, cross-site analytics.

Packages and local setup

The published npm package is @us-all/unifi-mcp, version 1.13.3. Its declared MCP transport is stdio.

The package declares UNIFI_API_KEY (required): UniFi Site Manager API key (https://unifi.ui.com).; UNIFI_API_URL: UniFi Site Manager API base URL (default: https://api.ui.com).; UNIFI_API_KEY_OWNER: Owner-role API key — enables 33 Cloud Connector tools for per-device/per-client deep data.; UNIFI_TOOLS: Comma-separated category allowlist. Default: all categories enabled.; UNIFI_DISABLE: Comma-separated category disablelist.; UNIFI_LOCAL_URL: Local controller URL (e.g. https://10.10.1.1). Enables 2 local-only tools (get-port-errors, list-port-flap-summary) that surface per-port errors + SFP DDM the Cloud API does not expose. Requires LAN reachability.; UNIFI_LOCAL_USER: Controller local account username (required when UNIFI_LOCAL_URL set). Viewer/Limited-Admin role is sufficient.; UNIFI_LOCAL_PASS: Controller local account password (required when UNIFI_LOCAL_URL set).; UNIFI_LOCAL_SITE: Site slug for legacy /api/s/{site}/ (default: default).; UNIFI_LOCAL_INSECURE: Set to 'true' to accept self-signed cert from the local controller (typical for UDM Pro)..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 1.13.3 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.