UniFi Protect MCP

Overview Schema Source Related Servers Score Discussions Admin

protect_list_sensors

Read-only

List all UniFi Protect sensors and retrieve their status, battery, motion, leak, and environmental readings in one call.

Instructions

List all sensors managed by UniFi Protect. Returns array; each sensor includes: id, modelKey, name, mac, state, mountType, batteryStatus (percentage, isLow), stats (light, humidity, temperature), lightSettings, humiditySettings, temperatureSettings, isOpened, openStatusChangedAt, isMotionDetected, motionDetectedAt, motionSettings, glassBreakSettings, scheduleMode, armProfileIds, hasCustomSensitivityWhenArmed, alarmTriggeredAt, alarmSettings, leakDetectedAt, externalLeakDetectedAt, leakSettings, tamperingDetectedAt, wirelessConnectionState (7.1.83 docs).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Array of items returned by the list endpoint

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed22 schema fields changedv2.7.5Jun 21, 2026

addedOutput schema / properties / result / items / properties / alarmSettings
```
Added value: +{
+  "description": "Alarm settings (object: isEnabled)"
+}
```

addedOutput schema / properties / result / items / properties / alarmTriggeredAt

Added value: +{
+  "description": "Last alarm timestamp in epoch ms (number)"
+}

addedOutput schema / properties / result / items / properties / armProfileIds

Added value: +{
+  "description": "Arm profile IDs this sensor belongs to (array of strings)"
+}

addedOutput schema / properties / result / items / properties / batteryStatus

Added value: +{
+  "description": "Battery status (object: percentage, isLow)"
+}

addedOutput schema / properties / result / items / properties / externalLeakDetectedAt

Added value: +{
+  "description": "Last external-leak timestamp in epoch ms (number)"
+}

addedOutput schema / properties / result / items / properties / glassBreakSettings
```
Added value: +{
+  "description": "Glass-break detection settings (object)"
+}
```
addedOutput schema / properties / result / items / properties / hasCustomSensitivityWhenArmed
```
Added value: +{
+  "description": "Custom armed sensitivity enabled (boolean)"
+}
```
addedOutput schema / properties / result / items / properties / humiditySettings
```
Added value: +{
+  "description": "Humidity threshold settings (object)"
+}
```
addedOutput schema / properties / result / items / properties / isMotionDetected
```
Added value: +{
+  "description": "Motion currently detected (boolean)"
+}
```

addedOutput schema / properties / result / items / properties / isOpened

Added value: +{
+  "description": "Open/close contact state (boolean)"
+}

addedOutput schema / properties / result / items / properties / leakDetectedAt

Added value: +{
+  "description": "Last leak timestamp in epoch ms (number)"
+}

addedOutput schema / properties / result / items / properties / leakSettings
```
Added value: +{
+  "description": "Leak detection settings (object)"
+}
```
addedOutput schema / properties / result / items / properties / lightSettings
```
Added value: +{
+  "description": "Light threshold settings (object)"
+}
```

addedOutput schema / properties / result / items / properties / motionDetectedAt

Added value: +{
+  "description": "Last motion timestamp in epoch ms (number)"
+}

addedOutput schema / properties / result / items / properties / motionSettings
```
Added value: +{
+  "description": "Motion detection settings (object)"
+}
```

addedOutput schema / properties / result / items / properties / mountType

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Mount type, e.g. \"door\", \"leak\", \"garage\""
+}

addedOutput schema / properties / result / items / properties / openStatusChangedAt

Added value: +{
+  "description": "Open-status change timestamp in epoch ms (number)"
+}

addedOutput schema / properties / result / items / properties / scheduleMode

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Schedule mode: \"always\" | \"when_armed\""
+}

addedOutput schema / properties / result / items / properties / stats

Added value: +{
+  "description": "Environmental stats (object: light, humidity, temperature)"
+}

addedOutput schema / properties / result / items / properties / tamperingDetectedAt

Added value: +{
+  "description": "Last tampering timestamp in epoch ms (number)"
+}

addedOutput schema / properties / result / items / properties / temperatureSettings
```
Added value: +{
+  "description": "Temperature threshold settings (object)"
+}
```

addedOutput schema / properties / result / items / properties / wirelessConnectionState

Added value: +{
+  "description": "Wireless link state (object: signalState, batteryStatus, bridge)"
+}

First observedv2.7.4Jun 11, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true and destructiveHint=false, making the safety profile clear. The description adds value by detailing the return format (array with fields like id, modelKey, name, etc.), going beyond annotations. However, it does not mention potential limits or pagination, which are minor gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence followed by a detailed list of return fields. It is front-loaded with the primary purpose. The list is structured but slightly verbose; however, every element is relevant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters and an existing output schema, the description provides a thorough breakdown of returned fields. It lacks details on ordering, filtering, or authentication requirements, but these are minor given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters, with schema coverage at 100%. Following guidelines, a baseline of 4 is appropriate since the description adds no param-specific information but cannot improve on an empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List all sensors managed by UniFi Protect', using a specific verb and resource. It distinguishes itself from sibling tools like protect_get_sensor (single sensor) and other list tools for different entities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving all sensors but lacks explicit guidance on when to use this tool versus alternatives (e.g., protect_get_sensor for a single sensor, or other list tools). No when-not or exclusion criteria are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/owine/unifi-protect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server