Reolink Mcp

io.github.ed-dryha由 GitHub 帳號 ed-dryha 發布v1.0.0更新於 Oct 24, 2026

MCP server for Reolink cameras: snapshots, device state, AI detection, PTZ, and deterrence controls

已驗證STDIO僅桌面位置與生活安全與監控

概覽

AI 產生的概覽

讓助理連接區域網路內的 Reolink 攝影機,取得即時快照、裝置狀態、AI 偵測資訊,並控制雲台與嚇阻功能。

可以做什麼
  • 列出攝影機,讀取裝置資訊、支援能力與目前狀態
  • 輪詢 AI 偵測狀態(人、車、寵物)及移動標記
  • 擷取即時快照並以影像回傳
  • 鳴響或停止警報器,開關音訊警報
  • 開關聚光燈、紅外線燈與白光燈,並調整變焦
  • 列出並呼叫雲台預設點、讀取雲台位置、設定雲台看守
適用情境
當你在區域網路上有 Reolink 攝影機,想讓助理查看即時畫面、了解攝影機偵測到什麼,或在不開啟原廠應用程式與 NVR 的情況下調整燈光、警報器與雲台時使用。
執行需求
以 stdio 方式在本機執行,通常透過 uvx 從 PyPI 套件啟動。需要區域網路上可連線的 Reolink 攝影機及其管理員帳號密碼。攝影機位址與帳號寫在由 RMCP_CONFIG_FILE 指定的 YAML 設定檔中,每台攝影機的密碼則透過各自的 RMCP_CAMERAS PASSWORD 環境變數提供。
安裝前請注意
伺服器會為每台攝影機維持一條長時間連線工作階段,若 NVR 或原廠應用程式同時連線,可能觸及攝影機的同時連線上限。控制類工具會改變攝影機狀態,其中 set_siren 標示為破壞性操作,會發出實際警報聲。攝影機密碼以環境變數傳入,請勿寫進共用的用戶端設定。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Reolink Mcp,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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):

yaml
cameras:  front_door:    host: 192.168.1.44    username: admin

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):

bash
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:

bash
claude mcp add reolink -- uvx reolink-mcp

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

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

Any other MCP client (generic stdio):

json
{  "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.

ToolTypePurposeDestructive
list_camerasObserveEnumerate every configured camera with live connection status, model, and hostNo
get_device_infoObserveModel, firmware, hardware details for a cameraNo
get_capabilitiesObserveWhat a camera supports — PTZ, siren, spotlight, IR/white LED, zoom, AI detection types — in neutral feature vocabularyNo
get_statesObserveCurrent device state: day/night mode, white LED/spotlight, IR lights, siren capability, and motionNo
get_recent_eventsObserveCurrent AI detection state (person/vehicle/pet plus any camera-reported extras) from an on-demand poll, plus the plain motion flagNo
get_snapshotObserveLive still image from a camera, returned as an MCP image content blockNo
set_sirenControlSound or stop a camera's siren — ~5s safe default, 60s hard cap, over-cap requests refused not clampedYes
set_audio_alarmControlEnable or disable a camera's siren/audio-alarm feature — needed when set_siren is accepted by the firmware but produces no soundNo
set_spotlightControlTurn a camera's spotlight on or offNo
set_ir_lightsControlSet a camera's IR lights to auto, on, or offNo
set_white_ledControlTurn a camera's white LED on or off, with optional brightnessNo
set_zoomControlZoom a camera to an absolute position (0-100) or a relative in/out stepNo
list_presetsControlList a camera's named PTZ presetsNo
ptz_move_to_presetControlMove a camera to a named (or numeric) PTZ presetNo
ptz_positionControlRead a camera's current pan/tilt/zoom position, naming the nearest saved preset when closeNo
ptz_guardControlConfigure a camera's PTZ guard point and auto-return (set/goto/enable/disable)No

Safety

  • RMCP_READ_ONLY=true starts 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_siren defaults 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:

CameraValidated capabilities
P437Siren, spotlight, zoom
P320IR lights

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

來源:README.md,提交 9293a07

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v1.0.0最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分