Agent skill
unifi-protect
How to manage UniFi Protect cameras and NVR — view cameras, smart detections, recordings, snapshots, lights, sensors, and the Alarm Manager. Use this skill when the user mentions UniFi cameras, security cameras, NVR, recordings, motion detection, person detection, snapshots, RTSP streams, floodlights, sensors, chimes, arming/disarming the alarm, or any UniFi Protect task.
Install this agent skill to your Project
npx add-skill https://github.com/sirkirby/unifi-mcp/tree/main/plugins/unifi-protect/skills/unifi-protect
SKILL.md
UniFi Protect MCP Server
You have access to a UniFi Protect MCP server that lets you query and manage a UniFi Protect NVR. It provides 38 tools covering cameras, smart detections, recordings, snapshots, lights, sensors, chimes, and the Alarm Manager (arm/disarm).
Tool Discovery
The server uses lazy loading by default — only meta-tools are registered initially:
| Meta-Tool | Purpose |
|---|---|
protect_tool_index |
List all 38 tools with full parameter schemas |
protect_execute |
Call any tool by name (essential in lazy mode) |
protect_batch |
Run multiple tools in parallel |
protect_batch_status |
Check async batch job status |
Workflow: Call protect_tool_index to find the right tool, then protect_execute to call it. Use protect_batch for multiple independent queries.
Safety Model
All mutations are disabled by default because Protect controls physical security hardware.
Read operations — always available. Listing cameras, events, snapshots, sensor readings — all work without permissions.
Mutations require explicit opt-in via env vars:
UNIFI_POLICY_PROTECT_CAMERAS_UPDATE=true— camera settings, recording toggle, PTZ, rebootUNIFI_POLICY_PROTECT_LIGHTS_UPDATE=true— light brightness, PIR sensitivityUNIFI_POLICY_PROTECT_CHIMES_UPDATE=true— chime volume, triggerUNIFI_POLICY_PROTECT_ALARM_UPDATE=true— arm/disarm the Alarm Manager (Protect 6.1+)
Confirmation flow — every mutation uses preview-then-confirm:
- Default call → returns preview of what would change
- Call with
confirm=true→ executes the mutation
Always preview first and show the user before confirming.
Response Format
All tools return: {"success": true, "data": ...}, {"success": false, "error": "..."}, or {"success": true, "requires_confirmation": true, "preview": ...}. Always check success first.
Key Capabilities
- Snapshots:
protect_get_snapshotwithinclude_image=truereturns base64 JPEG inline - RTSP streams:
protect_get_camera_streamsgives stream URLs for video player integration - Smart detections:
protect_list_smart_detectionsfilters by type (person, vehicle, animal, package, face, licensePlate). These are the highest-signal events — prioritize over raw motion. - Event camera names: All event responses include
camera_namealongsidecamera_id— no need to callprotect_list_camerasseparately to resolve names. - Real-time events:
protect_recent_eventsreads from websocket buffer instantly (no API call). Buffer holds ~100 events with 5-minute TTL. Useprotect_list_eventsfor historical queries. - Video export:
protect_export_clipreturns metadata (not video data — too large for MCP). Max 2 hours, supports timelapse (fps: 4=60x, 8=120x, 20=300x) - PTZ: Only zoom works via API. For pan/tilt, use
protect_ptz_presetwith saved positions
Efficiency Tips
- Use
protect_batchfor parallel queries — biggest performance win. Batch smart detections + events in one call. - Prefer
protect_list_smart_detectionsoverprotect_list_eventsfor security analysis — smart detections are pre-classified (person, vehicle, etc.) and higher signal than raw motion. protect_recent_eventsis fast but small — only a few minutes of buffered data. For anything beyond real-time monitoring, useprotect_list_eventswith time range filters.- Limit results — event queries default to 30 but can return large payloads. Use
limitparameter to keep responses focused. - Security digest — for comprehensive event summaries, use the
security-digestskill which handles batch calls, severity classification, and cross-product correlation.
Authentication
Username and password are required (local admin credentials, not Ubiquiti SSO). API key support exists but is experimental — limited to read-only operations and a subset of tools.
To configure, run /unifi-protect:setup or set env vars manually:
UNIFI_PROTECT_HOST=192.168.1.1
UNIFI_PROTECT_USERNAME=admin
UNIFI_PROTECT_PASSWORD=your-password
Other UniFi Servers
If the user also has networking or door access control, other UniFi MCP plugins are available:
unifi-network— network devices, clients, firewall, VPN, routingunifi-access— door locks, credentials, visitors, access policies
Cameras are network clients — if a camera appears offline, the Network server can help check connectivity via unifi_lookup_by_ip.
Tool Reference
For the complete list of all 38 tools organized by category with descriptions, tips, and common scenarios, read references/protect-tools.md.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
myco:implement-update-tool-fetch-merge-put
Use this skill whenever you are implementing or fixing an update_* tool in unifi-mcp. It covers the mandatory fetch-merge-put pattern, deep_merge semantics, V2 API response gotchas, the confirm double-fetch design, LLM UX requirements for dict params, and when flat params are appropriate instead. Applies even if the user only says "add an update tool for X" without specifying the implementation approach — the pattern is required for all update tools in this project.
myco:community-pr-review
Use this skill when reviewing or merging any community PR in unifi-mcp — even if the user just says "take a look at this PR" or "can we merge this." Covers the complete quality gate checklist (f-string logger ban, validator registry registration, doc site update ordering), the fork-edit model for trusted contributors, org-fork push limitations, the dual-subagent review pattern, and PR body standards. Apply this skill before approving any externally-authored PR, before running the merge command, and when auditing recently merged PRs for compliance.
unifi-access
How to manage UniFi Access door control — locks, credentials, visitors, access policies, and events. Use this skill when the user mentions UniFi Access, door locks, door access, building access, NFC cards, PIN codes, visitor passes, access policies, access schedules, door readers, or any UniFi Access task.
setup
Configure the UniFi Access MCP server — set controller host, credentials, and permissions
security-digest
Generate a security digest summarizing events across UniFi Protect cameras, Access door events, and Network firewall activity. Use when asked about what happened overnight, security summary, event digest, recent activity, or reviewing camera and access events.
setup
Configure the UniFi Protect MCP server — set NVR host, credentials, and permissions
Didn't find tool you were looking for?