UniFi RMCP

Rust MCP server and CLI for UniFi Network controller operations.

UniFi RMCP is a Rust-implemented MCP server and command-line interface for interacting with a UniFi Network controller. It communicates over stdio transport and is distributed as an npm package (version 0.2.4) by publisher ai.dinglebear, with source available at the linked GitHub repository.

The server is configured through environment variables: UNIFI_URL points to the controller endpoint, UNIFI_API_KEY supplies the authentication credential, and UNIFI_RMCP_VERSION, UNIFI_RMCP_REPO, and UNIFI_RMCP_RELEASE_BASE_URL control which release binary is used. RUST_LOG can be set to adjust logging verbosity at runtime.

No tool definitions were present in the registry record for this version, which means the specific operations the server exposes to an agent — such as querying devices, managing clients, or reading network statistics — are not confirmed from available facts. Agents connect to it via stdio, so any orchestration layer that supports stdio-based MCP servers can integrate with it.

This server is appropriate when the goal is to give an AI agent programmatic access to a UniFi Network controller using an MCP-compatible runtime. It is not appropriate for network controllers from other vendors, and it is not suitable for setups that require a networked (SSE or HTTP) transport rather than stdio.

Use cases

  • Connect an AI agent to a self-hosted UniFi Network controller for automated network management
  • Integrate UniFi controller operations into an MCP-compatible orchestration pipeline
  • Use the CLI interface to interact with UniFi controller from the command line in a scripted workflow
  • Configure controller access via environment variables for containerised or CI deployments

When to use it

  • The target system is a UniFi Network controller reachable at a known URL with an API key
  • The agent runtime supports stdio-based MCP servers
  • A Rust-compiled binary approach is acceptable for the deployment environment

When not to use it

  • The network infrastructure uses a controller from a vendor other than UniFi
  • The deployment requires an SSE or HTTP transport instead of stdio
  • Specific tool capabilities need to be confirmed before integration, as no tool definitions are present in the current registry record
  • A license requirement must be met — no license is specified in the registry record