Skip to main content
Glama
UsbServoController

UsbServoController

Official

Related Servers

Alternatives to UsbServoController

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Gives AI agents direct hands-on access to physical hardware and host OS resources over local stdio: serial monitoring with crash-dump detection, firmware compile/flash via arduino-cli, PlatformIO, ESP-IDF and esptool, direct GPIO/I2C/SPI over FTDI bridges, BLE GATT operations, webcam or microscope snapshots, logic analyzer captures, audio recording and test tones, GUI screenshots and hotkeys, and Android ADB commands. It also helps diagnose toolchain and serial-permission problems and identify or terminate processes that lock a port.
      33
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Local serial and USB hardware access for coding agents, with typed YAML protocol commands, checksum validation, audited writes, lossless captures, hardware-free replay, and MCP App visualizations. Runs locally over stdio; live hardware use requires a serial device connected to the same machine.
      18
      7
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets AI agents control ESP32-based OnlyClaws hardware (servo/robotic claw) over serial, exposing motion and device-control tools.
      7
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects embodied devices (like StackChan, Raspberry Pi, ESP32) to AI via MCP protocol, enabling motion control with zero API cost, no PC required, and fully self-hosted.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      87
      Apache 2.0

    TDQS

    B3.4/5.0

    Scored across 16 tools

    Disambiguation4/5

    Each tool targets a fairly distinct action: motion (move_servos, go_to_pose, play_sequence), lifecycle (upload/run/stop script), and hardware ops (read_analog, measure_current, set_protection). The only mild overlaps are disable_servos vs stop_all and board_status vs measure_current, but the descriptions clarify panic-stop vs selective release and status snapshot vs continuous sampling.

    Naming Consistency4/5

    Nearly everything follows a snake_case verb_noun pattern (move_servos, clear_faults, upload_script, release_port). The small deviations are noun-first status reads (board_status, script_status) which break the verb-first convention but are still readable and predictable.

    Tool Count4/5

    16 tools is slightly on the heavy side but justified: motion control, pose/sequence playback, analog sensing, current measurement, protection/fault handling, on-board scripting, and port management are all genuine subdomains. Nothing looks redundant enough to clearly cut.

    Completeness3/5

    The surface covers motion, playback, sensing, protection, and scripting well. However, board_status exposes channel names, modes, travel limits, and speed with no corresponding setter tools, so an agent cannot configure channels—a notable gap that likely forces reliance on the GUI.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues