Skip to main content
Glama
kayacancode

Reachy Mini MCP

by kayacancode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Reachy Mini MCP

No user-submitted related servers found.

    Related Servers

    • Reachy Mini MCP Server

      agentculture
      A
      license
      Not graded
      quality
      C
      maintenance
      Control a Reachy Mini robot through natural language, with tools for head/antenna movement, gestures, emotions, camera, and command sequences.
      32
      MIT

    • Reachy Mini MCP Server

      PixelML
      F
      license
      Not graded
      quality
      F
      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
      -

    • Reachy Mini MCP

      jackccrawford
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables control of Pollen Robotics Reachy Mini robot through high-level emotional expressions and low-level motor commands, with support for vision, audio, and text-to-speech capabilities.
      28
      MIT

    • reachy-mini-mcp

      nolte
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Reachy Mini robot that exposes robot state and motion control to LLM frontends like Claude Desktop.
      MIT

    • Robot Navigation MCP Server

      827346462
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables robot navigation control and monitoring through natural language. Provides tools for robot positioning, navigation to coordinates, device status monitoring, task management, and emergency controls.
      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

    A3.7/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools target clearly distinct actions such as moving the head, capturing images, or checking status. Some overlap exists among reachy_status, reachy_get_state, and reachy_get_motor_status, and between reachy_check_camera and reachy_capture_image, but the descriptions mostly clarify their different purposes.

    Naming Consistency5/5

    All tools follow a consistent reachy_ prefix with verb_noun naming, such as move_head, capture_image, and stop_webrtc_stream. The pattern is uniform and predictable across the entire set.

    Tool Count4/5

    At 19 tools, the count is slightly above the ideal sweet spot but remains justifiable for a robot control server covering movement, sensors, media, and streaming. The tools are not redundant enough to warrant trimming, though a few could potentially be consolidated.

    Completeness4/5

    The tool set covers the main robot lifecycle: wake/sleep, status, movement, camera, microphone, audio playback, and WebRTC streaming. Minor gaps exist such as no explicit individual joint control or audio file upload capability, but these do not critically undermine the server's apparent purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources