unifilisted

# UniFi Skill (unifi-rmcp) Access to a UniFi network controller via the **unifi-rmcp** MCP server. Data is fetched from the documented Network Integration API or internal controller APIs using X-API-KEY authentication. Mutating actions require MCP admin authorization. ## Quick Reference All operations use a single `unifi` MCP tool with an `action` parameter: ``` unifi(action="clients") # who's connected unifi(action="devices") # APs, switches, gateways unifi(action="health") # site health summary unifi(action="wlans") # WiFi network configs unifi(action="alarms") # active alarms unifi(action="events") # recent controller events unifi(action="sysinfo") # controller version/uptime unifi(action="me") # authenticated user info unifi(action="help") # built-in documentation ``` Generated action families are also available: ``` unifi(action="official_list_clients", params={"siteId": "<uuid>"}) unifi(action="unifi_list_alarms") unifi(action="list_clients", params={"siteId": "<uuid>"}) unifi(action="list_clients", params={"prefer": "internal"}) ``` Action surface summary: - `official_*`: 78 documented Network Integration API operations; mutating operations require admin authorization. - `unifi_*`: model-backed internal controller actions; runtime rows are exposed as endpoint actions. - Hybrid actions: read convenience actions that choose internal by default and official when