
Reolink Mcp
io.github.ed-dryhaPublished by GitHub account ed-dryhav1.0.0Updated Oct 24, 2026
MCP server for Reolink cameras: snapshots, device state, AI detection, PTZ, and deterrence controls
Overview
Connects an assistant to Reolink cameras on the local network for live snapshots, device state, AI detection, PTZ and deterrence controls.
- What you can do
- List cameras and read device info, capabilities and current state
- Poll AI detection states (person, vehicle, pet) and the motion flag
- Capture a live snapshot as an image
- Sound or stop the siren and toggle the audio alarm
- Switch spotlight, IR lights and white LED, and set zoom
- List and move to PTZ presets, read position, configure PTZ guard
- When to use it
- Useful when you have Reolink cameras on your LAN and want to ask an assistant for a live view, check what a camera detects, or adjust lights, siren and PTZ without opening the vendor app or an NVR.
- Requirements
- Runs locally over stdio, typically via uvx from the PyPI package. Needs a Reolink camera reachable on the local network with its admin username and password. Camera hosts and usernames go in a YAML config file located by RMCP_CONFIG_FILE; each camera password is supplied through its own RMCP_CAMERAS PASSWORD environment variable.
Installation
In SourceWeft
- Open Reolink Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
reolink-mcp
An open-source MCP (Model Context Protocol) server for Reolink cameras: lets Claude — or any MCP client — see and control Reolink cameras on the local network. Snapshots, device state, AI detection states, PTZ presets, and deterrence controls (spotlight, siren, IR/white LED). Local network only, no cloud.
Market gap (verified 2026-07-08): no dedicated Reolink MCP server exists
on GitHub, npm, or PyPI. Closest prior art requires a middleman:
dedsxc/mcp-frigate (needs Frigate NVR), homeassistant-mcp (needs Home
Assistant). This is a first-mover standalone niche.
A user with a Reolink camera adds reolink-mcp to their MCP client config,
asks "show me the front door camera," and gets a live snapshot — direct to
camera, no NVR or home-automation daemon in between.
Quickstart
Requires a Reolink camera reachable on the local network and its admin username/password.
1. Create your camera config
Copy config.example.yaml to
~/.config/reolink-mcp/config.yaml (or point RMCP_CONFIG_FILE at a copy
anywhere else on disk):
Passwords never go in this file. Set one RMCP_CAMERAS__<name>__PASSWORD
environment variable per camera instead — <name> must exactly match the
camera's key in the YAML above (lowercase snake_case):
Concurrent-session limit: Reolink cameras allow only a limited number of simultaneous sessions.
reolink-mcpholds onereolink-aiosession per configured camera for as long as the server runs — running it alongside another system that also holds sessions on the same cameras (an NVR, another MCP server, etc.) can exhaust that limit. See Camera compatibility & session limits below.
2. Add it to your MCP client
Claude Code:
Claude Desktop (claude_desktop_config.json — macOS:
~/Library/Application Support/Claude/claude_desktop_config.json, Windows:
%APPDATA%\Claude\claude_desktop_config.json):
Any other MCP client (generic stdio):
That's it — ask your MCP client to "show me the front door camera."
Tools
Built on reolink-aio and the
official MCP Python SDK.
Every tool carries readOnlyHint/destructiveHint annotations so MCP
clients can gate approvals — Observe tools are read-only, Control tools
mutate camera state, and set_siren is the only tool marked destructive.
Safety
RMCP_READ_ONLY=truestarts the server with all 10 control tools stripped at startup — they are simply never registered, not hidden. A one-line notice is printed to stderr; the client sees a clean, observe-only server with no control tools in its registry at all.set_sirendefaults to a ~5s burst when no duration is given, and refuses (never silently clamps) any request over its 60-second hard cap — a clear error asks for a shorter duration instead.- Capability gating: every control tool checks the target camera's actual capabilities before sending any command, and refuses cleanly (e.g. "camera 'front_door' has no siren") instead of letting a raw API error from an unsupported feature reach the client.
Camera compatibility & session limits
Validated live during development on:
PTZ tools (list_presets, ptz_move_to_preset, ptz_position,
ptz_guard) are mock-validated only — real PTZ hardware validation is
pending.
Concurrent-session limit: reolink-aio maintains one long-lived session
per camera for the lifetime of the server process. Reolink cameras cap the
number of simultaneous sessions a camera will accept; running reolink-mcp
alongside another system that independently holds sessions on the same
cameras (an NVR, Reolink's own app, a second automation stack) can hit that
cap. This project's own development setup runs against cameras shared with a
second, independent system and has been exercised under that exact
coexistence condition — if you see login/session errors, check what else
currently holds a session on the camera first.
License
MIT
Source: README.md at commit 9293a07
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts