A
licenseNot graded
qualityD
maintenanceEnables control of OBSBOT Tiny-series cameras (gimbal, zoom, focus, AI tracking, snapshots) through MCP tools.
MIT
obsbot-mcp
by lxman
Related Servers
Alternatives to obsbot-mcp
No user-submitted related servers found.
Related Servers
- 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 gradedqualityDmaintenanceProvides visual recognition and PTZ camera control for DIY MOSS (ESP32) smart assistants, bridging cloud AI with local camera capabilities via WebSocket.-
- AlicenseNot gradedqualityBmaintenanceEnables 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.85Apache 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
B3.2/5.0
Scored across 80 tools
Disambiguation2/5
The set includes two overlapping families (generic obsbot_* seemingly for Tiny 2 and obsbot_tail2_*) without a device qualifier in the generic names, so an agent must infer target hardware from descriptions. Within each family, numerous tracking, preset, and zoom tools share conceptual territory, increasing misselection risk despite detailed descriptions.
Naming Consistency3/5
All names use snake_case with the obsbot_/obsbot_tail2_ prefix, but the convention is mixed between verb_noun (e.g., obsbot_gimbal_move, obsbot_tail2_preset_list) and bare noun phrases (e.g., obsbot_tail2_audio, obsbot_tail2_wb, obsbot_tail2_info). The prefixing is consistent, but the lack of a predictable read/write action pattern makes names only moderately predictable.
Tool Count1/5
80 tools is far beyond the recommended 3-15 range and exceeds even the 25+ threshold for 'too many'. Although a large camera-control surface could justify many endpoints, this volume imposes extreme context load and selection difficulty.
Completeness5/5
The surface covers CRUD/lifecycle for presets, gimbal, zoom, focus, exposure, white balance, image adjust, AI tracking, capture, streaming, status, and device discovery for two camera families. Missing operations are minor (e.g., no Tiny 2 network scan, no firmware update), so agents can work around gaps.
Maintenance
ActivityActive
ResponsivenessUnresponsive