A
licenseNot graded
qualityD
maintenanceExposes the UniFi Network Integration API as MCP tools, dynamically loaded from JSON manifests, with read-only mode by default.
MIT
UniFi Protect MCP
by owine
Related Servers
Alternatives to UniFi Protect MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables interacting with a self-hosted UniFi Protect console through natural language, covering cameras, recorded events, smart detections, snapshots, footage export, and connected devices, with optional write access.2242 npm1MIT
- AlicenseBqualityDmaintenanceProvides 170+ tools to manage UniFi networks via the internal controller API, enabling AI assistants to perform full network management including clients, devices, WLANs, firewall, and more.64MIT
- AlicenseBqualityAmaintenanceExposes the Firewalla MSP API as tools for Claude Code and other MCP clients, enabling natural-language management of Firewalla boxes, alarms, rules, devices, flows, target lists, and trends with full read/write capabilities.19MIT
- AlicenseNot gradedqualityCmaintenanceEnables read-only querying of a UniFi fleet via the Site Manager API and per-console connector proxy, allowing users to list hosts, sites, devices, ISP metrics, and live network clients through Claude.Academic Free v1.1
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query and interact with Extra Low Voltage security hardware such as Hikvision and Dahua cameras and NVRs through typed, read-only-by-default MCP tools for device info, channel enumeration, and JPEG snapshot capture. Translates proprietary ISAPI and CGI protocols into safe, auditable calls that any MCP client can use over stdio.MIT
TDQS
A3.8/5.0
Scored across 38 tools
Disambiguation4/5
Most tools are clearly separated by resource type (list vs get per device category), making selection straightforward. The primary confusion is between protect_list_link_stations and protect_list_alarm_hubs, which return the same field set with alarm hubs explicitly sharing the 'linkstation' modelKey, creating an ambiguous boundary.
Naming Consistency5/5
All tool names follow a uniform protect_verb_noun convention with consistent snake_case, e.g., protect_list_cameras, protect_get_sensor, protect_subscribe_events. There are no mixed casing or irregular verb forms.
Tool Count3/5
38 tools is substantial, and many get/list pairs (e.g., protect_get_light vs protect_list_lights) return identical field sets, making the get tools largely redundant and inflating the count. The breadth of device types justifies some size, but the repetitive pattern suggests the surface could be consolidated.
Completeness2/5
The server covers read operations and subscriptions well, but lacks write/update/delete capabilities for most resources (no liveview creation/update, no device setting changes, no user management). Critically, protect_get_rtsp_streams references protect_create_rtsp_stream, yet that tool is absent, leaving an explicit dead-end in the workflow.
Maintenance
ActivityActive
ResponsivenessNo issues