UniFi Network MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 18 444 installs a week from pypi. Last commit 17 Sep 2026.
Manage UniFi Network devices, clients, firewall, VLANs, VPNs, and more via MCP.
We read the source, 20 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
этот файл ставится пользователю, но в репозитории его нет
<select id="f_{{ name }}" name="{{ name }}">
{% for opt_value, opt_label in options %}
subprocess.run(
env = dict(os.environ)
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
…eway --user '"${MCP_GATEWAY_UID}"':'"${MCP_GATEWAY_GID}"' --group-add '"${DOCKER_SOCK_GID}"' -v '"${DOCKER_SOCK_PATH}"':/var/run/docker.sock -e MCP_GATEWAY_PORT -e MCP_GATEWAY_DOMAIN -e MCP_GATEWAY_AGENT_ID -e MCP_GATEWAY_PAYLOAD_DIR -e MCP_GATEWAY_PAYLOAD_SIZE_THRESHOLD -e DOCKE…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add unifi-network-mcp -- uvx unifi-network-mcp
{
"mcpServers": {
"unifi-network-mcp": {
"args": [
"unifi-network-mcp"
],
"command": "uvx"
}
}
}
[mcp_servers.unifi-network-mcp]
command = "uvx"
args = ["unifi-network-mcp"]
{
"mcpServers": {
"unifi-network-mcp": {
"args": [
"unifi-network-mcp"
],
"command": "uvx"
}
}
}
{
"mcpServers": {
"unifi-network-mcp": {
"args": [
"unifi-network-mcp"
],
"command": "uvx"
}
}
}
This one needs environment variables set before it will start:
UNIFI_HOST (Controller IP/hostname), UNIFI_USERNAME (Admin username), UNIFI_PASSWORD (Admin password), UNIFI_API_KEY (API key (optional, experimental)), UNIFI_PORT (Controller HTTPS port), UNIFI_VERIFY_SSL (SSL certificate verification), UNIFI_SITE (UniFi site name).
The author declared them in the registry entry; get the values from the project itself.
Manage UniFi sites, devices, clients, networks, port forwarding, DNS, and firewall
Manage UniFi Access doors, credentials, policies, visitors, and events via MCP.
MCP server for the Hetzner Cloud API — servers, networks, volumes, firewalls, and more.
Manage UniFi Protect cameras, events, recordings, and smart detections via MCP.
MCP server for Domotz network monitoring — agents, devices, alerts, and network discovery.
MCP server for Domotz network monitoring — agents, devices, alerts, and network discovery.
Manage pfSense firewalls through AI assistants — rules, DHCP, DNS, and more
MCP server for LibreNMS network monitoring - query devices, ports, alerts, and manage infrastructure
Answers built from our own checks of this server.