Skip to main content
Glama
finnhyun12

genicam-mcp

by finnhyun12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to genicam-mcp

No user-submitted related servers found.

    Related Servers

    • dwf-mcp-server

      KenosInc
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables control of Digilent WaveForms instruments (oscilloscope, AWG, logic analyzer) over USB, supporting devices like Analog Discovery 2/3 and Digital Discovery.
      3
      MIT

    • 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

    • logic-analyzer-ai-mcp

      wegitor
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables remote control and automation of Saleae logic analyzers for capture, export, and protocol decoding.
      10
      -
    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

    A4.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: registration (add_producer), discovery (discover_cameras), connection (connect/disconnect), feature inspection (list_features, get_feature), feature modification (set_feature), and image capture (grab). No overlap.

    Naming Consistency5/5

    All tool names follow a consistent lowercase snake_case verb_noun pattern (e.g., add_producer, discover_cameras, set_feature). No mixing of conventions.

    Tool Count5/5

    8 tools is well-scoped for a camera control server. Each tool serves a necessary role without redundancy or bloat.

    Completeness4/5

    Covers the full lifecycle: producer registration, camera discovery, connection, feature configuration, image capture, and disconnection. Minor gap: no built-in support for continuous or burst capture, but single-frame grab and trigger control via set_feature suffice for basic use.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources