bi-mcp
Related Servers
Alternatives to bi-mcp
No user-submitted related servers found.
Related Servers
- -licenseAqualityNot gradedmaintenanceA 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-
- AlicenseNot gradedqualityDmaintenanceIntegrates Claude AI with Home Assistant to control smart home devices via natural language.119 npmMIT
- AlicenseBqualityBmaintenanceLets Claude Code see through and control local ONVIF/RTSP IP cameras entirely on your own network: snapshots with cropped region detail, baseline comparison and change detection, short video recordings, pan/tilt movement and preset management. It can also add, rename and remove cameras without hand-editing config, keeping credentials out of the conversation and each camera's media in its own folder.2192 PyPI3MIT
- FlicenseNot gradedqualityDmaintenanceConnects Claude to OpenNMS, allowing plain language interaction with alarms, nodes, events, asset records, categories, and service collection.1-
- FlicenseAqualityBmaintenanceEnables AI assistants to interact with Frigate NVR security camera systems, supporting camera management, event detection, snapshots, recordings, and system stats via natural language.714-
- AlicenseNot gradedqualityDmaintenanceConnects 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.21,328 npm79ISC
TDQS
Scored across 18 tools
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.
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.
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.
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.