No user-submitted related servers found.
Scored across 22 tools
Each tool targets a distinct resource and action: cameras, events, PTZ, auth, lights, sensors, viewers, and chimes are cleanly separated. Pairs like get_camera/list_cameras and get_event_thumbnail(s)/get_camera_snapshot are clearly differentiated by scope in the descriptions.
The vast majority follow unifi_protect_<verb>_<noun> (list_cameras, get_event, export_video), and the prefix is consistent. The auth_* group reverses the order (auth_login, auth_status) and the generic request tool lacks a resource, which are minor but visible deviations.
At 22 tools the server is on the heavy side of the 16-25 borderline range, though the breadth of UniFi Protect resource types explains much of the count. A few could arguably be consolidated, but the scope is broad enough that this is defensible rather than chaotic.
Core read/retrieval workflows are well covered: cameras, snapshots, events, thumbnails, video export, and peripheral devices. However, there are notable gaps in direct write/control operations—no camera settings update or liveview update despite list_liveviews explicitly referencing unifi_protect_update_viewer—and the raw request escape hatch only helps if writes are explicitly enabled.