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.
      92 npm
      MIT

    • Frigate MCP Server

      dedsxc
      F
      license
      A
      quality
      C
      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
      12
      -

    • 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,828 npm
      78
      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
      280 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/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target clearly distinct resources (snapshot vs alert image, alerts vs clips vs log, camera list vs camera config). The config surface is crowded — bi_get_camera_config, bi_get_camera_motion_config, bi_get_actionset, bi_get_reg, and bi_audit_actions all surface overlapping config data — but the descriptions explicitly steer between them (e.g. 'use this instead of bi_get_reg(key_path=...)' and the API-vs-.reg boundary). Crossover notes on alerts/clips/log further reduce misselection.

    Naming Consistency5/5

    Every tool uses the consistent bi_<verb>_<noun> pattern with clear verbs (get, list, audit, explain) and snake_case nouns throughout. The bi_ prefix is applied uniformly, and verb choice signals read semantics reliably.

    Tool Count4/5

    18 tools is at the upper edge but justified by a genuinely broad domain (cameras, alerts, clips, logs, config, PTZ, timeline, audit). Each tool maps to a distinct facet rather than being redundant padding, though the five-way config split could be trimmed.

    Completeness4/5

    The read/inspection surface is thorough: status, session, sysconfig, cameras, per-camera config, motion config, actions, reg, alerts, clips, log, timeline, images, and clip forensics cover the analyst workflow well. The main gap is the absence of any mutation operations (profile/schedule changes, PTZ moves, clip export), which the descriptions acknowledge as read-only by design.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources