Lancontrol

io.github.CloudCorpRecords由 GitHub 帳號 CloudCorpRecords 發布v0.1.0更新於 Nov 3, 2026

UniFi控制器：客戶端、裝置、WLAN、健康狀態、告警、事件、sysinfo、身份。

AI 翻譯由 AI 模型根據下方的原文描述翻譯，可能有誤。

原文描述

UniFi controller: clients, devices, WLANs, health, alarms, events, sysinfo, identity.

已驗證STDIO僅桌面

概覽

Lancontrol 的本機 MCP 服務；無需登入；STDIO。

暫無 AI 概覽：以下資訊來自註冊中心條目和服務本身。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Lancontrol，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

lancontrol

lancontrol reads UniFi Network controller state through a single action-router tool: connected clients, network devices, WLAN configurations, site health, active alarms, recent events, controller sysinfo, and the authenticated identity. One binary serves a command-line interface and a stdio MCP server.

This is a labelled core subset. The upstream surface defines 267 actions in total; lancontrol builds only the 8 preserved convenience actions plus help (9 action values). The generated families are omitted, on purpose and by name: official_* (78 actions), unifi_* (175 actions), and the 5 hybrid aliases (list_clients, list_devices, list_networks, list_wifi, get_system_info).

Configuration

Both variables are required for every action except help; a missing value errors before any request is made:

VariableRequiredPurpose
UNIFI_URLyesController base URL, e.g. https://unifi.local.
UNIFI_API_KEYyesAPI key, sent as the X-API-KEY header.
UNIFI_SITEnoUniFi site name. Defaults to default.

Never pass the API key as a tool argument; it is read from the environment only.

Install

bash
npx @reneturcios/lancontrol help

Or run the container image:

bash
docker run -i ghcr.io/cloudcorprecords/lancontrol

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

bash
lancontrol clientslancontrol deviceslancontrol wlanslancontrol healthlancontrol alarmslancontrol events --limit 25lancontrol sysinfolancontrol melancontrol help
lancontrol --version

Action commands print the upstream JSON payload. help prints the local action documentation and needs no configuration and no network. Exit codes: 0 on success, 1 when a call fails (including a missing-config or upstream API error), 2 for usage errors.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

bash
npx -y @reneturcios/lancontrol mcp

MCP client configuration:

json
{  "mcpServers": {    "lancontrol": {      "command": "npx",      "args": ["-y", "@reneturcios/lancontrol", "mcp"],      "env": {        "UNIFI_URL": "https://unifi.local",        "UNIFI_API_KEY": "...",        "UNIFI_SITE": "default"      }    }  }}

Tool

One tool is exposed:

ToolInputWhat it returns
unifiaction (required, one of the 9 subset values), limit (optional integer, events only)The upstream payload for the chosen action, or local documentation for help.
ActionDescription
clientsConnected wireless and wired clients.
devicesNetwork devices: APs, switches, gateways.
wlansWiFi network configurations.
healthSite health summary.
alarmsActive alarms and alerts.
eventsRecent controller events.
sysinfoController system information.
meAuthenticated UniFi identity.
helpBuilt-in action documentation.

Upstream mapping (documented reconstruction)

The public spec names the actions but does not publish, in its convenience-action table, the exact controller path for each one. Each action is therefore implemented as a GET to a plausible documented UniFi internal endpoint under UNIFI_URL, with the X-API-KEY header:

ActionEndpoint
clientsGET /proxy/network/api/s/{site}/stat/sta
devicesGET /proxy/network/api/s/{site}/stat/device
wlansGET /proxy/network/api/s/{site}/rest/wlanconf
healthGET /proxy/network/api/s/{site}/stat/health
alarmsGET /proxy/network/api/s/{site}/stat/alarm
eventsGET /proxy/network/api/s/{site}/stat/event (plus ?_limit={limit} when a limit is supplied)
sysinfoGET /proxy/network/api/s/{site}/stat/sysinfo
meGET /proxy/network/api/self
helpno request — answered locally

HTTP failures surface the status plus the upstream message (meta.msg, message, or error) when present.

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no network (fake fetch fixtures)npm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE.

來源：README.md，提交 b4b926c

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包，因此其工具未知。

版本歷史

1
  1. v0.1.0最新Nov 3, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手；SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分