Skip to main content
Glama
smaniktahla

blueiris-mcp

by smaniktahla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to blueiris-mcp

No user-submitted related servers found.

    Related Servers

    • reolink-mcp

      ed-dryha
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that allows Claude or any MCP client to see and control Reolink cameras on the local network. It provides snapshots, device state, AI detection, PTZ controls, and deterrence features without cloud dependency.
      18 PyPI
      2
      MIT

    • Axis MCP

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

    • hikvision-mcp

      cormac-rynne
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables safely inspecting and configuring Hikvision cameras via a local MCP server, with permission enforcement, read-only diagnostics, and supervised mutation flows.
      MIT

    • Hubitat MCP Server

      solaegis
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Hubitat Elevation hubs that controls devices via the Maker API, with optional gated access to undocumented admin routes, supporting device listing, command sending, virtual device and hub variable automation for Rule Machine, and hub management features.
      8
      MIT
    • BillingServ MCP by BillingServ

      BillingServ MCPofficial

      BillingServ
      A
      license
      A
      quality
      B
      maintenance
      This is an MCP server for the BillingServ API. Once it's set up, your AI assistant can look up customers, invoices, orders, packages, and reports straight from your BillingServ installation
      3
      68 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

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: list_cameras for status, get_snapshot for frame retrieval, list_clips and list_alerts for historical data, and ptz for camera control. There is no overlap in functionality.

    Naming Consistency4/5

    Most tools follow the verb_noun pattern with snake_case (list_cameras, get_snapshot, list_clips, list_alerts). The exception is 'ptz', which is a concise, recognizable command name but breaks the verb_noun pattern slightly.

    Tool Count5/5

    The server exposes 5 tools, which is well-scoped for its purpose of interacting with a Blue Iris server. Each tool addresses a distinct need without excessive or inadequate coverage.

    Completeness4/5

    The tool set covers the core surveillance workflows: camera listing, snapshot retrieval, clip listing, alert listing, and PTZ control. Minor gaps exist such as lack of timeline traversal or configuration changes, but the surface is solid for common use cases.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources