KallistoX/mcp-unifi-applications

A Model Context Protocol (MCP) server that makes the official UniFi API documentation queryable by AI agents — endpoint search, schema drill-down, and code examples in five languages, for Claude Desktop, Claude Code (VS Code / JetBrains), or any MCP-compatible client.
Covers every application Ubiquiti publishes API docs for: **Network, Protect, Site Manager, InnerSpace, Mobility and Carrier Fabric**.
It is **read-only and credential-free**: it serves documentation, it does not talk to your controller. Includes a Playwright-based scraper that turns the JS-rendered docs SPA into structured JSON, and a Python MCP server that serves it.
Example
> *"Without any context, just by using the unifi-applications MCP Server: can you
> tell me how to create a network with Go with the network API from UniFi, and
> what options do I have regarding the managed IPv4 DHCP gateway configuration?"*
Claude works that out through the server, with none of the documentation in its
context to begin with:
| Call | What comes back |
|---|---|
| search_endpoints("create network") | POST /v1/sites/{siteId}/networks |
| get_endpoint("network/createnetwork") | the request body — management is a discriminated union |
| get_field_schema(…, "management[GATEWAY].ipv4Configuration.dhcpConfiguration") | **only** the DHCP subtree |
| get_example("network/createnetwork", "go") | a working request in Go |
The third call is the one that earns the server its place. It returns this, and
nothing else — not the 70 KB endpoint schema it is buried in:
Both discriminator variants, every field typed and described. That is the answer
to *"what are my options"* — and the model writes the Go from it without ever
having seen the UniFi docs.
Quick Start
1. Install
The scraped docs ship inside the package — there is nothing to scrape and no
API key to configure. What you get:
| Application | API version | Scraped | Pages |
|---|---|---|---|
| Network | v10.6.106 | 2026-10-12 | 82 |
| Protect | v7.3.70 | 2026-10-12 | 81 |
| Site Manager | v1.0.0 | 2026-09-10 | 12 |
| InnerSpace | v1.3.23 | 2026-09-10 | 12 |
| Mobility | v1.0.0 | 2026-09-10 | 9 |
| Carrier Fabric | v1.0.0 | 2026-09-10 | 14 |
From source instead
2. Register with your client
**Claude Code (VS Code / JetBrains)** — add .mcp.json to your project root (Reload Window after):
**Claude Desktop** — add to ~/.config/Claude/claude_desktop_config.json (Linux) or
~/Library/Application Support/Claude/claude_desktop_config.json (macOS):
If the command is not on your client's PATH — Claude Desktop often does not
inherit a shell PATH — give the absolute path instead, e.g.
/path/to/.venv/bin/mcp-unifi-applications.
How this differs from other UniFi MCP servers
Most UniFi MCP servers are **control planes**: they authenticate against your controller and expose tools that read and change live state — devices, clients, firewall rules. This one is a **knowledge plane**. It never sees your network.
| | Control-plane servers | This server |
|---|---|---|
| Needs controller credentials | Yes | No |
| Touches live network state | Yes | No |
| Answers "what does this endpoint accept?" | Rarely | That is the whole job |
| Useful before you have hardware | No | Yes |
They are complements, not competitors. Pair this one with a control-plane server when you are *building* against the UniFi API: this one tells the model what the API looks like, the other one calls it.
Why not just feed the model the OpenAPI spec?
Ubiquiti does publish one — developer.ui.com/ /v /openapi.json. It is a good spec, and it is missing exactly the parts an agent needs most. For Network v10.4.57 (44 paths, 73 operations, 379 schemas):