Skip to main content
Glama
Sign In
axis-cam-mcp

axis-cam-mcp

by jilavsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to axis-cam-mcp

No user-submitted related servers found.

    Related Servers

    • Axis MCP

      hemla-com
      A
      license
      A
      quality
      D
      maintenance
      MCP server for configuring Axis IP cameras via VAPIX, supporting device info, snapshots, image settings, overlays, network, PTZ, and system management.
      37
      12 npm
      1
      GPL 3.0

    • camera-mcp

      maxritter0714-sketch
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to list configured cameras, fetch current JPEG frames from video files, webcams, or RTSP/HTTP streams, run local YOLO object detection, and count objects inside named polygonal zones using normalized coordinates. Answers come back as compact JSON with timestamps and image age, so a model can respond to questions like "Is anyone there?" or "How many cars are parked?" while only requesting the actual image when needed.
      AGPL 3.0

    • Anava MCP Server

      AnavaAcap
      -
      license
      A
      quality
      Not graded
      maintenance
      A bridge between AI assistants like Claude and Anava-enabled Axis cameras, enabling real-time image analysis, event monitoring, and camera management through natural language commands.
      4
      -

    • camera-mcp

      mpolinowski
      A
      license
      A
      quality
      B
      maintenance
      Enables controlling and monitoring INSTAR IP cameras over MQTT, with tools to set and query camera settings, wait for state changes, check connectivity, retrieve snapshots, and list capabilities.
      6
      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

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing configured cameras, grabbing a frame, retrieving device metadata, and querying supported capabilities. The potential similarity between camera_info and camera_capabilities is resolved by clear descriptions covering different aspects of the camera.

    Naming Consistency3/5

    Names are all lowercase snake_case and readable, but the convention is mixed: list_cameras and grab_frame use verb_noun while camera_info and camera_capabilities are noun phrases with no verb. This is not chaotic, but it lacks a single predictable pattern.

    Tool Count5/5

    Four tools is well-scoped for a camera-focused MCP: enumeration, metadata, capabilities, and frame capture. Each tool earns its place and there is no redundant or filler functionality.

    Completeness4/5

    The tool set covers the core read-only camera workflow: discover cameras, verify connectivity, check capabilities, and capture still frames. Minor gaps such as continuous video capture, camera configuration, or PTZ control are plausible extensions but do not seem essential to the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Resources