Skip to main content
Glama

Related Servers

Alternatives to obsbot-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables control of a USB-connected desk pet by setting facial state, playing timed face keyframes, speaking with synchronized mouth movement, and reading device status and button presses.
      4
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables an agent to aim, nudge, sweep, zoom and recentre a USB (UVC) pan/tilt/zoom camera, capture frames, and save, recall and compare named views. Every movement is treated as unconfirmed until the before-and-after pictures prove the view actually changed.
      17
      72 PyPI
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Let an AI agent drive up to 12 hobby servos on an open-hardware USB-C controller (Pololu Maestro compatible): moves, named poses, sequences, on-board scripts and rail current/voltage readout, with per-channel travel limits and overcurrent guardrails. Includes a --mock emulator, so it runs without the board.
      16
      46 PyPI
      1
      MIT

    TDQS

    B3.1/5.0

    Scored across 82 tools

    Disambiguation3/5

    The device-prefix split (obsbot_* for USB/Tiny 2 vs obsbot_tail2_* for the network Tail 2) does most of the disambiguation work, but within each family there are overlapping read tools and control paths. In particular, obsbot_tail2_status, obsbot_tail2_live_status, obsbot_tail2_info and obsbot_tail2_gimbal_position all return overlapping state, and the descriptions contradict each other about whether live pose is REST-readable. obsbot_zoom_uvc vs obsbot_zoom_vendor is another pair with nearly identical purpose and only subtle semantic differences.

    Naming Consistency3/5

    There is a recognizable device prefix convention (obsbot_* vs obsbot_tail2_*), which helps a lot, but the suffixes mix noun_verb, bare verbs, and noun stacks. Examples: obsbot_preset_save vs obsbot_tail2_preset_save is consistent, while obsbot_image_hdr vs obsbot_tail2_hdr, obsbot_image_exposure_manual vs obsbot_tail2_exposure, and obsbot_ai_track_speed vs obsbot_tail2_track_speed break the parallel naming. Some tools are bare verbs (wake, sleep, recenter, zoom) while others are resource_action (gimbal_position, preset_recall).

    Tool Count1/5

    82 tools is an extreme mismatch, well beyond the 50+ threshold, and many are near-duplicates across the two camera families plus overlapping status/discovery/zoom variants. Even for a dual-device hardware control server, this surface could be consolidated substantially (e.g., one status tool per device, one preset CRUD group, one image-controls tool per device). The count makes misselection and context bloat likely.

    Completeness4/5

    Coverage is unusually broad: both camera families get gimbal, zoom, focus, exposure, white balance, image adjust, presets, tracking, capture/record, sleep/wake, and status control, and the Tail 2 adds streaming, portrait rotation, hybrid zoom, logs, and gesture controls. Remaining gaps are modest — e.g., no Tail 2 album/file retrieval or recording download, and object tracking cannot be entered by coordinate because the bounding-box grammar is undecoded. These are workaroundable limitations rather than dead ends for core control.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data