UniFi MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 17 Sep 2026.
Every UniFi Network API operation, plus drift detection, topology, and rule prediction no other
What the code does
We read the source, 20 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
cacheFile := filepath.Join(c.cacheDir, c.cacheKey(path, params)+".json")
select {
case <-time.After(interval + jitter):
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to UniFi MCP
same job, measured the same wayEvery Datto RMM API operation, plus a local SQLite fleet store and fleet-wide analytics no other
Rust MCP server and CLI for UniFi Network controller operations.
Rust MCP server and CLI for UniFi Network controller operations.
Every ThreatLocker Portal API feature, plus the write operations the read-only tools lack and a
IP geolocation, ASN and network data, plus VPN, proxy and Tor detection. ASN tools need no key.
Every Cork API operation, plus cross-client risk attribution and exploitability-first vuln triage.
Every Avanan API operation, plus shift-start triage, campaign grouping, and quarantine evidence.
Every Zammad ticket, article, and Knowledge Base operation as one CLI and MCP server - plus a
UniFi MCP — questions
Answers built from our own checks of this server.