← Back to directory
U

UniFi Network MCP

Community
Manage UniFi network infrastructure through MCP.
Category
Other #71 of 230
Stars
★ 921 Very popular
Transport
stdio (local process)
Runtime
Python 3.13+
Credentials
API key / credential required
License
MIT
Last commit
60FMRS · C

The supplied material identifies this as an MIT-licensed UniFi Network MCP server maintained by sirkirby, not by Ubiquiti. Its scope is limited to Network controller management; Protect, Access, relay, and standalone API components must not be attributed to this server.

Strongest · Documentation 14/20 Weakest · Reliability 8/20

Reliability
8/20
Security and permissions
14/20
Maintenance
11/20
Documentation
14/20
Setup experience
13/20
Why each score
Reliability 8/20
The manifest declares a PyPI package using stdio, and the README describes MCP discovery, response modes, and related configuration, making the happy path plausible. However, the supplied material contains no server source, CI workflow, or committed tests for this server. Initialization, tool listing, the claimed 189 tools, dependency behavior, and failure handling therefore cannot be verified, so the static review applies a conservative deduction.
Security and permissions 14/20
The manifest marks credentials as secrets, the README describes default redaction of sensitive fields, and it states that mutations use preview-then-confirm. The server targets a local controller, and the documentation discloses local-account requirements and relevant data flow. Deductions apply because UNIFI_VERIFY_SSL defaults to false, the integration uses an admin or service account, and the materials do not verify per-tool authorization boundaries or confirmation enforcement for each dangerous operation. MFA is also unsupported according to the README. No red-line risk is evidenced.
Maintenance 11/20
The repository is not archived, the version is 0.27.0, the license is MIT, and the supplied material identifies a maintainer, stable status, and a PyPI update path. There is no evidence here of commit cadence, release history, dependency maintenance, issue-response performance, a SECURITY file, or a security-response channel. Stars, open-issue count, and README maintenance claims cannot substitute for that evidence, so the score is limited.
Documentation 14/20
The README covers server scope, installation, authentication requirements, environment variables, client examples, response sizing, redaction, limitations, and several usage scenarios, with a link to Network-specific configuration documentation. The supplied material lacks the actual tool parameters, return schemas, error diagnosis, compatibility matrix, cost guidance, and reviewable Network source evidence. It also contains substantial information about sibling servers and peripheral components, which cannot be credited to this server, so points are deducted.
Setup experience 13/20
The materials provide a uvx command, configuration examples for Claude Code, Codex, OpenClaw, and Claude Desktop, plus runtime, controller, and local-account requirements. The basic connection path is reasonably clear. Setup still requires a local UniFi controller and an account without MFA; SSL verification is disabled by default, and the combination of shared and Network-prefixed environment variables adds complexity. No CI or committed tests demonstrate reproducible installation and handshake success, so the score remains below the top tier.

Static review · not runListed 2026-08-14

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account data

Best for

  • Network administrators who want to manage a UniFi Network controller through an AI assistant.
  • Home-lab or small-organization environments running a local UniFi deployment and seeking network-operations automation.

Not for

  • Accounts configured only with Ubiquiti SSO, SSO MFA, or local 2FA.
  • Users without a UniFi Network controller.
  • Camera or door-access workflows; those belong to separate servers in the same repository.

Required permissions

  • The controller IP address or hostname.
  • A local UniFi administrator or service-account username and password.
  • Sufficient controller permissions for the intended network operations.
  • An optional UniFi API key for selected capabilities.

Risks and side effects

  • The server can manage firewalls, VLANs, VPNs, and network devices; incorrect changes may disrupt connectivity or weaken security boundaries.
  • Administrator credentials are highly sensitive and should be held by a dedicated local service account.
  • UNIFI_VERIFY_SSL defaults to false, which may reduce TLS certificate-validation protection.
  • Disabling sensitive-field redaction can expose Wi-Fi, VPN, or other secrets to agent context and logs.

Setup

Before you start

Runtime:Python 3.13+

UNIFI_HOST required UniFi controller IP or hostname, e.g. 192.168.1.1; required.
UNIFI_USERNAME requiredsecret Local admin/service account username; do not use a Ubiquiti SSO account; required.
UNIFI_PASSWORD requiredsecret Password for the local account; required.
UNIFI_API_KEY optionalsecret Optional UniFi API key for selected capabilities such as firewall policy ordering.
UNIFI_NETWORK_USERNAME optionalsecret Network-server-specific local account username, overrides shared variable.
UNIFI_NETWORK_PASSWORD optionalsecret Network-server-specific local account password, overrides shared variable.
UNIFI_NETWORK_API_KEY optionalsecret Network-server-specific UniFi API key.
Other optional settings (10)
UNIFI_PORT optional Controller HTTPS port, defaults to 443.
UNIFI_VERIFY_SSL optional SSL certificate verification, defaults to false.
UNIFI_SITE optional UniFi site name, defaults to 'default'.
UNIFI_MCP_CONTENT_MODE optional Global response mode: compat, compact, or adaptive (default, chosen by negotiated protocol version).
UNIFI_REDACT_SENSITIVE_FIELDS optional Set to false to disable secret redaction (default on, returns ***REDACTED***); only for trusted local admin workflows.
UNIFI_NETWORK_HOST optional Network-server-specific controller address, overrides shared UNIFI_HOST.
UNIFI_NETWORK_PORT optional Network-server-specific controller port.
UNIFI_NETWORK_VERIFY_SSL optional Network-server-specific SSL verification toggle.
UNIFI_NETWORK_MCP_CONTENT_MODE optional Overrides the global content mode for the Network server only.
UNIFI_NETWORK_REDACT_SENSITIVE_FIELDS optional Overrides redaction for the Network server only.

Run unifi-network-mcp with uvx and configure UNIFI_HOST, UNIFI_USERNAME, and UNIFI_PASSWORD. The server connects to a local UniFi controller and requires a local administrator or service account; do not use a Ubiquiti SSO cloud account. UNIFI_API_KEY, UNIFI_PORT, UNIFI_VERIFY_SSL, and UNIFI_SITE are optional settings.

claude_desktop_config.json
{"mcpServers":{"unifi-network":{"command":"uvx","args":["unifi-network-mcp@latest"],"env":{"UNIFI_HOST":"192.168.1.1","UNIFI_USERNAME":"admin","UNIFI_PASSWORD":"your-password","UNIFI_PORT":"443","UNIFI_VERIFY_SSL":"false","UNIFI_SITE":"default"}}}}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "unifi-network": {
      "command": "uvx",
      "args": [
        "unifi-network-mcp@latest"
      ],
      "env": {
        "UNIFI_HOST": "192.168.1.1",
        "UNIFI_USERNAME": "admin",
        "UNIFI_PASSWORD": "your-password",
        "UNIFI_PORT": "443",
        "UNIFI_VERIFY_SSL": "false",
        "UNIFI_SITE": "default"
      }
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add unifi-network -e UNIFI_HOST=192.168.1.1 -e UNIFI_USERNAME=admin -e UNIFI_PASSWORD=your-password -e UNIFI_PORT=443 -e UNIFI_VERIFY_SSL=false -e UNIFI_SITE=default -- uvx unifi-network-mcp@latest

Run it in a terminal; replace any <…> placeholders with your own values first.

Check that it works

After adding the server, tools from unifi-network-mcp (such as unifi_get_dashboard) should appear in your client's tool list; asking "show me all connected clients" and receiving real controller data confirms the connection.

Troubleshooting

  1. Verify that UNIFI_HOST points to a reachable UniFi controller and that the HTTPS port is correct.
  2. Verify that the credentials belong to a local administrator or service account rather than a Ubiquiti SSO account.
  3. Check the username, password, site name, and optional API key.
  4. If certificate validation prevents connection, inspect the UNIFI_VERIFY_SSL setting.
  5. Confirm that the account has the permissions required for the requested network operation.

Things to try

Once connected, you can ask your AI assistant things like:

  • Show me all clients on the Guest VLAN with their signal strength and data usage
  • Create a firewall rule that blocks IoT devices from reaching the internet between midnight and 6 AM
  • Audit my firewall policies — are there any redundant or conflicting rules?
  • Show me the top traffic flows from the last hour grouped by destination

Use cases

Query UniFi network device and client status.
Manage firewall rules, VLANs, and VPNs.
Inspect guest-VLAN clients, signal strength, and data usage.
Audit firewall policies and analyze network traffic.

Supported clients

Claude Desktop
Codex
OpenClaw

Listed from the project's documentation, not tested by this site.

Overview

UniFi Network MCP is an independent open-source MCP server for managing UniFi Network controllers, including network devices, clients, firewalls, VLANs, VPNs, and related network operations. The repository also contains Protect and Access servers; this profile covers only the Network server defined by apps/network/server.json. The server is version 0.27.0, provides 189 tools, and uses stdio transport.

Similar servers

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 659 · Tools 11 Compare with this →

More servers from this repository

Source revision fbd083c62ec8 Data synced 2026-10-19 Read the FMRS scoring method