Unifi MCP Server 1b14d571

MCPAI代理

提供方 enuno

AI代理 stdio · 本地进程 API Key 社区 / 第三方 Claude DesktopClaudeCursor
查看接入方式

一个暴露UniFi网络控制器API的模型上下文协议(MCP)服务器,使AI代理和应用程序能够以标准化方式与UniFi网络基础设施交互。

一句话选型结论

按资料字段整理

Unifi MCP Server 1b14d571 属于AI代理类 MCP 服务器,stdio · 本地进程,API Key,可直接接入 Claude Desktop、Claude、Cursor,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式stdio · 本地进程 鉴权API Key 部署方式本地部署
GitHub 星标 131 仓库热度,无公开仓库时显示未标注
工具数 73 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量73暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

网络管理Python本地部署AI集成UniFiAPI服务MCP协议API网关

安装与配置

stdio · 本地进程 API Key
客户端在本机拉起子进程,数据不出本机
pip install unifi-mcp-server

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 73 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 73 个工具,覆盖面较广,能满足多种调用。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Unifi MCP Server 1b14d571当前 73 stdio · 本地进程 本地部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方enuno上游标注的维护方 enuno
分类AI代理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

20.9 KB
来自项目仓库与上游目录的原文,未做删改

UniFi MCP Server

AI-native control of UniFi networks through the Model Context Protocol

An MCP server that exposes UniFi Network, UniFi Protect and the UniFi cloud APIs (Site Manager, Mobility, InnerSpace, Carrier Fabric) as MCP tools, so AI agents can read and change UniFi infrastructure through one standard interface. It runs against one controller or, in fleet mode, many.

Current release: 0.6.4. See CHANGELOG.md for what changed.

Contents

  • Features
  • API modes
  • Quick start
  • Agent skills
  • Tool profiles and safety controls
  • Network transports and deployment
  • Calling the server from code
  • Native MCP prompts
  • Documentation
  • Development

Features

343 tools in local mode, from 60 modules.

  • Network: clients (search, block, reconnect), networks and VLANs, WiFi SSIDs, DHCP reservations, DNS, WAN, guest vouchers, QoS profiles and traffic routes, DPI statistics, traffic flows.
  • Devices: inventory, adoption, restart, locate, upgrade, radio settings, port profiles and per-port overrides, switching and stacks, topology export (JSON, GraphML, DOT), diagnostics, WiFi channel planning.
  • Security: legacy firewall rules and groups, zone-based firewall (zones, policies, zone matrix), ACL rules, traffic matching lists, port forwarding, VPN and site-to-site VPN, content filtering, RADIUS and the guest portal.
  • Protect: cameras, NVRs, views, events, sensors, lights, chimes, sirens, relays, speakers, alarm hubs and the alarm manager.
  • Cloud: Site Manager (hosts, sites, cross-site statistics), the connector proxy, Mobility workspaces and devices, InnerSpace floor plans and inventory, Carrier Fabric subscribers and service plans.
  • Operations: sites, backups (create, schedule, download, restore), events, multi-site aggregation, device migration between sites.
  • Fleet mode (optional, with Postgres and Redis): many controllers behind one server, a controller registry with encrypted credentials, server-issued tokens with roles, a shared read cache, several replicas and background workers, and fleet_* tools that read across controllers. See MULTI_CONTROLLER.md and docs/FLEET_SCALING_PLAN.md.
  • Native prompts: eight parameterised UniFi operational workflows (health check, client connectivity, WiFi performance, device investigation, firewall review, change planning, Protect health, fleet summary) exposed through the standard prompts/list and prompts/get operations. See docs/PROMPTS.md.
  • Safety: every mutating tool needs confirm=True and supports dry_run=True, plus read-only and dry-run server modes, role-based access over risk tiers, and a hash-chained audit log (see below).
  • A2A discovery and delegation: an agent card built from the live tool registry, served at /a2a/agent-card and /.well-known/agent-card.json, plus a capability manifest and a delegation endpoint that runs a registered tool under the server's own role, confirmation and audit controls. See A2A.md.
  • Observability: Prometheus /metrics, /healthz, SIEM export of audit records, optional Redis caching, webhooks with HMAC verification.

API modes

Set UNIFI_API_TYPE to choose how the server reaches UniFi.

Mode What it reaches Use it for
local (recommended) Your UniFi console or gateway on the LAN (UNIFI_LOCAL_HOST) Everything: device and client control, configuration, firewall, Protect
cloud-ea UniFi's Early Access cloud API Sites and aggregate statistics; no per-device control or configuration
cloud-v1 UniFi's stable v1 cloud API Sites and aggregate statistics; no per-device control or configuration

The cloud tools (Site Manager, Mobility, InnerSpace, Carrier Fabric) call api.ui.com and are registered in every mode. Set UNIFI_SITE_MANAGER_ENABLED=true to use them. In local mode the server registers 343 tools; in either cloud mode, 71.

Zone-based firewall tools need UniFi Network 9.0 or later. Some documented UniFi endpoints do not exist on every firmware version; see docs/UNIFI_API.md.

UniFi Network 11 / UniFi OS 6: compatible per released documentation, with four items pending live-controller verification — not yet a claim of full support. USG gateways and the classic, self-hosted Network Application Server are removed platform targets; fleet_health automatically flags any registered controller with a USG in its device inventory, but there is no API signal to auto-detect a classic Network Application Server, so label that controller instead (e.g. deployment=classic-server) and filter on it. See docs/NETWORK_11_COMPATIBILITY.md for the full compatibility matrix.

Quick start

1. Get an API key

  1. Sign in to UniFi Site Manager.
  2. Go to Settings → Control Plane → Integrations and choose Create API Key.
  3. Copy the key. It is shown only once.

2. Install```bash

pip install unifi-mcp-server # or: uv tool install unifi-mcp-server

Fleet mode extras (Postgres, Redis):

pip install 'unifi-mcp-server[fleet]'


Or use the container image (amd64, arm64 and arm/v7; the `-fleet` variant for amd64 and arm64):```bash
docker pull ghcr.io/enuno/unifi-mcp-server:latest

3. Add it to your MCP client

Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows), Cursor (mcp.json, from View: Open MCP Settings) and most other MCP clients take the same mcpServers block:```json
{
"mcpServers": {
"unifi": {
"command": "uvx",
"args": ["unifi-mcp-server"],
"env": {
"UNIFI_API_KEY": "<your-api-key>",
"UNIFI_API_TYPE": "local",
"UNIFI_LOCAL_HOST": "192.168.2.1"
}
}
}
}


If you installed with `pip`, use `&quot;command&quot;: &quot;unifi-mcp-server&quot;` and drop `args`. To run the container instead:```json
{
  &quot;mcpServers&quot;: {
    &quot;unifi&quot;: {
      &quot;command&quot;: &quot;docker&quot;,
      &quot;args&quot;: [
        &quot;run&quot;, &quot;-i&quot;, &quot;--rm&quot;,
        &quot;-e&quot;, &quot;UNIFI_API_KEY=your-api-key-here&quot;,
        &quot;-e&quot;, &quot;UNIFI_API_TYPE=local&quot;,
        &quot;-e&quot;, &quot;UNIFI_LOCAL_HOST=192.168.2.1&quot;,
        &quot;ghcr.io/enuno/unifi-mcp-server:latest&quot;
      ]
    }
  }
}

Keep -i and do not add -d: the client talks to the server over the container's stdin and stdout.

4. Main settings

Variable Purpose Default
UNIFI_API_KEY UniFi API key (required) —
UNIFI_API_TYPE local, cloud-ea or cloud-v1 cloud-ea
UNIFI_LOCAL_HOST / UNIFI_LOCAL_PORT Console address in local mode — / 443
UNIFI_LOCAL_VERIFY_SSL Verify the console's TLS certificate. false logs a warning at startup true
UNIFI_LOCAL_CA_FILE CA certificate (PEM) for a self-signed console, instead of turning verification off —
UNIFI_DEFAULT_SITE Site used when a tool call names none default
UNIFI_SITE_MANAGER_ENABLED Enable the cloud tools (Site Manager, Mobility, InnerSpace, Carrier) false
UNIFI_PROFILE Register only one group of tools (profiles) all
UNIFI_READ_ONLY / UNIFI_DRY_RUN Read-only or preview-only server false
DEBUG Registers debug_api_request (raw GET/DELETE, destructive tier, removed by read-only). Leave unset in production unset
MCP_SERVER_TRANSPORT stdio, streamable_http, http or sse stdio
MCP_AUTH_TOKEN Bearer token, required on network transports; viewer: (or operator:, admin:) limits a token's role —
REDIS_URL Optional response cache —
WEBHOOK_SECRET HMAC secret for incoming UniFi webhooks —
DATABASE_URL Turns on fleet mode (Postgres) —

.env.example lists every setting with comments, including audit logging, SIEM export, metrics, Supermemory and agnost.ai.

Agent skills

The skills/ directory holds agent skills: Markdown files an AI agent loads on demand, so it knows which UniFi tools exist and how to use them safely without keeping every tool definition in context. Each skill is a folder with a SKILL.md, in the layout Claude Code and other agents install.

Using the server (operator skills)

Skill Covers
unifi-network Clients, networks and VLANs, WiFi, DHCP, DNS, WAN, vouchers
unifi-devices Inventory, adoption, restarts and upgrades, ports, switching, topology
unifi-security Firewall rules and groups, zone-based firewall, ACLs, port forwarding, VPN
unifi-system Sites, backups, QoS, traffic flows, DPI, RADIUS, guest portal
unifi-channel-planning Low-interference WiFi channel plans from neighbor scans

Changing this codebase (developer skills)

Skill Covers
unifi-mcp-tool-builder Adding any MCP tool: model, function, registration, tests, docs
unifi-network-config-tools Network configuration tools: URL spaces, site IDs, read-modify-write
unifi-security-tools Firewall, ZBF, ACL and port forward tools, and their risk tiers
unifi-protect-tools The protect_* modules and the Protect client
unifi-cloud-fleet-tools Cloud API tools and the fleet stack

Install

Claude Code loads skills from ~/.claude/skills//SKILL.md (every session) or /.claude/skills//SKILL.md (one project). Copy the folders you want:```bash
git clone https://github.com/enuno/unifi-mcp-server.git
cd unifi-mcp-server
mkdir -p ~/.claude/skills

All operator skills

cp -r skills/unifi-network skills/unifi-devices skills/unifi-security \
skills/unifi-system skills/unifi-channel-planning ~/.claude/skills/

Or one skill

cp -r skills/unifi-security ~/.claude/skills/

The one-file overview of the whole server, as a skill named "unifi"

mkdir -p ~/.claude/skills/unifi && cp SKILL.md ~/.claude/skills/unifi/SKILL.md


Other agents that read the same `SKILL.md` format take the same folders; copy them into that agent&#x27;s skills directory (Codex, for example, reads `.agents/skills/`). To update, pull and copy again. Inside this repository the developer skills are already installed for Claude Code (`.claude/skills/`) and Codex (`.agents/skills/`).

### Use

You don&#x27;t invoke a skill yourself. The agent reads each skill&#x27;s description and loads the one that matches your request, then calls the MCP tools it describes, so the MCP server must also be configured in the same client. For example:

- &quot;Which clients are on the guest VLAN right now?&quot; loads `unifi-network`.
- &quot;Audit the zone-based firewall for anything that allows WAN to LAN.&quot; loads `unifi-security`.
- &quot;Which APs share a 5 GHz channel with a neighbor? Propose a channel plan.&quot; loads `unifi-channel-planning`.

If the agent doesn&#x27;t pick a skill up, name it (&quot;use the unifi-security skill&quot;). Pair a skill with the matching `UNIFI_PROFILE` to keep the tool list small too. docs/SKILLS.md has the full guide.

## Tool profiles and safety controls

**Profiles.** `UNIFI_PROFILE` registers only one group of modules, so the client sees fewer tool definitions:

| Profile | Tools | Covers |
|---|---|---|
| `network` | 48 | Clients, networks, WiFi, DHCP, DNS, WAN, vouchers, channel planning |
| `devices` | 53 | Devices, control, migration, ports, switching, topology, diagnostics |
| `security` | 47 | Firewall, ZBF, ACLs, port forwarding, VPN, content filtering |
| `system` | 182 | Sites, backups, events, DPI, QoS, RADIUS, traffic flows, Protect, cloud |
| `protect` | 75 | The Protect modules |
| `mobility` / `innerspace` / `carrier` | 12 / 10 / 15 | One cloud API each |
| `minimal` | 19 | Sites, clients, devices |

Counts include the four fleet tools every profile gets. An unknown profile logs a warning and loads everything.

**Safety controls.**

- Every mutating tool requires `confirm=True`, and `dry_run=True` returns the change it would make without making it.
- `UNIFI_READ_ONLY=true` leaves mutating tools out of the tool list entirely. `UNIFI_DRY_RUN=true` forces every mutating call into preview mode.
- `DEBUG=true` adds `debug_api_request`, a raw GET or DELETE to any controller endpoint. It is a destructive-tier tool, a DELETE needs `confirm=True`, and read-only mode removes it. Leave `DEBUG` unset in production.
- With tokens, each tool has a risk tier (`read`, `write`, `destructive`) and each role a set of tiers: `viewer` reads, `operator` writes, and `admin` can also run destructive tools, including deletes, restores, restarts, client blocking and firewall policy changes. See API.md.
- Mutations are written to a hash-chained JSON-lines audit log (Postgres in fleet mode), with optional field encryption and SIEM export. See SECURITY.md.
- Inputs are validated with Pydantic, and credentials are redacted from logs.

## Network transports and deployment

`stdio` is the default and needs no port. To serve MCP over the network, use Streamable HTTP:```bash
export MCP_SERVER_TRANSPORT=streamable_http
export MCP_SERVER_PORT=3000
export MCP_AUTH_TOKEN=$(openssl rand -hex 32)   # required on every network transport
unifi-mcp-server
# Listening on 127.0.0.1:3000; clients send Authorization: Bearer $MCP_AUTH_TOKEN

Clients and MCP gateways then connect to http://:3000/mcp. The server binds to 127.0.0.1 unless you set MCP_SERVER_HOST; put an authenticating TLS proxy in front before exposing it further. http also works. sse is deprecated: client proxies such as mcp-remote can race its initialize handshake (#96).

Container, with the published port on loopback:```yaml
services:
unifi-mcp:
image: ghcr.io/enuno/unifi-mcp-server:latest
environment:
UNIFI_API_KEY: your-api-key
UNIFI_API_TYPE: local
UNIFI_LOCAL_HOST: 192.168.2.1
MCP_SERVER_TRANSPORT: streamable_http
MCP_SERVER_PORT: 3000
MCP_SERVER_HOST: 0.0.0.0 # inside the container only
MCP_AUTH_TOKEN: ${MCP_AUTH_TOKEN}
ports:
- "127.0.0.1:3000:3000"


The repository&#x27;s docker-compose.yml adds Redis and the MCP Toolbox dashboard (MCP_TOOLBOX.md); copy `.env.docker.example` to `.env` and run `make compose-up`. That example starts read-only (`UNIFI_READ_ONLY=true`) with a `viewer` stdio caller (`UNIFI_STDIO_ROLE=viewer`); to allow changes, set `UNIFI_READ_ONLY=false` and raise `UNIFI_STDIO_ROLE` to `operator`, or `admin` for destructive changes.

- **Ansible:** deploy/ansible/ deploys the server alone, a single-host fleet (server, worker, Redis, Postgres), or replicas behind nginx on several hosts. To have an AI agent run the deployment, start from a prompt in docs/deploy-prompts/.
- **Kubernetes:** deploy/helm/unifi-mcp/ is a Helm chart for the server alone or in fleet mode with workers, taking every credential from an existing Secret.
- **Local dev deployment (either method):** `make helm-deploy-local` or `make ansible-dev-deploy` build the current working tree — including uncommitted changes — tag it `local-[-dirty]`, and deploy it for real, instead of pulling or building from a published release. See the &quot;Deploying from a local checkout&quot; / &quot;Local dev deployment&quot; sections in the two overview docs above.

## Calling the server from code

Any MCP client library works. With the FastMCP client:```python
import asyncio

from fastmcp import Client

config = {
    &quot;mcpServers&quot;: {
        &quot;unifi&quot;: {
            &quot;command&quot;: &quot;unifi-mcp-server&quot;,
            &quot;env&quot;: {
                &quot;UNIFI_API_KEY&quot;: &quot;&lt;your-api-key&gt;&quot;,
                &quot;UNIFI_API_TYPE&quot;: &quot;local&quot;,
                &quot;UNIFI_LOCAL_HOST&quot;: &quot;192.168.2.1&quot;,
            },
        }
    }
}

async def main() -&gt; None:
    async with Client(config) as client:
        sites = await client.call_tool(&quot;list_sites&quot;, {})
        print(sites.data)

        clients = await client.call_tool(&quot;list_active_clients&quot;, {&quot;site_id&quot;: &quot;default&quot;})
        print(clients.data)

        # Mutations need confirm=True; dry_run=True previews the change.
        preview = await client.call_tool(
            &quot;create_firewall_zone&quot;,
            {&quot;site_id&quot;: &quot;default&quot;, &quot;name&quot;: &quot;IoT&quot;, &quot;confirm&quot;: True, &quot;dry_run&quot;: True},
        )
        print(preview.data)

asyncio.run(main())

bin/unifi-cli runs a single tool from a shell (unifi-cli list-clients --site default); see docs/SKILLS.md.

Native MCP prompts

Besides the tools, the server exposes eight parameterised UniFi operational
workflows through the standard MCP prompts interface. A client discovers them
with prompts/list and retrieves a rendered workflow brief with prompts/get.```python
import asyncio

from fastmcp import Client

config = {
"mcpServers": {
"unifi": {
"command": "unifi-mcp-server",
"env": {
"UNIFI_API_KEY": "<your-api-key>",
"UNIFI_API_TYPE": "local",
"UNIFI_LOCAL_HOST": "192.168.2.1",
},
}
}
}

async def main() -> None:
async with Client(config) as client:
for prompt in await client.list_prompts():
print(prompt.name, prompt.description)

    result = await client.get_prompt(
        &quot;network_health_check&quot;,
        {&quot;site_id&quot;: &quot;default&quot;, &quot;focus&quot;: &quot;wan&quot;},
    )
    for message in result.messages:
        print(message.content.text)

asyncio.run(main())


The prompts are `network_health_check`, `troubleshoot_client_connectivity`,
`troubleshoot_wifi_performance`, `investigate_device`,
`review_firewall_policy`, `plan_network_change`, `protect_health_check` and
`fleet_health_summary`. A workflow is advertised only when the tools it needs
are registered on this server, so the prompt list follows the API mode, the
profile and the read-only and dry-run settings.

Retrieving a prompt does **not** run the workflow and grants no approval. The
rendered text tells an agent which read tools to call and what to report; the
agent calls the tools itself, and the server&#x27;s role checks, `confirm` gate and
audit trail still apply.

Use `make inspect` to open the MCP Inspector and browse the prompts, or the
MCPJungle CLI to check what the gateway forwards:```bash
mcpjungle list prompts --server unifi
mcpjungle get prompt unifi__network_health_check --arg site_id=default

A tools-only client will not display the prompts; that is a client limitation.
There is no prompts-as-tools shim.

See docs/PROMPTS.md for the full catalog, the availability
matrix, the validation rules and the manual acceptance steps.

Documentation

Document Contents
API.md Every MCP tool and resource, with parameters and examples
docs/PROMPTS.md The native MCP prompt catalog, with arguments and availability rules
A2A.md The agent card, the capability manifest and the delegation endpoint
docs/AUDIT_A2A_SKILLS.md The A2A and skills audit: what was implemented, what was not, and why
docs/SKILLS.md Agent skills, profiles and the CLI wrapper
docs/UNIFI_API.md The UniFi endpoints behind the tools
MULTI_CONTROLLER.md Fleet mode: controllers, tokens and roles
METRICS.md, WEBHOOK_SETUP.md, A2A.md Metrics, webhooks, the A2A agent endpoints
NETWORK_PLAYBOOK.md, HARBOR_SETUP.md Operating runbooks
SECURITY.md Reporting vulnerabilities, audit logging and hardening
SPEC.md, DEVELOPMENT_PLAN.md, ROADMAP.md Architecture target and roadmap
CHANGELOG.md, docs/RELEASE_PROCESS.md Release history and how releases are cut and published

Development```bash

git clone https://github.com/enuno/unifi-mcp-server.git
cd unifi-mcp-server
make install # uv sync from uv.lock with the dev extra (no activation needed)
make hooks # pre-commit and commit-msg hooks
cp .env.example .env # then set UNIFI_API_KEY and, for local mode, UNIFI_LOCAL_HOST

make test # unit tests
make ci # every blocking CI check: lint, typecheck, security, docs coverage, tests with the 80% gate
make inspect # open the server in the MCP Inspector (needs Node.js)
make help # list every target
```

Without make, the same commands run through uv run --locked, for example uv run --locked pytest tests/unit/ -m &quot;not integration&quot;. Integration tests (-m integration) need real UniFi hardware.

Layout: src/main.py builds the server, src/tools/ holds the tool modules, src/api/ the UniFi clients, src/models/ the Pydantic models, src/fleet/ the fleet stack, and tests/unit/ the unit tests. AGENTS.md and CLAUDE.md describe the conventions in detail, and commands.md lists the development commands.

Contributing

Contributions from people and AI coding agents are welcome. See CONTRIBUTING.md and AGENTS.md.

  1. Fork the repository and create a branch.
  2. Write tests first, keep new code at 80% coverage or better, and run make ci.
  3. Use conventional commit messages (feat: ..., fix: ...) and open a pull request.

Issues with [Bug] in the title opened by a maintainer or collaborator get an automated first analysis; other reports are triaged by hand (details).

Security

Report vulnerabilities as described in SECURITY.md. Never commit credentials.

Acknowledgments

  • sirkirby/unifi-network-mcp, the reference implementation
  • MakeWithData's UniFi MCP guide
  • Model Context Protocol and FastMCP

License

Apache License 2.0. See LICENSE.

Links

  • Issues and discussions: GitHub Issues, GitHub Discussions
  • Releases:
  • PyPI:
  • Container images:
  • MCP Registry: search for io.github.enuno/unifi-mcp-server at

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Unifi MCP Server 1b14d571 怎么安装?

在客户端按下面的安装命令接入:pip install unifi-mcp-server。装完在客户端配置里引用同一个包或端点。

Unifi MCP Server 1b14d571 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Unifi MCP Server 1b14d571 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Unifi MCP Server 1b14d571 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Unifi MCP Server 1b14d571 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Unifi MCP Server 1b14d571 能提供哪些能力?

资料显示约 73 个工具;能力标签包括 网络管理、API集成、Python、Claude、API网关。具体工具清单以官方文档为准。

Unifi MCP Server 1b14d571 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

Unifi MCP Server 1b14d571 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。