scrypted-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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
Tool | Description |
| List all devices with id, name, type, and supported interfaces |
| Full current state of one device by id or name |
| Take a still snapshot from a camera |
| Capture a short live video clip from a camera via ffmpeg, independent of NVR recordings |
| Get a direct rtsp:// URL for a camera's live stream (open in VLC, not a browser) |
| Turn a switch/plug/light on or off |
| Lock or unlock a device |
| Check whether a camera is actively recording to the NVR |
| Turn NVR recording on/off for a camera |
| List the mixin provider ids currently applied to a device |
| Apply a mixin provider to a device without disturbing its other mixins |
| Escape hatch to call any method on any device |
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: ScrapeGraph MCP Server
Configuration
Copy .env.example to .env and fill in:
SCRYPTED_BASE_URL— your Scrypted server's URLSCRYPTED_USERNAME/SCRYPTED_PASSWORD— credentials for an account on that serverSCRYPTED_INSECURE=1— only if your server uses a self-signed cert you trustPORT— HTTP port to listen on (default3000). With Docker Compose'snetwork_mode: host(required forrecord_clipto 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 devRunning 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 --buildWithout 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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Give the physical world an API: cameras become typed endpoints your agent can read and act on.
Control your Tesla from your AI assistant - climate, charging, access, and security.
Operate Linux, macOS and Windows from your LLM. Every action runs through an auditable allowlist.
Control your existing Philips lights, Sonos speakers, Roborock vacuums and other supported devices through Port OS cloud. Give ChatGPT, Claude and other MCP-compatible assistants access to the devices you connect. Turn off the living room lights, play music on your speakers, adjust the thermostat, run a vacuum in a room, check a camera snapshot or find a connected tracker. Available actions depend on your linked provider accounts and each device’s supported capabilities. Port OS runs in the cloud; no local server is required. You choose the account, device and capability permissions each assistant receives. Device operations require user OAuth; public tool discovery does not grant device access. Port OS is in alpha. Setup: https://portoperatingsystem.com/docs/getting-started/ Support: https://portoperatingsystem.com/contact/
Related MCP Servers
AlicenseAqualityDmaintenanceAllows AI agents to run, inspect, and create Scrapeer visual web-scraping flows, bridging human-designed browser automation with agent-driven execution.1553 npm1MIT- FlicenseNot gradedqualityAmaintenanceEnables language models to perform AI-powered web scraping, structured extraction, search, crawling, schema generation, and scheduled monitoring through an integrated web-scraping API.-
- FlicenseNot gradedqualityAmaintenanceEnables language models to scrape, extract structured data, search the web, run asynchronous multi-page crawls, and schedule monitoring jobs through the ScrapeGraph AI API. It also exposes schema generation, credit, and history tools, with remote HTTP or local stdio deployment options.-
- FlicenseNot gradedqualityAmaintenanceEnables language models to perform AI-powered web scraping, extraction, search, crawling, schema generation, and monitoring through the ScrapeGraph AI API.-