unifi-network-setup

To configure UniFi Network controller access for Claude Code, you provide the controller host and credentials through an interactive setup process that writes the resulting environment variables to the correct local MCP server configuration file.

Yes, you can restrict MCP server permissions to read-only UniFi API access by selecting a read-only permission policy during setup, or progressively enable specific write capabilities like firewall, port forwards, and QoS using explicit policy variables.

Yes, UniFi MCP setup supports an optional, experimental API key mode for network automation, allowing you to configure read-oriented API key access instead of standard username and password authentication.

The best way to write UniFi controller credentials to different MCP clients is using target-aware setup logic that detects whether you are using Claude Code, Codex, or OpenClaw and updates the corresponding local configuration automatically.

Yes, you need to run prerequisite checks before setting up UniFi Network MCP by executing the check-prereqs.sh script, which verifies your environment is ready before running the target-aware set-env.sh configuration script.

On Windows, UniFi MCP setup handles environment variables by using platform-specific MCP commands instead of the set-env.sh script, ensuring the controller host and credentials are written correctly to the Windows client configuration.