No user-submitted related servers found.
Scored across 22 tools
Nearly every tool targets a distinct resource+action, and the descriptions actively disambiguate the close pairs (list_cameras vs get_camera, get_event_thumbnail vs get_event_thumbnails, auth_status vs auth_login vs auth_logout). The main residual risk is the singular/plural thumbnail pair and the three-tool auth cluster, which an agent could still pick wrongly under time pressure, but descriptions largely resolve this.
Every tool uses the same unifi_protect_ prefix followed by a consistent snake_case verb_noun pattern (list_cameras, get_event, export_video, check_settings). No mixing of conventions or casing anywhere in the set.
22 tools is at the upper edge, but the domain genuinely spans several device classes (cameras, sensors, chimes, lights, viewers), events, media export, and auth, so most tools earn their slot. It is slightly heavy and could be trimmed (e.g. collapsing the PTZ preset/patrol pair or the thumbnail pair), but not bloated.
Read/monitoring coverage is excellent and explicit gaps (PTZ movement, patrol control) are documented as upstream API limits. However, the surface is essentially read-only — there is no way to change camera settings, arm/disarm, trigger a chime, or update anything, despite check_settings naming the fixes it cannot perform, which is a notable lifecycle gap for a management server.