Skip to main content
Glama
RhombusSystems

Rhombus MCP Server

Official
by RhombusSystems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Rhombus MCP Server

No user-submitted related servers found.

    Related Servers

    • Chirp Home Automation MCP Server by chirpwireless

      Chirp Home Automation MCPofficial

      chirpwireless
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI apps to securely connect to your Chirp home automation, letting you query sensors, control devices, manage automations, view alerts, and more through natural language.
      MIT

    • ring-vision-mcp

      SwaggyXO
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to interact with Ring cameras and doorbells through the official Amazon Vision API, supporting device listing, health status, event history, and live WebRTC streaming via natural language.
      7
      MIT

    • visioncore

      Denisijcu
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI agent to act as a security operations operator by providing tools to monitor camera feeds, analyze scenes, review situations and alarms, acknowledge or resolve alarms, make voice announcements, and consult audit trails and system status.
      -

    • home-assistant-mcp

      mattmaas
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read Home Assistant entity states, call any service, and optionally apply named scene presets from a catalog using plain-English descriptions.
      138 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, with detailed descriptions that differentiate similar ones like events-tool vs report-tool or multiple door-related tools. However, some potential overlap exists between camera-tool and update-tool for camera settings, and between get-entity-tool and entity-lookup-tool, but the descriptions mitigate confusion.

    Naming Consistency4/5

    Tool names consistently use snake_case and follow a <domain>-tool pattern (e.g., access-control-tool, alarm-monitoring-tool). A few names like create-camera-policy-tool deviate slightly from the verb-noun pattern, but overall naming is predictable.

    Tool Count3/5

    With 31 tools, the server is on the high side for a typical MCP server. While the domain (physical security) is broad enough to justify many tools, some tools could be consolidated (e.g., multiple door-related tools). The count feels slightly heavy but still manageable.

    Completeness3/5

    The tool surface covers a wide range of operations across various domains (access control, cameras, analytics, LPR, etc.) but has notable gaps. Missing user creation, alarm management beyond monitoring, and full CRUD for locations (only create and update). Some operations require workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources