Queryable UniFi API docs: endpoint search, schemas, code examples. No controller access.
MCPpedia last refreshed this data
MCP Unifi Applications is an MCP server that queryable UniFi API docs: endpoint search, schemas, code examples. No controller access. Its tool list has not been published yet over stdio and http, requires no API key, and scores 86/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"unifi-docs": {
"args": [
"/path/to/mcp-unifi-applications/mcp_server.py"
],
"type": "stdio",
"command": "/path/to/mcp-unifi-applications/.venv/bin/python"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Queryable UniFi API docs: endpoint search, schemas, code examples. No controller access.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked mcp-unifi-applications against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in devops
MCP server for using the GitLab API
MCP server for discovering, reading, and changing ZenML resources with compact generic tools
MCP server for Dynatrace Managed to access logs, events, and metrics.
An MCP server for Azure DevOps
MCP Security Weekly
Get CVE alerts and security updates for Mcp Unifi Applications and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server that makes the official UniFi API documentation queryable by AI agents: endpoint search, schema drill-down, and code examples in five languages. It 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 and never talks to your controller.
You need uv. The scraped docs ship inside the package, so there is nothing to scrape and no API key to set.
Claude Code
claude mcp add unifi-docs -- uvx mcp-unifi-applications
Add --scope user to make it available in every project.
Claude Desktop and other clients that read an mcpServers block take this entry
(Claude Desktop: claude_desktop_config.json):
{
"mcpServers": {
"unifi-docs": {
"command": "uvx",
"args": ["mcp-unifi-applications"]
}
}
}
If the client reports that it cannot find uvx (GUI apps often start without your
shell's PATH), put the output of which uvx in command instead.
pip install mcp-unifi-applications
Then use "command": "mcp-unifi-applications" with no args, or the absolute path
to that script if your client does not see your virtualenv.
What ships in the current release:
| Application | API version | Scraped | Pages |
|---|---|---|---|
| Network | v11.0.97 | 2026-11-02 | 82 |
| Protect | v7.3.74 | 2026-11-02 | 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 |
A workflow checks developer.ui.com every Monday and releases new API versions on its own.
"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 answers that 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. Instead of the 70 KB endpoint schema, it returns just the subtree that answers the question:
# management[GATEWAY].ipv4Configuration.dhcpConfiguration (in requestBody)
- dhcpConfiguration: object (Gateway Managed IPv4 DHCP Configuration) — IPv4 DHCP …
- mode: string (required)
[RELAY]:
- dhcpServerIpAddresses: Array of string — DHCP Server IP addresses
[SERVER]:
- dnsServerIpAddressesOverride: Array of string — List of DNS servers …
- domainName: string — Domain nam
... [View full README on GitHub](https://github.com/KallistoX/mcp-unifi-applications#readme)