Rhombus MCP Server

Rhombus MCP Server is an MCP server that integrates the Rhombus physical security and surveillance API with LLM clients like Claude Desktop. It connects directly to Rhombus commercial security infrastructure, including smart security cameras, access control door controllers, environmental IoT sensors, and alarm monitoring systems. Security engineers, facility managers, and enterprise operations teams use this server to query and manage physical security infrastructure through conversational AI interfaces. By exposing Rhombus endpoints through Model Context Protocol tools, it enables language models to inspect camera status, retrieve device telemetry, access surveillance insights, and verify facility incidents. Users can run the integration either via containerized Docker environments or directly using Node-based execution. It bridges cloud-managed physical security devices and modern agentic workflows, allowing security operations centers to automate routine monitoring tasks, review security sensor events programmatically, and diagnose device connectivity without switching between different enterprise management consoles.

Category: Monitoring & Observability

Tags: cctv, monitoring, security, surveillance

Visit Rhombus MCP Server

How to install and configure Rhombus MCP Server

1. Generate an API key in your Rhombus Console under API Management settings. 2. Install via Smithery automatically by running npx -y @smithery/cli install @RhombusSystems/rhombus-node-mcp --client claude. 3. Alternatively, manually configure Claude Desktop by opening claude_desktop_config.json. 4. Add the server using Docker: json { "mcpServers": { "rhombus": { "command": "docker", "args": ["run", "-i", "--rm", "-e", "RHOMBUS_API_KEY=YOUR_API_KEY_HERE", "rhombussystems/mcp-server-rhombus"], "env": { "RHOMBUS_API_KEY": "YOUR_API_KEY_HERE" } } } } 5. Or add it via NPX using package rhombus-node-mcp with command mcp-server-rhombus. 6. Restart Claude Desktop and verify the Rhombus tools appear in the interface.

What you can do with Rhombus MCP Server

• Interrogating camera feeds, connection states, and status reports directly through Claude Desktop conversations. * Querying enterprise access control points, door controllers, and entry sensor statuses across multiple managed facilities. * Retrieving operational alerts and environmental metric updates generated by Rhombus IoT sensors in real time. * Streamlining security incident triage by fetching surveillance device details and event context within security chat assistants. * Developing custom security orchestration tools using the included helper script to expose additional Rhombus API endpoints.

Key facts

• https://github.com/RhombusSystems/rhombus-node-mcp
• Monitoring & Observability, Security & Compliance
• cctv, monitoring, security, surveillance

Part of MCP Servers

How do I install Rhombus MCP Server?

You can install it automatically for Claude Desktop using Smithery by running the Smithery CLI install command for rhombus-node-mcp. Alternatively, you can add it manually to your claude_desktop_config.json file using either a Docker container or via NPX with your Rhombus API key set in the environment variables.

What can Rhombus MCP Server do?

Rhombus MCP Server connects AI assistants to the Rhombus API. It allows models like Claude to interact with physical security systems, including querying smart security cameras, monitoring IoT environmental and motion sensors, reading door access control data, and retrieving alerts from alarm monitoring services directly within your chat client.

Which MCP clients work with Rhombus MCP Server?

The server works with any standard Model Context Protocol client. The documentation explicitly details setup instructions for Claude Desktop via Docker, Smithery, or NPX, and the server can also be built and run locally in any Docker-compatible development environment.

Is Rhombus MCP Server open source?

Yes, Rhombus MCP Server is open source and distributed under the MIT License. The code is hosted on GitHub by Rhombus Systems, allowing developers to inspect, modify, test with Vitest, and extend the toolset using local build scripts.