UniFi Agent MCP
Integrates with the UniFi Network Integration API to inspect Network sites, active clients, firewall policies, and endpoint traces, and—when approval mode is enabled—submit operator-approved requests to create, edit, and delete user-defined firewall rules within configured zone pairs.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
UniFi Agent MCP
UniFi Agent MCP lets agents inspect UniFi Network sites and firewall policies through the Model Context Protocol.
The service starts in read-only mode. An opt-in approval mode lets authorized callers request creation, editing, and deletion of user-defined firewall rules. An operator approves the exact proposed change before a dedicated executor applies it and reads back the result. Privilege Broker
The integration targets the UniFi Network Integration API. Find the API reference for your installed version under UniFi Network → Integrations. Ubiquiti's API guide
Run from source
Install the project with uv sync --frozen. Configure UNIFI_NETWORK_URL with
the controller's HTTPS Integration API base, such as
https://controller.example.test/proxy/network/integration. Provide the
inspection key through UNIFI_NETWORK_API_KEY in the MCP launch environment.
TLS uses the system trust store by default. Set UNIFI_NETWORK_PINNED_CERT_FILE
to the verified controller leaf certificate for a self-signed deployment.
Set UNIFI_NETWORK_TIMEOUT_SECONDS to a value from 1 to 60 seconds per
controller call. The default is 10 seconds.
Use uv run unifi-agent-mcp as the stdio MCP command. The default mode exposes
configuration, active clients, firewall policy inspection, and endpoint tracing.
Firewall management for the first release
Related MCP server: OPNsense MCP
Enable firewall requests
Set UNIFI_FIREWALL_SCOPE_FILE to a JSON file containing a non-empty
targets array. Each target names site_id, source_zone, and
destination_zone UUIDs. The optional protected_policy_ids array
names rules to protect. Admit only intended data zone pairs. Keep gateway
management pairs outside the configured targets.
Provide distinct, high-entropy UNIFI_MCP_READ_TOKEN and
UNIFI_MCP_REQUEST_TOKEN values. The enabled MCP binds loopback on
UNIFI_MCP_PORT (default 8080) and requires a TLS frontend for remote
clients. The request token can submit and inspect operator-approved
create, edit, and delete requests on the shared MCP. The read token
grants inspection.
Configure UNIFI_BROKER_URL, UNIFI_BROKER_CLIENT_CERT_FILE,
UNIFI_BROKER_CLIENT_KEY_FILE, and the optional UNIFI_BROKER_CA_FILE
for the caller's broker mTLS identity. Requests return a broker approval
link and request ID. The status tool reports approval and verified
execution separately. Use a broker that implements the UniFi approval
family.
The first rule profile creates disabled IPv4 allow or block rules in the requested zone pair. Edits support the name, description, logging, and enabled state while preserving existing match criteria. Updates and deletes require an admitted user-defined policy.
Run the trusted executor
Run unifi-firewall-executor with its own broker mTLS identity and
controller credentials. Set UNIFI_BROKER_EXECUTOR_IDENTITY to the
registered broker identity and UNIFI_BROKER_SIGNING_PUBLIC_KEY_FILE
to the pinned OpenSSH Ed25519 public key. Give only this process
UNIFI_NETWORK_WRITE_KEY. Supply the same controller URL, trust
configuration, and firewall scope. Each invocation drains a bounded
approved queue and records read-back or uncertainty for each claim.
Use GitHub Issues for defects and feature requests. See SECURITY.md for private vulnerability reporting.
Licensed under Apache-2.0.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP gateway with runtime security policy, tool-call-level control, and audit of agent actions.
Human-in-the-loop review and approval for AI agents. Audit trail, approval policies, native MCP.
Crypto transaction firewall and risk tools for MCP agents.
Unified MCP Server is a remote MCP connector for AI agents and vertical AI products that provides access to 22,000+ authorized SaaS tools across 400+ integrations and 24 categories directly inside LLMs (Claude, GPT, Gemini, Cohere). Tools operate only on explicitly authorized customer connections, enabling agents to safely read and write against live third-party systems.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage UniFi Network, Protect, and Access infrastructure through MCP tools, with support for local controllers and cloud relay.MIT
- AlicenseNot gradedqualityCmaintenanceEnables remote agents to securely read firewall and NAT rules, inspect routing tables and logs, and execute safety-gated mutation plans through a bearer-authenticated MCP endpoint.49 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and applications to interact with UniFi network infrastructure through the UniFi Network Controller API, supporting device, client, network, firewall, QoS, backup, multi-site, and topology management.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read and change UniFi Network, UniFi Protect, and UniFi cloud infrastructure through a standard MCP interface, including single-controller and multi-controller fleet operations.50 npmApache 2.0