An MCP server that leverages official UniFi API
Unifi MCP server exists for a simple reason — assistants are far more useful when they can act on Unifi directly instead of describing what you should do. An MCP server that leverages official UniFi API.
A Model Context Protocol (MCP) server that exposes the UniFi Network Controller API today and is evolving into a production-grade multi-domain platform for Protect, Access, and enterprise-scale orchestration.
Once Unifi is connected, these are the calls the assistant has available:
Objective — Give operators a fast, safe reading order for understanding what the server does today, what it is becoming, and which docs govern rollout decisionsPrerequisites — The Prerequisites tool exposed by this serverProcedure — 1. Confirm the current stable release and current phase focus. 2. Read SPEC.md for architecture intent and DEVELOPMENT_PLAN.md for sequencing. 3. UseVerification — The Verification tool exposed by this serverRollback — The Rollback tool exposed by this serverInstallation — The Installation tool exposed by this serverPublishing — The Publishing tool exposed by this serverConfiguration — The Configuration tool exposed by this serverYou will need 6 environment variables: MCP_SERVER_TRANSPORT, MCP_SERVER_PORT, UNIFI_LOCAL_HOST, UNIFI_API_KEY, AGNOST_ORG_ID, UNIFI_HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
SPEC.md and the current work item in DEVELOPMENT_PLAN.md.Installation goes through your MCP client rather than a global install: point it at unifi-mcp-server on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Unifi's toolset — Objective, Prerequisites, Procedure and 5 more — is a fair guide to whether it matches your workflow. It is maintained by enuno; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Objective | Give operators a fast, safe reading order for understanding what the server does today, what it is becoming, and which docs govern rollout decisions. |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Procedure | 1. Confirm the current stable release and current phase focus. 2. Read SPEC.md for architecture intent and DEVELOPMENT_PLAN.md for sequencing. 3. Use API.md and docs/UNIFI_API.md for implementation surface details. 4. Us |
| Verification | The Verification tool exposed by this server. |
| Rollback | The Rollback tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
| Publishing | The Publishing tool exposed by this server. |
| Configuration | The Configuration tool exposed by this server. |
{
"mcpServers": {
"unifi": {
"url": "http://your-server-ip:3000/sse"
}
}
}Configuration as documented by the project. Restart the client after saving.
SPEC.md and the current work item in DEVELOPMENT_PLAN.md.| Variable | Description | Required |
|---|---|---|
| MCP_SERVER_TRANSPORT | Configuration value read at startup. | Optional |
| MCP_SERVER_PORT | Configuration value read at startup. | Optional |
| UNIFI_LOCAL_HOST | Endpoint or connection string the server talks to. | Optional |
| UNIFI_API_KEY | Credential the server authenticates with. | Yes |
| AGNOST_ORG_ID | Configuration value read at startup. | Optional |
| UNIFI_HOST | Endpoint or connection string the server talks to. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.