ring-vision-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Port for the HTTP SSE server (default: 3001). | 3001 |
| MCP_TRANSPORT | No | Set to "http" to start the HTTP SSE transport instead of stdio. | |
| RING_API_BASE | No | Amazon Vision API base URL. Defaults to https://api.amazonvision.com. | https://api.amazonvision.com |
| RING_CLIENT_ID | No | OAuth 2.0 Client ID (paired with RING_CLIENT_SECRET). | |
| RING_MOCK_MODE | No | Set to "true" to run offline with simulated devices and events. | |
| RING_TOKEN_URL | No | OAuth token endpoint. Defaults to https://api.amazonvision.com/oauth/token. | https://api.amazonvision.com/oauth/token |
| RING_ACCESS_TOKEN | No | Direct developer access token from the Ring Developer Playground. | |
| RING_CLIENT_SECRET | No | OAuth 2.0 Client Secret. | |
| RING_EXTENDED_TOOLS | No | Set to "true" to register extended diagnostic tools. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ring_list_devicesA | List all connected Ring cameras and doorbells with online status and hardware capabilities. |
| ring_get_device_statusA | Retrieve real-time battery percentage, Wi-Fi RSSI signal strength, and firmware version for a Ring device by ID or name. |
| ring_get_device_capabilitiesA | Inspect hardware capabilities for a Ring device (supported video codecs, resolutions, two-way audio, color night vision). |
| ring_get_device_configurationsA | Retrieve motion zones, privacy zones, and camera alert settings for a Ring device by ID or name. |
| ring_initiate_whep_streamC | Start a live WebRTC WHEP video streaming session with a Ring camera by ID or name and exchanging a client SDP offer. |
| ring_terminate_whep_streamA | Cleanly terminate an active WebRTC WHEP live streaming session using its session control URL. |
| ring_query_event_historyA | Retrieve recorded historical events (motion alerts, doorbell presses, live views). Can target a specific device ID or name, or aggregate recent events across all account devices. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ring-devices | Catalog of all Ring cameras and doorbells registered to the account |
| ring-recent-events | Real-time buffer of incoming Ring webhook vision events (motion alerts, person detections) |
TDQS
Scored across 7 tools
Each tool targets a distinct concern: device discovery, status, capabilities, configurations, stream lifecycle, and event history. There is no meaningful overlap between tools, so an agent can reliably select the right one.
All tools share a consistent ring_ prefix and follow a clear verb_noun structure such as list_devices, get_device_status, initiate_whep_stream. Naming conventions are uniform and predictable.
Seven tools is well-scoped for a Ring-focused MCP server. Each tool addresses a distinct operational need without redundancy or bloat.
The surface covers device listing, status, capabilities, configurations, live streaming, and event history—the core Ring use cases. Minor gaps exist, such as the lack of configuration updates or recorded clip playback, but these do not break primary workflows.