MCP.so
ログイン

Unifi MCP Server

@enuno

基本情報

カテゴリ

その他

ライセンス

Apache-2.0

トランスポート

stdio

作者

enuno

投稿者

Elvis Nuno

Unifi MCP Server について

An MCP server that leverages official UniFi API

#v0-1-0#v0-1-1#v0-1-2

Unifi MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "unifi": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "UNIFI_API_KEY=$API_KEY",
        "-e",
        "UNIFI_API_TYPE=cloud",
        "ghcr.io/enuno/unifi-mcp-server:latest"
      ]
    }
  }
}

Unifi MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Unifi MCP Server?

A Model Context Protocol (MCP) server that exposes the UniFi Network Controller API and is evolving into a multi-domain platform for Protect, Access, and enterprise-scale orchestration. It is designed for network operators and developers who need programmatic control over UniFi infrastructure.

How to use Unifi MCP Server?

Install via pip: pip install unifi-mcp-server. Set environment variables for API mode (e.g., UNIFI_API_TYPE=local) and transport (e.g., MCP_SERVER_TRANSPORT=stdio), then run unifi-mcp-server. For SSE mode, set MCP_SERVER_TRANSPORT=sse and expose a port.

Key features of Unifi MCP Server

  • Device management (list, restart, locate, upgrade)
  • Network, VLAN, DHCP, and WiFi configuration
  • Client management with block/unblock and analytics
  • Port profile and switch port configuration
  • Firewall rules and ACL management
  • Multi-site aggregation and cross-site statistics
  • 220+ async tool functions across 40+ modules

Use cases of Unifi MCP Server

  • Automate network configuration and updates across sites
  • Monitor device, client, and bandwidth statistics in real time
  • Manage firewall rules and access control lists programmatically
  • Integrate UniFi management with AI assistants via MCP transport
  • Orchestrate multi-site deployments with dry-run and audit logging

よくある質問

1

What API modes are supported?

Three modes: Local Gateway API (full feature, read-write), Cloud Early Access API (site-only, read-only, 100 req/min), and Cloud V1 API (aggregate statistics only, read-only, 10,000 req/min). Recommendation: use Local Gateway API.

2

What transport modes are available?

STDIO (default for local subprocess), SSE (network-accessible HTTP), HTTP, and Streamable HTTP. SSE is best for MCP gateways, STDIO for Claude Desktop and Cursor.

3

What are the runtime requirements?

Python 3.10 or later. Install via `pip install unifi-mcp-server`. For local API, network access to the UniFi gateway (e.g., 192.168.2.1) is required.

4

Where does the server store data?

The server does not store data locally; it communicates with the UniFi controller's API. All device, client, and configuration data resides on the UniFi controller.

5

What are the known limitations of cloud API modes?

Cloud EA and Cloud V1 modes are read-only; they cannot query individual devices or clients, and cannot make configuration changes. They are suitable only for high-level monitoring dashboards.

コメント

「その他」の他のコンテンツ