This comes from Rhombus rather than a third party, so the key you hand it goes to the company that already holds the footage — a different risk calculation from giving a physical-security API key to an independent wrapper. It is explicitly a beta with a feedback programme running, so expect the tool surface to move. The key it takes is console-scoped, which means whatever your account can reach, the assistant can too.
The vendor's own server for the Rhombus API, published by Rhombus Systems as a beta. It puts the same capabilities the Rhombus web app has behind MCP tools: the camera fleet, door controllers and readers, IoT sensors for audio, environment, motion and entry, and the alarm monitoring layer with live agent verification.
- Access to the Rhombus API surface — the same capabilities available in the Rhombus web app
- Cameras across dome, fisheye, bullet and multisensor hardware
- Access control over door controllers, readers and intercoms, with mobile, card and fob credentials
- IoT sensors covering audio, environmental, motion, entry and multipurpose panic
- Alarm monitoring backed by live agent verification and dispatch
- A script for scaffolding a new tool if you want to extend the set
A Rhombus Console account and an API key generated under API Key Settings, supplied as `RHOMBUS_API_KEY`. Run it with `npx --yes --package rhombus-node-mcp mcp-server-rhombus` (package `rhombus-node-mcp`, version 0.1.56), from the `rhombussystems/mcp-server-rhombus` Docker image, or install it for Claude Desktop in one command through the Smithery CLI. It is published as a beta with a feedback form attached.
One command plus a key — npx --yes --package rhombus-node-mcp mcp-server-rhombus, then supply credentials