Skip to main content
Glama
danmartinez78

VectorClaw

by danmartinez78
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to VectorClaw

No user-submitted related servers found.

    Related Servers

    • Reachy Mini MCP Server

      PixelML
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language control of Reachy Mini robots for tasks like head movement, camera capture, and performing choreographed dances or emotions. It includes local, low-latency text-to-speech capabilities with synchronized head animations for lifelike interaction.
      21
      -

    • bodybridge

      alice-jin-dev
      A
      license
      Not graded
      quality
      A
      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

    • VEX AIM MCP

      dbbudd
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to drive and control a VEX AIM coding robot over Wi-Fi, using its camera, lights, screen, speaker and kicker to navigate, detect objects, and play soccer. Also serves a live browser control panel for driving, team setup, and running autonomous-then-driver matches, with simulators available for testing without hardware.
      40
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 24 tools

    Disambiguation2/5

    Several tools have effectively the same purpose: vector_look and vector_capture_image both capture a camera frame, vector_status and vector_charger_status both report battery/charging state, and vector_face_detection overlaps heavily with vector_list_visible_faces. An agent could easily select the wrong tool despite the descriptions.

    Naming Consistency4/5

    Most tools follow a vector_ + verb_noun pattern (drive, find_faces, capture_image), and the shared prefix makes the set feel unified. A few noun-style names like vector_pose, vector_status, vector_cube, and vector_face deviate slightly, but they are still predictable and readable.

    Tool Count3/5

    24 tools is at the heavy end for a single server, and redundant pairs inflate the count. However, the robot-control domain legitimately needs many operations for driving, sensors, vision, and display, so the scope is borderline rather than excessive.

    Completeness4/5

    The set covers core Vector workflows: movement, docking, camera, speech, animation, face/object detection, head/lift control, sensor status, and setup. Lacking explicit audio capture or a dedicated stop-speaking command are minor gaps that don't create dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources