Reachy Mini Sonos Voice Control
by cpoissonco.huggingface.cpoisson/reachy-mini-sonos-voice-tool
Reachy Mini controls Sonos by saying Hey Sonos.
- Remote endpoint
- 1 tool
Uptime
Checked · every day
0%from 4 days of checks
Up without downtime on 0 of 4 days with data; down 4915 minutes in all, the longest 1440 minutes on 1 November.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
How far each check got
- Reached the address 100%
- Completed the handshake 0.0%
- Listed its tools 0.0%
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 3 Nov (today) | Down 1142 minutes | 1 | – |
| 2 Nov | Down 1440 minutes | 1of 1 | – |
| 1 Nov | Down 1440 minutes | 1of 1 | – |
| 31 Oct | Down 893 minutes | 8 | – |
A failure counts as down time only when a second check five minutes later fails too. How we check
Connect to the publisher's own endpoint
Paste into Settings › Connectors › Add custom connector:
https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse Run in a terminal:
claude mcp add --transport sse reachy-mini-sonos-voice-tool https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to ~/.gemini/settings.json:
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
{
"mcpServers": {
"reachy-mini-sonos-voice-tool": {
"url": "https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse"
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"reachy-mini-sonos-voice-tool": {
"type": "sse",
"url": "https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"reachy-mini-sonos-voice-tool": {
"url": "https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"reachy-mini-sonos-voice-tool": {
"type": "sse",
"url": "https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "reachy-mini-sonos-voice-tool"
type: sse
url: "https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse" Add to ~/.config/goose/config.yaml:
extensions:
"reachy-mini-sonos-voice-tool":
type: streamable_http
name: "reachy-mini-sonos-voice-tool"
enabled: true
uri: "https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse"
headers: {}
env_keys: []
envs: {}
timeout: 300 This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Run in a terminal:
codex mcp add reachy-mini-sonos-voice-tool --url https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"reachy-mini-sonos-voice-tool": {
"url": "https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"reachy-mini-sonos-voice-tool": {
"url": "https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"reachy-mini-sonos-voice-tool": {
"url": "https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse"
}
}
} For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server Reachy Mini Sonos Voice Control (`co.huggingface.cpoisson/reachy-mini-sonos-voice-tool`)
Its page: https://plug.directory/servers/co.huggingface.cpoisson/reachy-mini-sonos-voice-tool
It runs on the publisher's servers; the client connects to its URL.
Use the section for the person's client.
## Claude Desktop
Paste into Settings › Connectors › Add custom connector:
```text
https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse
```
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport sse reachy-mini-sonos-voice-tool https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse
```
## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA
Merge into the place for the person's client:
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
```json
{
"mcpServers": {
"reachy-mini-sonos-voice-tool": {
"url": "https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse"
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"reachy-mini-sonos-voice-tool": {
"type": "sse",
"url": "https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Zed
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Cline, AnythingLLM, Augment Code
Merge into the place for the person's client:
- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)
```json
{
"mcpServers": {
"reachy-mini-sonos-voice-tool": {
"type": "sse",
"url": "https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Continue
Merge into ~/.continue/config.yaml:
```yaml
mcpServers:
- name: "reachy-mini-sonos-voice-tool"
type: sse
url: "https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse"
```
## Goose
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Codex
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Agenvoy
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Amp
Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
```json
{
"amp.mcpServers": {
"reachy-mini-sonos-voice-tool": {
"url": "https://cpoisson-reachy-mini-sonos-voice-tool.hf.space/gradio_api/mcp/sse"
}
}
}
```
Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.
Tools 1
reachy_mini_sonos_voice_tool_sonos_voice_commandControl a Sonos system by voice: returns a 'Hey Sonos, ...' sentence that you must then say out loud, word for word, so a Sonos speaker with a microphone in the room hears it. Call this whenever the user asks to play music, pause, skip, change the volume, or asks what's playing on Sonos. Pick the obvious action and go; do not ask which service. Use 'custom' with the request in 'value' for anything else Sonos Voice Control can do. Pass the language Sonos Voice Control is set to ('en' or 'fr'); if you don't know it, leave it empty for the default. Speak the returned 'say' text and nothing else, then stay quiet while the speaker answers: that voice is Sonos, not the user.
From Hugging Face Spaces. Report a problem