Reolink MCP server

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.

<!-- mcp-name: io.github.ed-dryha/reolink-mcp -->

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 RMCPCONFIGFILE at a copy anywhere else on disk):

cameras:
  front_door:
    host: 192.168.1.44
    username: admin

Passwords never go in this file. Set one RMCPCAMERASPASSWORD environment variable per camera instead — must exactly match the camera's key in the YAML above (lowercase snakecase):

RMCP_CAMERAS__front_door__PASSWORD=<camera-password>

Concurrent-session limit: Reolink cameras allow only a limited number

of simultaneous sessions. reolink-mcp holds one reolink-aio session 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 mcp add reolink -- uvx reolink-mcp

Claude Desktop (claudedesktopconfig.json — macOS: ~/Library/Application Support/Claude/claudedesktopconfig.json, Windows: %APPDATA%\Claude\claudedesktopconfig.json):

{
  "mcpServers": {
    "reolink": {
      "command": "uvx",
      "args": ["reolink-mcp"],
      "env": {
        "RMCP_CAMERAS__front_door__PASSWORD": "<camera-password>"
      }
    }
  }
}

Any other MCP client (generic stdio):

{
  "command": "uvx",
  "args": ["reolink-mcp"]
}

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.

Shortened. The full README is on GitHub.