What does this server do vs alternatives?
It is an MCP server, not a UniFi controller. It translates MCP tool calls into UniFi controller API operations, enabling any MCP-compatible LLM or agent to interact with your network.
@sirkirby
基本信息
MCP server implementation for the UniFi network application
使用下面的配置,将此服务器添加到你的 MCP 客户端。
{
"mcpServers": {
"unifi-network-mcp": {
"command": "docker",
"args": [
"pull",
"ghcr.io/sirkirby/unifi-network-mcp:latest"
]
}
}
}工具列表暂未提供
当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。
工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。
A self-hosted Model Context Protocol (MCP) server that turns your UniFi Network Controller into a programmable set of tools. It exposes every capability as standard MCP tools prefixed with unifi_, so any LLM or agent speaking MCP (e.g., Claude Desktop, mcp-cli, LangChain) can query, analyse, and – when explicitly confirmed – modify your network.
Run via Docker using ghcr.io/sirkirby/unifi-network-mcp:latest, or install locally with Python/UV (uv pip install unifi-network-mcp) then launch the mcp-server-unifi-network command. Supply UniFi controller credentials through environment variables (UNIFI_HOST, UNIFI_USERNAME, UNIFI_PASSWORD, etc.) or an .env file. Integrate with Claude Desktop by adding the server to your claude_desktop_config.json.
confirm=true to prevent accidental changes.mcp-server-unifi-network.pyproject.toml and available on PyPI.It is an MCP server, not a UniFi controller. It translates MCP tool calls into UniFi controller API operations, enabling any MCP-compatible LLM or agent to interact with your network.
You need either Docker (to run the pre-built image) or Python ≥3.10 with `uv`/`pip`. The server must be able to reach a UniFi Network Controller over HTTPS.
All data remains in the UniFi controller. The server acts as a pass-through and does not store any network configuration or client data.
The server supports both **stdio** (default for MCP) and **SSE HTTP** (on port 3000 by default). Configuration is set in `src/config/config.yaml`.
Credentials are supplied via environment variables (`UNIFI_HOST`, `UNIFI_USERNAME`, `UNIFI_PASSWORD`, `UNIFI_PORT`, `UNIFI_SITE`, `UNIFI_VERIFY_SSL`) or an `.env` file. No additional authentication layer is provided for the MCP transport.

Model Context Protocol Servers

Model Context Protocol Servers
A search tool helps dev to solve the naming things problem.
Painless E2E Automation for Mobile and Web
A curated list of references for MLOps
评论