Skip to main content
Glama
SwaggyXO

ring-vision-mcp

by SwaggyXO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to ring-vision-mcp

No user-submitted related servers found.

    Related Servers

    • ring-partner-mcp

      inslot2525-ctrl
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to read a user's Ring devices, doorbell presses, motion events and latest snapshots through the Ring Partner API, read-only over stdio or Streamable HTTP. It surfaces device kind, online state and end-to-end encryption status, handles pagination and pre-signed media URLs, and returns plain-language errors for missing media or unauthorized time windows.
      4
      MIT

    • Ring MCP Server

      jpcors
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables control of Ring home security devices, including doorbells, cameras, lights, and alarm systems, through MCP-compatible clients like Claude Desktop.
      4
      MIT
    • Rhombus MCP Server by RhombusSystems

      Rhombus MCP Serverofficial

      RhombusSystems
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to interact with Rhombus physical security systems, providing access to smart cameras, access control, IoT sensors, and alarm monitoring through the Rhombus API.
      31
      280 npm
      MIT

    • Amazon MCP Server

      drahmad89
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Amazon services through AI assistants, allowing users to search products, manage their cart, view order history, and place orders using natural language.
      12 npm
      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.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct concern: device discovery, status, capabilities, configurations, stream lifecycle, and event history. There is no meaningful overlap between tools, so an agent can reliably select the right one.

    Naming Consistency5/5

    All tools share a consistent ring_ prefix and follow a clear verb_noun structure such as list_devices, get_device_status, initiate_whep_stream. Naming conventions are uniform and predictable.

    Tool Count5/5

    Seven tools is well-scoped for a Ring-focused MCP server. Each tool addresses a distinct operational need without redundancy or bloat.

    Completeness4/5

    The surface covers device listing, status, capabilities, configurations, live streaming, and event history—the core Ring use cases. Minor gaps exist, such as the lack of configuration updates or recorded clip playback, but these do not break primary workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources