Skip to main content
Glama
thefiredev-cloud

eufy-cam-mcp

by thefiredev-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to eufy-cam-mcp

No user-submitted related servers found.

    Related Servers

    • Frigate MCP Server

      dedsxc
      F
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to interact with Frigate NVR security camera systems, supporting camera management, event detection, snapshots, recordings, and system stats via natural language.
      7
      10
      -

    • elv2mcp

      AMPVIP
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query and interact with Extra Low Voltage security hardware such as Hikvision and Dahua cameras and NVRs through typed, read-only-by-default MCP tools for device info, channel enumeration, and JPEG snapshot capture. Translates proprietary ISAPI and CGI protocols into safe, auditable calls that any MCP client can use over stdio.
      MIT

    • Larnitech MCP

      mpopovych-thinkhome
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to connect to smart-home controllers to read device snapshots, watch live state changes, look up type-specific documentation and known vendor quirks, save and compare data snapshots, and perform guarded two-phase writes for lights, climate, blinds, sensors and meters. Writes stay disabled until explicitly enabled, are previewed and token-confirmed before execution, and report what actually landed on the device.
      42 PyPI
      1
      MIT

    • scrypted-mcp

      hooptiej
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to list, inspect, snapshot, and control Scrypted home-automation/NVR devices such as switches, locks, and cameras through natural language.
      34 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

    B3.3/5.0

    Scored across 6 tools

    Disambiguation4/5

    Tools mostly target distinct resources: list all cameras, get one camera status, snapshot live, get recordings overview, list motion clips, and extract a clip frame. However, snapshot_camera and clip_frame both return a JPEG file path, and camera_status partially overlaps list_cameras' ready state, so minor confusion is possible.

    Naming Consistency3/5

    All names use snake_case, but the patterns are mixed: verbs (list_cameras, snapshot_camera, clip_frame) alternate with noun phrases (camera_status, recordings_info, motion_clips). Still readable, but not a consistent verb_noun convention.

    Tool Count5/5

    Six tools is well within the ideal 3–15 range for a camera monitoring server, and each tool appears to serve a distinct purpose.

    Completeness4/5

    Core monitoring and frame-extraction workflows are covered, but there is no direct tool to retrieve or download a full motion clip (only frame extraction), and no camera control or configuration operations. These are minor gaps for the apparent monitoring-focused purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources