Get ready to see Reachy Mini in a whole new light! Your favorite conversation robot is no longer limited to just local interactions. Thanks to an exciting integration with Hugging Face Spaces, Reachy Mini can now tap into a vast universe of remote tools, powered by **MCP (Model-Controller Protocol)**.
This means you can easily grant your robot new abilities, like checking the weather or searching the web, without ever having to modify its core application. Simply add a tool Space from the Hugging Face Hub, and Reachy Mini gains instant new capabilities. Best of all, these tools run remotely in their dedicated Space, meaning no new code is downloaded onto your local machine, keeping your setup clean and secure.
Expanding Reachy Mini’s Horizons with Remote Tools
When you interact with Reachy Mini, you’re experiencing more than just a voice; you’re engaging with a sophisticated system designed to react dynamically to your conversation. This includes everything from non-verbal cues and movements to accessing specific functions through what we call “tools.” Essentially, a tool is any capability the robot’s model can execute during a dialogue, whether it’s playing an emotion, moving its head, or looking through a camera.
Each tool is defined by a clear name and a concise description, which the robot’s AI model interprets to decide when and how to use it. Previously, most of these tools were **built-in and local**, shipping directly with the Reachy Mini app and primarily focused on controlling the robot’s physical body. While essential for expressive interaction, this local-only approach created limitations for adding broader, more diverse functionalities.
Imagine needing to integrate a web search or a real-time weather update. Requiring every such capability to be a local Python file added unnecessary complexity and friction to the development process. This is precisely where remote tools come into play, offering a seamless way to expand Reachy Mini’s intelligence far beyond its immediate hardware. Now, adding a new ability is as simple as running a command like: reachy-mini-conversation-app tool-spaces add pollen-robotics/reachy-mini-weather-tool
Understanding Reachy Mini’s Tool Ecosystem
At the heart of Reachy Mini’s adaptable toolset are **profiles**, which serve as gatekeepers, determining which tools are active and usable. Each profile is a folder containing crucial files like instructions.txt (the prompt) and tools.txt, which lists all enabled tools. If a tool isn’t listed in tools.txt, the model simply cannot access it, offering you granular control over your robot’s capabilities.
Now, alongside the original built-in tools and any custom local Python tools you might create, we have a powerful third category: **remote MCP tools**. These are hosted on platforms like Hugging Face Spaces, making them incredibly easy to publish, share, and update independently of the main Reachy Mini application. You can even combine multiple remote tools for complex interactions, allowing Reachy Mini to, for example, search the web and check the weather in a single conversation.
Managing these tool Spaces is straightforward with a set of intuitive commands:
- To install and enable a Space in your active profile:
reachy-mini-conversation-app tool-spaces add <owner/space-name> - To install without immediately enabling:
reachy-mini-conversation-app tool-spaces add <owner/space-name> --install-only - To view all installed Spaces:
reachy-mini-conversation-app tool-spaces list - To remove an installed Space:
reachy-mini-conversation-app tool-spaces remove <owner/space-name>
When a Space is installed, it receives a local alias and its remote tools are carefully namespaced to prevent conflicts. For instance, `pollen-robotics/reachy-mini-search-tool` might become `pollen_robotics_reachy_mini_search_tool__search_web`. This clever naming ensures that tools from different Spaces, or even multiple tools from the same Space, can coexist harmoniously within a single profile, all managed by your `tools.txt` file.
Crafting Intelligent Conversations with Prompts
While the technical plumbing gets tools into Reachy Mini, it’s the **prompts** that truly dictate how the model leverages them during a conversation. Stored in your profile’s `instructions.txt` file, these prompts guide the AI on when to call a tool, how to interpret its results, and how to formulate a coherent response. This is especially critical when dealing with complex queries that might involve multiple tools.
Consider a question like: “Should I bring a jacket in Bordeaux today, and is there anything major happening downtown tonight?” Without a well-crafted prompt, the model might serialise tool calls (weather first, then search, or vice-versa), leading to unnecessary latency and a less fluid interaction. An effective prompt, however, can encourage parallel execution of tools, allowing Reachy Mini to gather information simultaneously and merge it into a single, comprehensive answer.
The quality of your prompts directly impacts the robot’s responsiveness and the naturalness of its dialogue. Clear, concise instructions help Reachy Mini decide whether to prioritize weather, search, or even combine both, ensuring a more intelligent and satisfying user experience. It highlights that the design of prompts is just as crucial as the tools themselves in shaping Reachy Mini’s conversational abilities.
Publishing Your Own Reachy Mini Tools & What’s Next
The integration of remote tools marks a significant leap forward for Reachy Mini, enabling a flexible and expandable architecture. We now support installing public, **MCP-compatible Gradio Spaces**, allowing multiple Spaces to be active simultaneously with per-profile enablement. Key capabilities like backend-agnostic registration and the assurance that no arbitrary code is downloaded locally further enhance this robust system.
However, it’s important to note a few current limitations: private or authenticated Spaces are not yet supported, nor are non-Gradio Spaces or arbitrary raw MCP URLs. While prompts can encourage parallel tool calls, they don’t guarantee deterministic orchestration; for use cases requiring strict parallel logic, this would ideally be handled directly in code.
If you’re inspired to expand Reachy Mini’s capabilities, publishing your own tool Space is straightforward. Ensure your tool is a **public Gradio Space** that exposes the standard MCP endpoint and design your tools to be **stateless** for optimal network performance. To help others discover your innovation, remember to tag your Space with **`reachy-mini-tool`** and **`mcp`** on Hugging Face.
With built-in, local custom, and now remote MCP tools all sharing a unified registry, and profiles continuing to orchestrate their usage, Reachy Mini’s potential is truly limitless. We can’t wait to see the incredible tools and applications the community will build, transforming Reachy Mini into an even more versatile and intelligent companion!
Source: Hugging Face Blog
