Name: Rhombus MCP Server
Author: RhombusSystems

LABSCO SUMMARY

Vendor-published, which matters for a security system.

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.

What it is

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.

What you get

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

Requirements

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), or from the rhombussystems/mcp-server-rhombus Docker image. It is published as a beta with a feedback form attached.

Setup effort

One command plus a key — npx --yes --package rhombus-node-mcp mcp-server-rhombus, then supply credentials

See installation options

USE CASES

01

Asking about site activity without opening the console

Query the camera and sensor estate from the assistant you are already in.

02

Checking who has access to a door

Read the access-control configuration for controllers, readers and credentials.

03

Following up on an environmental or motion alert

Pull the sensor readings behind the alert and the related camera coverage.

04

Extending the tool set for your own workflows

Scaffold a new tool with the supplied script and build on the existing set.

BEFORE YOU INSTALL

What to know first

Requires

Node.js 18 or later with npx (npx route)
docker on PATH (Docker route only)
RHOMBUS_API_KEY in your environment

Where it runs

Both documented setups run the server on your machine.

INSTALLATION

Connect your client

Server setup

TERMINAL

npx --yes --package rhombus-node-mcp mcp-server-rhombus

MCP Clients

Claude Desktop — Docker

CLAUDE DESKTOP — DOCKER · JSON

{
  "mcpServers": {
    "rhombus": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "RHOMBUS_API_KEY=<YOUR_RHOMBUS_API_KEY>",
        "rhombussystems/mcp-server-rhombus"
      ],
      "env": {
        "RHOMBUS_API_KEY": "<YOUR_RHOMBUS_API_KEY>"
      }
    }
  }
}

Claude Desktop — npx

CLAUDE DESKTOP — NPX · JSON

{
  "mcpServers": {
    "rhombus": {
      "command": "npx",
      "args": [
        "--yes",
        "--package",
        "rhombus-node-mcp",
        "mcp-server-rhombus"
      ],
      "env": {
        "RHOMBUS_API_KEY": "<YOUR_RHOMBUS_API_KEY>"
      }
    }
  }
}

Rhombus MCP Server