Skip to main content
Glama
whoamiTM

bi-mcp

by whoamiTM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to bi-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      -

    • Home Assistant MCP

      aniketbhondave
      A
      license
      Not graded
      quality
      D
      maintenance
      Integrates Claude AI with Home Assistant to control smart home devices via natural language.
      80 npm
      MIT

    • 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
      -

    • Atlassian Jira MCP Server

      aashari
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants like Claude to Jira projects, enabling natural language queries and operations for issue management, project tracking, comments, and workflows through the Jira REST API.
      11,401 npm
      74
      ISC
    • 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
      17 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.9/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools target clearly distinct resources or workflows — alerts, clips, log, timeline, snapshots, config, and PTZ status are well separated. A few could be confused at first glance, particularly bi_get_actionset vs bi_audit_actions and bi_get_session vs bi_get_status vs bi_get_sysconfig, but the descriptions draw clear boundaries.

    Naming Consistency5/5

    All tools follow a consistent bi_<verb>_<object> pattern with snake_case throughout. get is used for single-item/state lookups, list is used for collections, and explain/audit are appropriately used for analytical tools, so the naming is predictable and coherent.

    Tool Count4/5

    Nineteen tools is slightly above the ideal 3-15 range, but the count is justified by the breadth of the Blue Iris domain: system health, per-camera config, alert/clip forensics, PTZ state, logs, and .reg inspection. It feels near the upper edge rather than bloated.

    Completeness2/5

    The read/investigation surface is deep, but there are no write or control tools at all — no PTZ movement, profile switching, camera trigger, or clip management — which makes the server one-directional. Additionally, bi_get_alert_tracks is documented as broken, creating a dead end for AI track workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources