Rhombus API MCP Server - Rhombus Developer Documentation

The Rhombus API MCP Server connects AI tools directly to your Rhombus security platform. Unlike the Documentation MCP (which searches docs), this server gives AI assistants the ability to take actions — list cameras, pull clips, manage doors, review alerts, and more — using your Rhombus API key.

Warning

This MCP server acts on your live Rhombus organization: tools that unlock doors, change lockdowns or reboot devices act on the real world. Give an assistant a key with a read-only role by default. If it must take actions, use a separate key whose role covers only those devices, and keep your MCP client's confirmation for tool calls turned on, so a person approves each action.

What you can do

The server provides 30+ tools organized by capability:

Cameras & Video

camera-tool — List cameras, get camera details, view status and health
clips-tool — Search and retrieve saved video clips (manual and policy-triggered)
video-walls-tool — Manage video wall configurations for multi-camera monitoring
reboot-cameras — Remotely reboot cameras
camera-uptime-tool — Check camera uptime and connectivity history

Access Control & Doors

access-control-tool — Manage access control systems, credentials, and users
door-tool — Lock, unlock, and monitor door status
door-schedule-exception-tool — Create and manage door schedule overrides
guest-management-tool — Manage guest access and visitor credentials

Security & Monitoring

alarm-monitoring-tool — Check monitoring status, manage threat cases
policy-alerts-tool — Review and dismiss policy-triggered alerts (motion, person detection, etc.)
events-tool — Query security events and activity logs
rules-tool — Manage automation rules and triggers

Analytics & Search

analytics-tool — Space utilization, traffic patterns, and real-time scene analysis
search-tool — Search across cameras, events, and entities
count-tool — People counting and occupancy data
faces-tool — Face recognition person lookup
lpr-tool — License plate recognition searches

Organization & Users

user-tool — Manage users and permissions
user-audit-tool — Review user activity audit trails
user-access-trail-tool — Track user access history
location-tool — Manage locations and site configuration
get-org-information — Retrieve organization details
report-tool — Generate and retrieve reports

Utilities

entity-lookup-tool — Look up any entity by UUID
get-entity-tool — Get detailed entity information
time-tool — Current time utilities
time-conversion-tool — Convert between time formats and timezones
update-tool — Update entity properties

Prerequisites

A Rhombus organization with API access enabled
An API key generated from the Rhombus Console, with the narrowest role the assistant needs (see Permissions)
Node.js 18+ (for npx) or Docker (for container-based setup)

Setup

Add the Rhombus MCP server with a single command:

bash

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

Set your API key as an environment variable:

bash

export RHOMBUS_API_KEY=YOUR_API_KEY

Verify by asking Claude Code:

"List all my Rhombus cameras"

Add to your claude_desktop_config.json:

json

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

Tip

On macOS, this file is located at ~/Library/Application Support/Claude/claude_desktop_config.json

Run via Docker for an isolated environment:

json

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

Add to your Cursor MCP settings (Cmd+Shift+P → "Open MCP settings"):

json

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

Restart Cursor after saving.

Install automatically via Smithery:

bash

npx -y @smithery/cli install @RhombusSystems/rhombus-node-mcp --client claude

Partner accounts

With a partner API key, the server can act in one of your client organizations. Set RHOMBUS_PARTNER_ORG to the client organization's UUID alongside RHOMBUS_API_KEY:

json

{
  "mcpServers": {
    "rhombus": {
      "command": "npx",
      "args": ["--yes", "--package", "rhombus-node-mcp", "mcp-server-rhombus"],
      "env": {
        "RHOMBUS_API_KEY": "YOUR_PARTNER_API_KEY",
        "RHOMBUS_PARTNER_ORG": "CLIENT_ORG_UUID"
      }
    }
  }
}

Over the HTTP transport, send the client organization's UUID in the x-auth-org header instead. List your client organizations and their UUIDs with getClientsV2.

Example workflows

Monitor your cameras

Ask your AI assistant:

"Show me the status of all my cameras. Are any offline?"

The assistant uses the camera-tool to list cameras and check connectivity status.

Review security alerts

"What policy alerts happened in the last 24 hours? Show me the most critical ones."

The assistant uses policy-alerts-tool to query recent alerts and events-tool for details.

Check door activity

"Which doors were held open or forced open today?"

The assistant uses door-tool to read door status and events.

Search for vehicles

"Has a red Toyota been seen in any camera in the last week?"

The assistant uses lpr-tool to search license plate recognition data across your cameras.

Generate a report

"Give me a summary of foot traffic at the front entrance over the past month."

The assistant uses analytics-tool and count-tool for occupancy and traffic data.

Running locally

To build and run from source:

Clone the repository

bash

git clone https://github.com/RhombusSystems/rhombus-node-mcp.git
cd rhombus-node-mcp

Install dependencies
bash
```
npm install
```
Build and run with Docker
bash
```
docker build -t mcp-server-rhombus .
```
Then update your MCP config to use the local image name mcp-server-rhombus instead of rhombussystems/mcp-server-rhombus.