Connect AI Agents to UniFi with UniFi MCP
Network infrastructure is a compelling agent use case because investigation often requires gathering evidence from many screens. It is also dangerous because the same interface may be able to change firewall rules, Wi-Fi settings, cameras, doors, or credentials.
UniFi MCP is an independent community project that exposes UniFi Network, Protect, and Access capabilities to AI applications through Model Context Protocol servers and related tools. It is not an official Ubiquiti product.
Start with visibility
Section titled “Start with visibility”The lowest-risk value is read-only investigation:
- inventory devices, clients, networks, cameras, and doors;
- inspect connection quality and traffic patterns;
- review firewall and Wi-Fi policy;
- examine detections, recordings, or access events; and
- correlate evidence across UniFi products during an incident.
An MCP server gives an AI host structured tools with defined inputs and outputs. That is better than asking a model to guess its way through a web interface, but the server is only as trustworthy as its implementation, permissions, and deployed version.
Use a dedicated local identity
Section titled “Use a dedicated local identity”Create a dedicated UniFi account for the integration and grant only the permissions required for its approved workflows. Do not reuse a personal administrator account or place credentials in prompts, notes, or repository files.
Keep the controller and MCP server private when possible. If a remote relay is enabled, evaluate it as a separate trust boundary rather than assuming the local-first properties remain unchanged.
Treat writes as production changes
Section titled “Treat writes as production changes”A confirmation prompt is useful friction, not proof that a change is safe.
Before enabling mutation tools:
- verify current state from the live controller;
- capture the intended change and affected objects;
- preview or plan the operation when supported;
- confirm backups and an out-of-band recovery path;
- require explicit human approval; and
- verify the result after execution.
Begin with create, update, and delete actions disabled. Enable only the categories that have a real, reviewed use case.
Different UniFi products carry different risks
Section titled “Different UniFi products carry different risks”Network data can reveal clients, topology, and security policy. Protect data can include cameras, recordings, detections, and private spaces. Access data can include doors, visitors, credentials, and physical-security events.
Do not treat all three as ordinary infrastructure telemetry. Limit who can query each product and where the returned information may be stored.
Compatibility is a live question
Section titled “Compatibility is a live question”UniFi APIs change across controller and firmware releases. This project is community-maintained, so verify current documentation for the specific product, controller version, authentication method, and agent host before installation.
Use the repository’s current quickstart rather than copying commands from a blog post. Record the installed component and version in the owning operational system.
When I recommend it
Section titled “When I recommend it”UniFi MCP is valuable for operators who already understand their UniFi environment and want faster inventory, investigation, and policy review. It should not be the first place a new administrator learns what a firewall rule does.
The safest progression is read-only visibility, reviewed recommendations, previewed changes, and only then narrowly scoped automation.