{
  "markdown": "# unifi-rmcp\n\nUniFi Network client, device, WLAN, firewall, and health operations over MCP and CLI.\n\nIt exposes one MCP tool, `unifi`, plus the `runifi` CLI. Agents can inspect\nclients, devices, WiFi networks, health, alarms, events, controller sysinfo, and\nauthenticated identity, and can use generated `official_*` / `unifi_*` actions\nwhen their MCP auth scope permits it.\n\n**30-second path:** set `UNIFI_URL` and `UNIFI_API_KEY`, then run\n`npx -y @dinglebear/runifi health --json` -> start loopback HTTP with\n`UNIFI_MCP_HOST=127.0.0.1 npx -y @dinglebear/runifi serve` -> call `tools/call` with\n`{\"action\":\"health\"}`.\n\n**Status:** operational RMCP upstream-client server. The preserved convenience\nactions are read-oriented; generated mutating actions require `unifi:admin`\nauthorization. HTTP MCP supports loopback dev mode, static bearer tokens, and\nGoogle OAuth through `lab-auth`.\n\n**Not for:** replacing the UniFi console, storing controller credentials for\ncallers, bypassing UniFi permissions, generic HTTP proxying, multi-tenant\nisolation, or passing UniFi API keys through MCP tool arguments.\n\n## Contents\n\n- [Naming](#naming)\n- [Capabilities And Boundaries](#capabilities-and-boundaries)\n- [Install](#install)\n- [Quickstart](#quickstart)\n- [Client Configuration](#client-configuration)\n- [Runtime Surfaces](#runtime-surfaces)\n- [MCP Tool Reference](#mcp-tool-reference)\n- [CLI Reference](#cli-reference)\n- [Configuration](#configuration)\n- [Authentication](#authentication)\n- [Safety And Trust Model](#safety-and-trust-model)\n- [Architecture](#architecture)\n- [Distribution Contract](#distribution-contract)\n- [Development](#development)\n- [Verification](#verification)\n- [Deployment](#deployment)\n- [Troubleshooting](#troubleshooting)\n- [Related Servers](#related-servers)\n- [Documentation](#documentation)\n- [License](#license)\n\n## Naming\n\n| Surface | This repo |\n|---|---|\n| Repository | `unifi-rmcp` |\n| Rust crate | `unifi-rmcp` |\n| Binary / CLI | `runifi` |\n| npm package | `@dinglebear/runifi` |\n| npm binary aliases | `unifi-rmcp`, `runifi` |\n| MCP tool | `unifi` |\n| Config home | `~/.unifi-rmcp` on hosts, `/data` in containers |\n| Env prefixes | `UNIFI_*`, `UNIFI_MCP_*`, `UNIFI_RMCP_*` for npm launcher controls |\n\nThe repo and npm package use the RMCP family name, while the shipped binary uses\nthe short Rust CLI name `runifi`.\n\n## Capabilities And Boundaries\n\n- Read connected wireless and wired clients, network devices, WLAN configs,\n  site health, active alarms, recent events, controller sysinfo, and current\n  authenticated user.\n- Dispatch generated `official_*` actions for documented Network Integration API\n  endpoints.\n- Dispatch model-backed `unifi_*` internal controller actions and hybrid aliases\n  such as `list_clients`, `list_devices`, `list_networks`, `list_wifi`, and\n  `get_system_info`.\n- Enforce `unifi:read` for read actions and `unifi:admin` for mutating actions\n  in mounted HTTP MCP mode.\n- Provide setup, doctor, and endpoint-verification commands for local runtime\n  checks.\n\n| This repo owns | UniFi owns | Explicitly out of scope |\n|---|---|---|\n| MCP/CLI projection, action registry, request validation, HTTP MCP auth policy, response shaping, generated action dispatch, setup checks, and endpoint verification. | Controller state, site/device/client data, UniFi users, API key issuance, upstream authorization, and actual network mutations. | Replacing the controller UI, credential brokerage, arbitrary HTTP proxying, long-lived polling, policy-as-code, multi-tenant sandboxing, and local gateway provisioning. |\n\n## Install\n\n| Path | Command | Best for | Notes |\n|---|---|---|---|\n| npm / npx | `npx -y @dinglebear/runifi --help` | Local MCP clients and quick trials. | Downloads the matching `runifi` binary from GitHub Releases. |\n| Release installer | `curl -fsSL https://raw.githubusercontent.com/dinglebear-ai/runifi/main/scripts/install.sh \\| bash` | Host installs without Node. | Installs `runifi` for the current Linux host. |\n| Docker / Compose | `docker compose up -d` | Shared HTTP MCP deployments. | Reads `.env` and exposes container port `40030`. |\n| Build from source | `cargo build --release` | Development and audits. | Produces `target/release/runifi`. |\n| Plugin | `claude plugin install plugins/unifi` | Claude Code local plugin setup from this checkout. | Ships the skill and `.mcp.json`. No session hooks — plugin settings reach the server through `.mcp.json`'s `${user_config.*}` env block, so no manual setup step is needed. |\n\n### npm / npx\n\nRun the stdio MCP server or CLI without a manual binary install:\n\n```bash\nnpx -y @dinglebear/runifi --help\nnpx -y @dinglebear/runifi mcp\nnpx -y @dinglebear/runifi health --json\n```\n\nThe npm package downloads `runifi` during `postinstall`. Override download\nbehavior only when testing packaging:\n\n| Variable | Purpose |\n|---|---|\n| `UNIFI_RMCP_SKIP_DOWNLOAD=1` | Skip postinstall binary download. |\n| `UNIFI_RMCP_VERSION` or `UNIFI_RMCP_BINARY_VERSION` | Select the GitHub Release tag. |\n| `UNIFI_RMCP_REPO` | Select the GitHub repo used for release downloads. |\n| `UNIFI_RMCP_RELEASE_BASE_URL` | Select a custom release base URL. |\n\n### Build From Source\n\n```bash\ngit clone git@github.com:dinglebear-ai/runifi.git\ncd runifi\ncargo build --release\n./target/release/runifi --help\n```\n\nMinimum supported Rust version: 1.86. The Cargo workspace has three members:\nthe root `unifi-rmcp` package, `crates/unifi` (reusable core), and `xtask`\n(dev tooling). All members inherit Rust edition 2024 and MSRV 1.97.1 from the\nworkspace root.\n\n## Quickstart\n\n### 1. Create A UniFi API Key\n\nIn UniFi OS, go to Settings -> Admins & Users -> API Keys, create a key, and\ncopy it into `UNIFI_API_KEY`.\n\n### 2. Configure The Controller\n\n```bash\nexport UNIFI_URL=https://unifi.local\nexport UNIFI_API_KEY=...\nexport UNIFI_SITE=default\nexport UNIFI_SKIP_TLS_VERIFY=true\n```\n\nSet `UNIFI_LEGACY=true` only for older non-UDM controllers that do not use the\n`/proxy/network` path prefix.\n\n### 3. Run A Safe CLI Call\n\n```bash\nnpx -y @dinglebear/runifi health --json\n```\n\n### 4. Start Loopback HTTP MCP\n\n```bash\nUNIFI_MCP_HOST=127.0.0.1 npx -y @dinglebear/runifi serve\n```\n\nIn another shell:\n\n```bash\ncurl -sf http://127.0.0.1:40030/health\n```\n\n### 5. Make A First MCP Call\n\n```bash\ncurl -s -X POST http://127.0.0.1:40030/mcp \\\n  -H \"Content-Type: application/json\" \\\n  -H \"Accept: application/json, text/event-stream\" \\\n  -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools/call\",\"params\":{\"name\":\"unifi\",\"arguments\":{\"action\":\"health\"}}}'\n```\n\n## Client Configuration\n\n### Claude Code Stdio\n\n```json\n{\n  \"mcpServers\": {\n    \"unifi\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"unifi-rmcp\", \"mcp\"],\n      \"env\": {\n        \"UNIFI_URL\": \"https://unifi.local\",\n        \"UNIFI_API_KEY\": \"...\",\n        \"UNIFI_SITE\": \"default\",\n        \"UNIFI_SKIP_TLS_VERIFY\": \"true\"\n      }\n    }\n  }\n}\n```\n\n### Claude Code HTTP\n\n```json\n{\n  \"mcpServers\": {\n    \"unifi\": {\n      \"type\": \"http\",\n      \"url\": \"http://127.0.0.1:40030/mcp\",\n      \"headers\": {\n        \"Authorization\": \"Bearer ${UNIFI_MCP_TOKEN}\"\n      }\n    }\n  }\n}\n```\n\n### Codex / Labby Gateway\n\nRegister UniFi through Labby as an HTTP upstream when sharing one long-running\nserver, or run it directly as stdio for local-only use.\n\n```toml\n[mcp_servers.unifi]\ncommand = \"npx\"\nargs = [\"-y\", \"unifi-rmcp\", \"mcp\"]\n```\n\n### Generic MCP JSON\n\n```json\n{\n  \"command\": \"runifi\",\n  \"args\": [\"mcp\"],\n  \"env\": {\n    \"UNIFI_URL\": \"https://unifi.local\",\n    \"UNIFI_API_KEY\": \"...\"\n  }\n}\n```\n\nDo not put `UNIFI_API_KEY`, OAuth secrets, passwords, SSH keys, or upstream\nbearer tokens in MCP tool arguments. Use env, config files, or the MCP client's\nsecret storage. MCP callers never provide credentials, tokens, keys, or secrets\nas action arguments.\n\n## Runtime Surfaces\n\n| Surface | Status | Entry point | Purpose |\n|---|---:|---|---|\n| MCP stdio | Supported | `runifi mcp`, `npx -y @dinglebear/runifi mcp` | Local child-process MCP clients. |\n| MCP HTTP | Supported | `runifi serve`, `POST /mcp` | Streamable HTTP MCP for local or shared server deployments. |\n| CLI | Supported | `runifi <command>` | Scriptable parity and debugging. |\n| Prompts | Supported | `network_summary` | Agent prompt for UniFi status summaries. |\n| Resource | Supported | MCP tool schema resource | Client-side schema discovery. |\n| REST API | Not shipped | N/A | UniFi already owns the REST APIs. |\n| Web UI | Not shipped | N/A | UniFi already owns the controller UI. |\n\n## MCP Tool Reference\n\nOne MCP tool is exposed: `unifi`. Pass the required `action` argument to select\nthe operation. The action enum is generated from the inventories in `data/`, so\nthe surface is large:\n\n| Family | Actions | Mutating |\n|---|---:|---:|\n| `official_*` | 78 | 36 |\n| `unifi_*` | 175 | 87 |\n| Preserved convenience | 8 | 0 |\n| Hybrid aliases | 5 | 0 |\n| `help` | 1 | 0 |\n| **Total** | **267** | **123** |\n\nCounts are derived from `data/unifi_official_network_v10_3_58.json` and the\n`runtime: true` entries of `data/unifi_internal_endpoint_models.json`.\n`crates/unifi/src/capabilities.rs` is the source of truth at runtime.\n\n### Preserved Convenience Actions\n\n| Action | Description | Required params | Optional params |\n|---|---|---|---|\n| `clients` | Connected wireless and wired clients. | none | none |\n| `devices` | Network devices: APs, switches, gateways. | none | none |\n| `wlans` | WiFi network configurations. | none | none |\n| `health` | Site health summary. | none | none |\n| `alarms` | Active alarms and alerts. | none | none |\n| `events` | Recent controller events. | none | `limit` |\n| `sysinfo` | Controller system information. | none | none |\n| `me` | Authenticated UniFi identity. | none | none |\n| `help` | Built-in action documentation. | none | none |\n\n### Generated Action Families\n\n| Family | Description | Scope behavior |\n|---|---|---|\n| `official_*` | Documented Network Integration API operations under `/proxy/network/integration/v1`. | Read operations require `unifi:read`; mutating operations require `unifi:admin`. |\n| `unifi_*` | Model-backed internal controller-compatible actions under `/proxy/network/api/s/{site}` and `/proxy/network/v2/api/site/{site}`. | Read operations require `unifi:read`; mutating operations require `unifi:admin`. |\n| Hybrid aliases | `list_clients`, `list_devices`, `list_networks`, `list_wifi`, `get_system_info`. | Use internal actions by default, or official API when `siteId` or `params.prefer=\"official\"` is supplied. |\n\nEndpoint coverage is tracked in `docs/unifi_api_coverage.md`; contract and safe\nlive verification are documented in `docs/unifi_endpoint_verification.md`.\n\n## CLI Reference\n\nThe binary calls the same service layer as the MCP tool:\n\n```bash\nrunifi clients [--json]\nrunifi devices [--json]\nrunifi wlans [--json]\nrunifi health [--json]\nrunifi alarms [--json]\nrunifi events [--limit N] [--json]\nrunifi sysinfo [--json]\nrunifi me [--json]\nrunifi official_list_clients --param siteId=<uuid> --json\nrunifi official_create_network --param siteId=<uuid> --body-json '{\"name\":\"IoT\"}' --json\nrunifi list_clients --param siteId=<uuid> --json\nrunifi doctor [--json]\nrunifi setup check [--json]\nrunifi setup repair [--json]\nrunifi setup install [--json]\nrunifi setup plugin-hook [--no-repair] [--json]\n```\n\nGenerated actions accept `--param k=v`, `--body-json JSON`, and `--json`.\n\n`setup plugin-hook` maps `CLAUDE_PLUGIN_OPTION_*` env vars into `UNIFI_*`,\nrefreshes the `~/.local/bin` copy of the binary, and runs check + repair. It\nused to run automatically from a Claude Code `SessionStart`/`ConfigChange`\nhook; those hooks have been removed.\n\nYou do **not** need to run it to configure the plugin: `plugins/unifi/.mcp.json`\nmaps your plugin settings into the server's environment directly via\n`${user_config.*}`. Run it by hand only when you want the `~/.local/bin` binary\nrefresh or the preflight checks.\n\n## Configuration\n\nConfiguration loads from `config.toml` first, then `UNIFI_*` environment\nvariables override it. Host installs read `~/.unifi-rmcp/.env` before loading\nconfig; containers read `/data/.env`. Process environment overrides both.\n\n| Variable | Default | Purpose |\n|---|---|---|\n| `UNIFI_URL` | unset | Controller base URL, e.g. `https://unifi.local`. |\n| `UNIFI_API_KEY` | unset | API key for the `X-API-KEY` header. |\n| `UNIFI_SITE` | `default` | UniFi site name. |\n| `UNIFI_SITE_ID` | unset | Official API site UUID used by live tests and explicit generated calls. |\n| `UNIFI_SKIP_TLS_VERIFY` | `true` | Skip TLS certificate verification for self-signed controllers. |\n| `UNIFI_LEGACY` | `false` | Legacy controller mode without `/proxy/network` prefix. |\n| `UNIFI_MCP_HOST` | `0.0.0.0` | HTTP bind host. |\n| `UNIFI_MCP_PORT` | `40030` | HTTP bind port. |\n| `UNIFI_MCP_TOKEN` | unset | Static bearer token for HTTP MCP. |\n| `UNIFI_MCP_NO_AUTH` | `false` | Disable auth only for loopback development. |\n| `UNIFI_MCP_DISABLE_HTTP_AUTH` | `false` | Compatibility alias for `UNIFI_MCP_NO_AUTH`. |\n| `UNIFI_NOAUTH` | `false` | Trust an upstream gateway to enforce auth. |\n| `UNIFI_MCP_ALLOWED_HOSTS` | empty | Comma-separated `Host` header allowlist. |\n| `UNIFI_MCP_ALLOWED_ORIGINS` | empty | Comma-separated CORS `Origin` allowlist. |\n| `UNIFI_MCP_PUBLIC_URL` | unset | Public URL for OAuth metadata. |\n| `UNIFI_MCP_AUTH_MODE` | `bearer` | `bearer` or `oauth`. |\n| `UNIFI_MCP_GOOGLE_CLIENT_ID` | unset | Google OAuth client ID. |\n| `UNIFI_MCP_GOOGLE_CLIENT_SECRET` | unset | Google OAuth client secret. |\n| `UNIFI_MCP_AUTH_ADMIN_EMAIL` | unset | Admin email for OAuth bootstrap. |\n| `UNIFI_MCP_AUTH_SQLITE_PATH` | `/data/auth.db` | OAuth state database path. |\n| `UNIFI_MCP_AUTH_KEY_PATH` | `/data/auth-jwt.pem` | OAuth JWT signing key path. |\n| `UNIFI_MCP_HOME` | `~/.unifi-rmcp` | Appdata dir override; read by `setup` only. |\n\n`config.toml`-only settings with no environment override: `mcp.server_name`\nand the `[mcp.auth]` TTL, rate-limit, and allowlist fields\n(`access_token_ttl_secs`, `refresh_token_ttl_secs`, `auth_code_ttl_secs`,\n`register_rpm`, `authorize_rpm`, `disable_static_token_with_oauth`,\n`allowed_emails`, `allowed_client_redirect_uris`). See `config.example.toml`.\n\n`xtask` endpoint verification reads its own variables that the server never\ntouches: `UNIFI_ALLOW_INSECURE_TLS`, `UNIFI_RESOLVE_IP`,\n`UNIFI_VERIFY_TIMEOUT_SECS`, `UNIFI_VERIFY_RATE_LIMIT_MS`,\n`UNIFI_VERIFY_MAX_REQUESTS`, `UNIFI_VERIFY_UNVERIFIED_INTERNAL`.\n\n## Authentication\n\nStdio MCP runs as a local trusted child process and does not use HTTP auth.\n\nHTTP MCP auth policy:\n\n| State | Condition | Behavior |\n|---|---|---|\n| Loopback dev | `UNIFI_MCP_HOST` starts with `127.` or auth is explicitly disabled on loopback | Local unauthenticated development is allowed. |\n| Mounted bearer | Non-loopback with `UNIFI_MCP_TOKEN` | Requires `Authorization: Bearer <token>` and action scopes. |\n| Mounted OAuth | `UNIFI_MCP_AUTH_MODE=oauth` | Uses Google OAuth/JWT through `lab-auth`. |\n| Trusted gateway | `UNIFI_NOAUTH=true` | Assumes a reverse proxy or gateway already enforced auth. |\n\n`unifi:admin` satisfies `unifi:read`; `unifi:read` does not satisfy mutating\nactions.\n\n## Safety And Trust Model\n\n- UniFi API keys are loaded from config/env only.\n- MCP callers select actions, params, and request bodies, not upstream\n  credentials.\n- Preserved convenience actions are read-oriented.\n- Generated mutating actions require `unifi:admin` in mounted HTTP MCP mode.\n- Unknown actions and malformed generated-action params fail before upstream\n  calls.\n- Non-loopback HTTP deployments must use bearer auth, OAuth, or a trusted\n  authenticated gateway.\n- This bridge does not sandbox UniFi itself. UniFi remains responsible for API\n  permissions and the actual network-side effect of a mutating call.\n\n## Architecture\n\n```text\nCapabilities   (src/capabilities.rs)   official/internal/hybrid registry\n      |\nUnifiClient    (src/api.rs, src/unifi.rs) HTTP path families and transport\n      |\nUnifiService   (src/app.rs)            action execution boundary\n      |\nMCP shim       (src/mcp/tools.rs)      JSON args -> service -> Value\nCLI shim       (src/cli.rs)            argv -> service -> stdout\n```\n\n## Distribution Contract\n\n- `Cargo.toml`, `Cargo.lock`, `packages/unifi-rmcp/package.json`,\n  `.release-please-manifest.json`, and `server.json` must agree on the released\n  version.\n- GitHub Releases publish the `runifi` binary consumed by the npm launcher.\n- The npm package name is `@dinglebear/runifi`; binary aliases are `@dinglebear/runifi` and\n  `runifi`.\n- Docker/OCI metadata uses `ghcr.io/dinglebear-ai/runifi:<version>`. The GHCR\n  namespace still reads `jmagar` because that is what\n  `.github/workflows/docker-publish.yml` publishes; the git remote is\n  `dinglebear-ai/runifi`. Do not \"fix\" one without the other.\n- `plugins/unifi/.mcp.json` must launch `npx -y @dinglebear/runifi mcp` so stdio\n  clients start the MCP transport rather than the HTTP server.\n- `plugins/unifi/` ships no Claude Code hooks. `scripts/validate-plugin-layout.sh`\n  and `tests/setup_cli.rs` both fail if a `hooks/` directory or a manifest\n  `hooks` key reappears.\n- The root README is curated. Source of truth for current actions and generated\n  endpoint coverage is `src/capabilities.rs`, the `data/` inventories,\n  `docs/unifi_api_coverage.md`, and `docs/unifi_endpoint_verification.md`.\n\n## Development\n\n```bash\ncargo fmt --check\ncargo test\ncargo clippy -- -D warnings\ncargo build --release\nnpm --prefix packages/unifi-rmcp run check\n```\n\n## Verification\n\n```bash\nnpm --prefix packages/unifi-rmcp run check\ncargo check\ncargo test\ncargo clippy -- -D warnings\njust validate-plugin\ncargo run -p xtask -- verify-api-endpoints --mode contract\ngit diff --check\n```\n\nLive read probes require a controller:\n\n```bash\nUNIFI_URL=https://<gateway> \\\nUNIFI_API_KEY=<network-api-key> \\\nUNIFI_SITE=default \\\nUNIFI_SITE_ID=<official-site-uuid> \\\nUNIFI_SKIP_TLS_VERIFY=true \\\ncargo run -p xtask -- verify-api-endpoints --mode safe_live\n```\n\n## Deployment\n\nUse loopback for local development:\n\n```bash\nUNIFI_MCP_HOST=127.0.0.1 runifi serve\n```\n\nUse Docker Compose for shared HTTP deployment:\n\n```bash\ncp .env.example .env\ndocker compose up -d\n```\n\nWhen binding to a non-loopback address, configure `UNIFI_MCP_TOKEN`,\n`UNIFI_MCP_AUTH_MODE=oauth`, or `UNIFI_NOAUTH=true` behind an authenticated\ngateway.\n\n## Troubleshooting\n\n| Symptom | Check |\n|---|---|\n| `UNIFI_URL` or `UNIFI_API_KEY` is missing | Set it in env or `~/.unifi-rmcp/.env`. |\n| TLS errors against a UniFi controller | Keep `UNIFI_SKIP_TLS_VERIFY=true` unless the controller has a trusted certificate. |\n| Legacy controller paths fail | Set `UNIFI_LEGACY=true` for older non-UDM controllers. |\n| HTTP `/mcp` returns unauthorized | Set `UNIFI_MCP_TOKEN` and send `Authorization: Bearer <token>`. |\n| Stdio client hangs or logs JSON errors | Ensure client config runs `unifi-rmcp mcp`, not the default HTTP server mode. |\n| Generated official action needs `siteId` | Pass `--param siteId=<uuid>` or MCP `params.siteId`. |\n| Mutating generated action is forbidden | Use an HTTP MCP token/session with `unifi:admin`. |\n\n## Related Servers\n\nAll sibling servers live under the `dinglebear-ai` org.\n\n- [soma](https://github.com/dinglebear-ai/soma) - RMCP runtime and scaffold for provider-backed MCP servers.\n- [rtailscale](https://github.com/dinglebear-ai/rtailscale) - Tailscale API bridge for devices, users, and tailnet operations.\n- [unraid](https://github.com/dinglebear-ai/unraid) - Unraid monorepo; `unraid-rs/` is the GraphQL bridge (binary `runraid`).\n- [rapprise](https://github.com/dinglebear-ai/rapprise) - Apprise notification fan-out bridge for many delivery backends.\n- [rgotify](https://github.com/dinglebear-ai/rgotify) - Gotify push notification bridge for sends, messages, apps, and clients.\n- [rarcane](https://github.com/dinglebear-ai/rarcane) - Arcane Docker management bridge for containers and related resources.\n- [yarr](https://github.com/dinglebear-ai/yarr) - Media-stack bridge for Sonarr, Radarr, Prowlarr, Plex, and related services.\n- [rytdl](https://github.com/dinglebear-ai/rytdl) - Media download and metadata workflow server.\n- [synapse](https://github.com/dinglebear-ai/synapse) - Local Synapse workflow server for scout and flux actions.\n- [cortex](https://github.com/dinglebear-ai/cortex) - Syslog and homelab log aggregation MCP server.\n- [axon](https://github.com/dinglebear-ai/axon) - RAG, crawl, scrape, extract, and semantic search project.\n- [labby](https://github.com/dinglebear-ai/labby) - Homelab control plane and MCP gateway project.\n\n## Documentation\n\n- `CLAUDE.md` is the curated local operating guide for contributors and agents.\n- `docs/unifi_api_coverage.md` is the curated API-family and coverage summary.\n- `docs/unifi_endpoint_verification.md` is the curated endpoint verification\n  guide.\n- `docs/SETUP.md` is curated plugin/setup guidance.\n- `docs/OAUTH.md` is curated OAuth setup guidance.\n- `plugins/unifi/skills/unifi/SKILL.md` is the agent usage guide.\n- `data/` inventories are generated/reference inputs for the action registry.\n- `src/` is the source of truth for current action dispatch, config defaults,\n  auth behavior, and CLI parsing.\n\n## License\n\nOriginal Dinglebear-authored portions of this project are licensed under [AGPL-3.0-only](LICENSE). Separate commercial licensing is available for organizations that need terms outside the AGPL. Third-party material remains under its original license. See [LICENSING.md](https://github.com/dinglebear-ai/runifi/blob/main/LICENSING.md).\n",
  "bytes": 21554,
  "sha": "cadd5c8954eaa7c4b3ab002165113d4e833c4a4d3add3a6c3d892e30ae9ed8a1",
  "repo_slug": "jmagar/unifi-rmcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_ai_dinglebear_unifi_rmcp_6d38eded/readme"
}