Go 67a59ba8

MCP浏览器工具

提供方 未标注

浏览器工具 HTTP · 远程 OAuth 授权 社区 / 第三方

全面解析Go Unifi MCPMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,Go Unifi MCP能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

Go 67a59ba8 属于浏览器工具类 MCP 服务器,HTTP · 远程,OAuth 授权,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类浏览器工具 传输方式HTTP · 远程 鉴权OAuth 授权 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

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

能力标签

安装与配置

HTTP · 远程 OAuth 授权
连远程 HTTPS 端点,通常为 Streamable HTTP
  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
自动操作网页

打开页面、点击、填表,把浏览器动作交给模型执行。

抓取结构化数据

把页面内容整理成表格或 JSON,省掉手工复制粘贴。

关键流程回归

按步骤检查页面是否正常,回归时少漏环节。

选择建议

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

值得选的地方

  • 基础信息齐全,可以先按官方文档接入试跑。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在浏览器工具场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Go 67a59ba8当前 未标注 HTTP · 远程 远程部署 无 2026-05-17
Playwright MCP Server 21 stdio · 本地进程 本地部署 有 2026-05-18
Fetch 9a2682de 1 SSE · 服务端推送 支持远程部署 有 2026-05-18
Browser 738d52bc 未标注 stdio · 本地进程 本地部署 有 2026-05-17
MCP 40600ece 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Skyvern MCP 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

浏览器工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类浏览器工具本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

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

go-unifi-mcp

A Model Context Protocol (MCP) server for UniFi Network Controller, written in
Go.

Overview

go-unifi-mcp provides an MCP interface to UniFi Network Controller, enabling
AI assistants and other MCP clients to interact with your UniFi infrastructure.

Why this exists

I couldn’t find an MCP server that supported both v1 and v2 firewall rules and
IPv6, so I built one. This wraps the go-unifi library (which I trust from my
Terraform provider experience) and leans on its generated API surface. The
server is generated from the controller’s own API definitions, which makes it
much easier to keep tool coverage up to date as UniFi evolves.

UniFi controller versioning

This project generates tools against the same UniFi Controller version pinned by
go-unifi. When go-unifi updates its supported controller version, we regenerate
our field definitions and tool metadata to match. We support the same controller
range; see their
controller support range.

Installation

Binary (GitHub Releases)

Download pre-built binaries from the
Releases page. Binaries are
available for macOS and Linux (amd64/arm64).```bash

macOS (Apple Silicon)

curl -L https://github.com/claytono/go-unifi-mcp/releases/latest/download/go-unifi-mcp_darwin_arm64.tar.gz | tar xz
sudo mv go-unifi-mcp /usr/local/bin/

macOS (Intel)

curl -L https://github.com/claytono/go-unifi-mcp/releases/latest/download/go-unifi-mcp_darwin_amd64.tar.gz | tar xz
sudo mv go-unifi-mcp /usr/local/bin/

Linux (amd64)

curl -L https://github.com/claytono/go-unifi-mcp/releases/latest/download/go-unifi-mcp_linux_amd64.tar.gz | tar xz
sudo mv go-unifi-mcp /usr/local/bin/

Linux (arm64)

curl -L https://github.com/claytono/go-unifi-mcp/releases/latest/download/go-unifi-mcp_linux_arm64.tar.gz | tar xz
sudo mv go-unifi-mcp /usr/local/bin/


### Homebrew

Available from the
claytono/homebrew-tap tap:```bash
brew install claytono/tap/go-unifi-mcp

Nix```bash

Run without installing

nix run github:claytono/go-unifi-mcp

Install to your profile

nix profile install github:claytono/go-unifi-mcp


### Docker

Multi-architecture images (amd64/arm64) are published to GitHub Container
Registry.```bash
# Latest (pinned to most recent release, rebuilt on base image updates)
docker pull ghcr.io/claytono/go-unifi-mcp:latest

# Edge (built from main on every merge, unstable)
docker pull ghcr.io/claytono/go-unifi-mcp:edge

Go Install```bash

go install github.com/claytono/go-unifi-mcp/cmd/go-unifi-mcp@latest


## Configuration

### UniFi Credentials

The server requires access to a UniFi Network Controller. Two authentication
methods are supported:

1. **API Key** (preferred): Create an API key in your UniFi controller under
   Settings > Control Plane > Integrations. Set `UNIFI_HOST` and
   `UNIFI_API_KEY`.

2. **Username/Password**: Use a local admin account. Set `UNIFI_HOST`,
   `UNIFI_USERNAME`, and `UNIFI_PASSWORD`.

### Claude Desktop

Add to your `claude_desktop_config.json`:

**Using the binary:**```json
{
  "mcpServers": {
    "unifi": {
      "command": "/usr/local/bin/go-unifi-mcp",
      "env": {
        "UNIFI_HOST": "https://your-controller:443",
        "UNIFI_API_KEY": "your-api-key"
      }
    }
  }
}

Using Docker:```json
{
"mcpServers": {
"unifi": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"UNIFI_HOST",
"-e",
"UNIFI_API_KEY",
"ghcr.io/claytono/go-unifi-mcp:latest"
],
"env": {
"UNIFI_HOST": "https://your-controller:443",
"UNIFI_API_KEY": "your-api-key"
}
}
}
}


### Claude Code```bash
claude mcp add unifi -- go-unifi-mcp

Then set the required environment variables in your shell before running
claude.

Environment Variables

Variable Required Default Description
UNIFI_HOST Yes — UniFi controller URL
UNIFI_API_KEY * — API key (preferred auth method)
UNIFI_USERNAME * — Username for password auth
UNIFI_PASSWORD * — Password for password auth
UNIFI_SITE No default UniFi site name
UNIFI_VERIFY_SSL No true Whether to verify SSL certs
UNIFI_LOG_LEVEL No error go-unifi client log level
UNIFI_TOOL_MODE No lazy Tool registration mode

* Either UNIFI_API_KEY or both UNIFI_USERNAME and UNIFI_PASSWORD must be
set.

Log Levels

The UNIFI_LOG_LEVEL variable controls logging from the underlying go-unifi
client library. The default is error because the client otherwise emits INFO
messages to stderr, which can interfere with tools like mcp-cli that parse JSON
on stdout/stderr.

Level Description
disabled No logging
trace Most verbose, including wire details
debug Debug messages
info Informational messages
warn Warnings only
error Errors only (default)

Tool Modes

The server supports two tool registration modes, following the pattern
established by
unifi-network-mcp:

Mode Tools Context Size Description
lazy 3 ~200 tokens Meta-tools only (default, recommended for LLMs)
eager 252 ~55K tokens All tools registered directly

Lazy mode (default) registers only 3 meta-tools that provide access to 252
UniFi operations (generated from the controller API):

  • tool_index - Search/filter the tool catalog by category or resource
  • execute - Execute any tool by name with arguments
  • batch - Execute multiple tools in parallel

This dramatically reduces context window usage while preserving full
functionality. The LLM first queries the index to find relevant tools, then
executes them via the dispatcher.

Eager mode registers all 252 tools directly, which may be useful for non-LLM
clients or debugging but consumes significant context.

Update semantics: Updates use a read-modify-write flow against the
controller API. We fetch the current resource, merge your fields, and submit the
full object. This avoids clearing unspecified fields, but it is not atomic and
concurrent updates can race (last write wins) because the UniFi API does not
expose etags or revision IDs. In practice this is unlikely to be an issue, but
it's something to be aware of.

ID Resolution

Responses from the UniFi API contain opaque ID references (e.g. network_id,
usergroup_id, networkconf_id). By default, the server resolves these to
human-readable names by looking up the referenced resource and injecting a
sibling _name field:```json
{
"src_networkconf_id": "609fbf24e3ae433962e000de",
"src_networkconf_name": "IOT"
}


Resolution uses a per-request cache, so listing 100 firewall rules that
reference networks only makes one additional `ListNetwork` API call. Typical
overhead is 10-40ms depending on how many distinct resource types are
referenced.

To disable resolution for a specific call, pass `"resolve": false` in the tool
arguments.

### Query Parameters

All list operations support optional post-processing parameters for filtering
and projecting results.

**filter** — Match items by field values. Supports three operators:```jsonc
// Exact match
{"filter": {"type": "usw"}}

// Substring match (case-insensitive)
{"filter": {"name": {"contains": "office"}}}

// Regular expression (RE2 syntax: https://github.com/google/re2/wiki/Syntax)
{"filter": {"name": {"regex": "^ap-.*"}}}

// Multiple conditions (ANDed together)
{"filter": {"type": "uap", "name": {"contains": "echo"}}}

search — Case-insensitive full-text search across all string field values:```json
{ "search": "living room" }


**fields** — Project the response to include only specific keys:```json
{ "fields": ["name", "ip", "mac"] }

Parameters can be combined. Execution order is filter → search → fields, so you
can filter on fields that are excluded from the output:```json
{
"filter": { "type": "uap" },
"search": "echo",
"fields": ["name", "ip"]
}


## Development

### Prerequisites

- Nix with flakes enabled
- direnv (optional but recommended)

### Developing```bash
# Clone the repository
git clone https://github.com/claytono/go-unifi-mcp.git
cd go-unifi-mcp

# Enter the development environment
nix develop
# Or with direnv:
direnv allow

# Install pre-commit hooks
pre-commit install

# Run linters
task lint

# Run tests
task test

# Run tests with coverage
task coverage

Available Tasks```bash

task lint # Run linters via pre-commit
task test # Run tests
task coverage # Run tests with coverage checks
task build # Build the binary
task generate # Run go generate
```

Testing with mcp-cli

The development environment includes
mcp-cli for interactive testing of the
MCP server.

  1. Create .envrc.local with your UniFi credentials (not tracked in git):bash export UNIFI_HOST="https://your-controller:443" export UNIFI_API_KEY="your-api-key" # Or use username/password: # export UNIFI_USERNAME="admin" # export UNIFI_PASSWORD="password"

  2. Build the binary:bash task build

  3. Test with mcp-cli:

The .mcp_servers.json config provides two server entries:
- go-unifi-mcp - eager mode (252 tools)
- go-unifi-mcp-lazy - lazy mode (3 meta-tools)

Eager mode (direct tool access):```bash
# List tools (shows all 252)
mcp-cli info go-unifi-mcp

# Call a tool directly
mcp-cli call go-unifi-mcp list_device '{}'
mcp-cli call go-unifi-mcp list_network '{"site": "default"}'
```

Lazy mode (meta-tools):```bash
# List tools (shows only 3 meta-tools)
mcp-cli info go-unifi-mcp-lazy

# Query the tool index
mcp-cli call go-unifi-mcp-lazy tool_index '{}'
mcp-cli call go-unifi-mcp-lazy tool_index '{"category": "list"}'
mcp-cli call go-unifi-mcp-lazy tool_index '{"resource": "network"}'

# Execute a tool via the dispatcher
mcp-cli call go-unifi-mcp-lazy execute '{"tool": "list_device", "arguments": {}}'

# Batch execute multiple tools
mcp-cli call go-unifi-mcp-lazy batch '{"calls": [{"tool": "list_network", "arguments": {}}, {"tool": "list_device", "arguments": {}}]}'
```

Credits

This project builds upon:

  • go-unifi - Go client library for UniFi
    Network Controller
  • unifi-network-mcp - Python
    MCP server for UniFi that inspired this project
  • mcp-go - Go SDK for Model Context
    Protocol

License

MPL-2.0

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Go 67a59ba8 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Go 67a59ba8 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Go 67a59ba8 收费吗?

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

Go 67a59ba8 需要 API Key 吗?

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

Go 67a59ba8 能提供哪些能力?

资料显示能力标签包括 网络管理、智能家居、API集成、自动化、OAuth认证。具体工具清单以官方文档为准。

Go 67a59ba8 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

Go 67a59ba8 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

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

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