ring-partner-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_TOKEN | No | Bearer token required when running the Streamable HTTP server on a non-localhost host. Clients must send Authorization: Bearer <MCP_HTTP_TOKEN>. | |
| RING_CLIENT_ID | No | Ring client ID used with RING_REFRESH_TOKEN and RING_CLIENT_SECRET to auto-renew the access token. | |
| RING_ACCESS_TOKEN | No | A Ring access token from the Ring Developer Playground (valid 30 minutes). | |
| RING_CLIENT_SECRET | No | Ring client secret used with RING_REFRESH_TOKEN and RING_CLIENT_ID to auto-renew the access token. | |
| RING_REFRESH_TOKEN | No | Refresh token from Ring account linking, used to auto-renew access. Requires RING_CLIENT_ID and RING_CLIENT_SECRET. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ring_list_devicesA | List the Ring devices shared with this app, with kind (camera, contact_sensor, ...), online state and whether video is end-to-end encrypted. |
| ring_get_deviceA | Status, capabilities and configuration for one device (battery, motion zones, encryption, sensor state). |
| ring_get_event_historyA | Past events for a device, newest first: doorbell presses (ding), motion (with subtypes), and live views (on_demand). Only events after the user granted consent to the app are available. |
| ring_get_snapshotA | The most recent recorded image from a camera within the last N minutes, returned as a JPEG. Refuses cameras with end-to-end encryption. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tools are highly distinct, with clear separation between listing devices, retrieving static configuration, accessing historical events, and capturing current images. No tool overlaps with another's primary function.
The naming convention is perfectly consistent across all tools, following the pattern 'ring_action_resource'. This provides a clear and predictable pattern for agents to parse.
With four tools, the set is perfectly scoped for a monitoring and discovery purpose within the Ring ecosystem. Each tool provides essential, non-redundant functionality.
The set is complete for read-only operations (listing, getting data, history). However, it is noticeably incomplete as it lacks any write or mutation capabilities, such as updating device configurations or arming sensors.