Reachy Mini MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REACHY_HOST | No | Daemon host | localhost |
| REACHY_PORT | No | Daemon port | 8000 |
| REACHY_SSH_USER | No | SSH username for streaming commands | reachy |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| reachy_statusA | Get Reachy Mini daemon health status and robot connection info |
| reachy_get_stateA | Get full robot state including joint positions and sensor data |
| reachy_move_headB | Move the robot's head to a specific orientation. Pitch/roll limited to [-40, 40] degrees, yaw to [-180, 180] degrees. |
| reachy_move_antennasB | Move the robot's antennas to specified positions |
| reachy_go_to_zeroB | Move the robot to its zero/neutral position |
| reachy_wake_upB | Wake up the robot (execute wake up behavior) |
| reachy_go_to_sleepA | Put the robot to sleep (execute sleep behavior) |
| reachy_start_continuous_moveB | Start continuous sinusoidal movement on the robot |
| reachy_stop_continuous_moveA | Stop continuous movement on the robot |
| reachy_capture_imageA | Capture a single frame from the robot's camera |
| reachy_play_audioA | Play an audio recording through the robot's speaker |
| reachy_list_audioA | List all saved audio recordings on the robot |
| reachy_check_cameraA | Check if the robot's camera is working by capturing a test frame |
| reachy_check_microphoneA | Check if the robot's microphone is working by recording a short sample |
| reachy_get_motor_statusB | Get detailed motor status information |
| reachy_reconnectB | Try to reconnect to the robot daemon |
| reachy_start_webrtc_streamA | Start WebRTC video/audio streaming from the robot's camera and microphone. Returns the stream URL to connect to. |
| reachy_stop_webrtc_streamA | Stop the WebRTC video/audio stream on the robot |
| reachy_webrtc_stream_statusA | Check if WebRTC stream is currently running and get the stream URL |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
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.
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.
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.
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.