obsbot-mcp
Related Servers
Alternatives to obsbot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables control of OBSBOT Tiny-series cameras (gimbal, zoom, focus, AI tracking, snapshots) through MCP tools.MIT
- AlicenseBqualityDmaintenanceEnables PTZ camera control with gimbal positioning, snapshots, and AI visual analysis for OBSBOT and UVC cameras. Supports autonomous scanning patterns and integrates with vision-language models for real-time camera analysis.71MIT
- FlicenseNot gradedqualityCmaintenanceProvides visual recognition and PTZ camera control for DIY MOSS (ESP32) smart assistants, bridging cloud AI with local camera capabilities via WebSocket.-
- AlicenseNot gradedqualityAmaintenanceEnables typed, native control of OBS Studio—scene/source discovery and recording start/stop/pause/resume with status readbacks—through a secure loopback WebSocket interface.GPL 2.0
- AlicenseNot gradedqualityDmaintenanceEnables LLM-based AI agents to control SO-ARM100 and SO-101 robots through natural language commands and camera feedback. It supports various transport protocols and provides tools for both autonomous robotic movement and manual keyboard operation.83Apache 2.0
- FlicenseAqualityDmaintenanceControls Reachy Mini robot, enabling movement of head, body, and antennas, playing animations, capturing images, text-to-speech, and WebRTC streaming via natural language.19-
TDQS
Scored across 34 tools
Tools are mostly distinct by subsystem and action; descriptions clearly delineate near pairs such as obsbot_zoom_uvc vs obsbot_zoom_vendor and obsbot_preset_save vs obsbot_preset_update. A few related autofocus/AI-tracking and save/update tools still need careful reading, so there is minor ambiguity.
All names share the obsbot_ prefix and snake_case, and most follow a predictable domain_action pattern (preset_save, gimbal_move, image_adjust). The pattern is not perfectly uniform, with noun-only names like obsbot_devices and action-first names like obsbot_capture_snapshot or obsbot_wake, but it remains highly readable.
34 tools is a heavy surface, well beyond the typical 3-15 range, and a few pairs (zoom UVC/vendor, auto/manual image controls) could have been consolidated. That said, the tools map to distinct camera subsystems, so the count is defensible for a full device-control server.
The surface covers device discovery, gimbal control, zoom, AI tracking, focus, exposure, white balance, image adjustments, presets, and capture with full lifecycle operations. Minor gaps such as no relative gimbal move, no readback for several image-adjust controls, and no firmware/battery info prevent a perfect score.