scrypted-mcp

An MCP server that exposes a Scrypted home-automation/NVR server's devices, cameras, and controls as tools an LLM can call.

Talks to Scrypted over its RPC client (@scrypted/client), so it works against any Scrypted server — cloud or self-hosted — not just a Docker deployment.

Tools

get_recording_active/set_recording_active wrap the documented VideoRecorderManagement interface (setRecordingActive) plus the NVR's per-camera recording:privacyMode setting — these two must agree for recording to actually start or stop. They only cover on/off; the richer "Always / Motion-Triggered / Off" mode and day/time schedule grid in the NVR web console isn't backed by any device-level RPC method or Settings key (confirmed by grepping the NVR plugin's compiled backend for record/schedule/rule/mode identifiers — none exist there), so it's likely driven by the console's own HTTP endpoint rather than the Scrypted SDK. Not wrapped here; use invoke_device_method if you reverse-engineer it.

Related MCP server: Crestron Home MCP Server

Configuration

Copy .env.example to .env and fill in:

• SCRYPTED_BASE_URL — your Scrypted server's URL

• SCRYPTED_USERNAME / SCRYPTED_PASSWORD — credentials for an account on that server

• SCRYPTED_INSECURE=1 — only if your server uses a self-signed cert you trust

• PORT — HTTP port to listen on (default 3000). With Docker Compose's network_mode: host (required for record_clip to reach Scrypted's internal stream proxy — see below), there's no port remapping, so set this to whatever port you actually want to expose.

Running locally

npm install
npm run dev

Running with Docker

docker-compose.yml uses network_mode: host — required for record_clip, which spawns ffmpeg against Scrypted's internal loopback stream proxy (127.0.0.1:<random port>, only reachable from within the host's own network namespace, not a bridged container network). Set PORT in .env to whatever port you want exposed, since host mode has no remapping.

docker compose up -d --build

Without host networking (e.g. running standalone via docker run -p), every other tool still works fine — only record_clip needs it.

Connecting a client

This server speaks MCP over streamable HTTP at POST /mcp. Point your MCP client at http://<host>:3000/mcp. A GET /health endpoint is available for basic uptime checks.

Security note

This server holds credentials for full control of your Scrypted devices (cameras, locks, switches). Do not expose it directly to the internet — run it on a trusted local network, behind a VPN, or in front of your own auth proxy.