CAMERAS & NVRS / HM-CV-019
HM-CV-019 · datasheet
Reolink CLI
Reolink's own command-line tool for its cameras, doorbells, NVRs and Home Hub, with a built-in MCP stdio server; LAN only, no cloud account
01 · What it does
- Discover cameras on the LAN, ping, log in and read model, firmware and capabilities
- Pan, tilt and zoom, and go to, set or delete PTZ presets
- Read and set IR, spotlight and status LED, volume, mute and the siren
- Take a JPEG snapshot or save a short preview clip
- Read and change motion and AI detection, encoder and OSD settings, and query events, storage and recordings
02 · Install
$ curl -fsSL https://raw.githubusercontent.com/reolink/reolink-cli/main/install.sh | sh
$ reolink-cli config init
$ reolink-cli device add porch --host 192.0.2.10:9000 --user admin --password-stdin
$ reolink-cli gateway start --addr 127.0.0.1:9000- Published by Reolink. The CLI binaries are under a proprietary royalty-free EULA and their source is not in the repo; the skill, plugin manifests and installers are Apache 2.0
- The gateway must be running for the MCP server to work. Replace 192.0.2.10 with your camera's LAN address; the password is read from stdin
- Claude Code: /plugin marketplace add reolink/reolink-cli, then /plugin install reolink-cli@reolink-cli (install the CLI first)
- Features differ by model; the README says to check reolink-cli --camera <alias> capabilities. Battery cameras paired to a Home Hub are reached through the hub
- The README's config is the bare mcpServers block; it is wrapped in braces here
03 · Client config (from README)
{
"mcpServers": {
"reolink-cli": {
"command": "reolink-cli",
"args": ["mcp-server"],
"env": { "REOLINK_GATEWAY_ADDR": "127.0.0.1:9000" }
}
}
}
Install steps taken from the project README (its recommended path first). Placeholders are the maintainer's. Not bench-tested by HardwareMCP yet.
Weekly bulletin
New hardware MCP servers, notable releases and setup notes. One email, Mondays.