UniFi RMCP MCP Server

Rust MCP server and CLI for UniFi Network controller operations. That is what the unifi rmcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

MCP server and CLI for UniFi Network controllers: clients, devices, WLANs, firewall, and health over stdio or streamable HTTP, with auth.

• Read connected wireless and wired clients, network devices, WLAN configs,
• Dispatch generated official_* actions for documented Network Integration API
• Dispatch model-backed unifi_* internal controller actions and hybrid aliases
• Enforce unifi:read for read actions and unifi:admin for mutating actions
• Provide setup, doctor, and endpoint-verification commands for local runtime

Getting it running

Installation goes through your MCP client rather than a global install: point it at @dinglebear/runifi on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What it needs from you

Configuration is passed through the environment: UNIFI_URL, UNIFI_API_KEY, UNIFI_SITE, UNIFI_SKIP_TLS_VERIFY, UNIFI_MCP_HOST, UNIFI_RMCP_RELEASE_BASE_URL, UNIFI_MCP_TOKEN, UNIFI_SITE_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by ai.dinglebear; 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.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.