New here? For a friendly installation walkthrough, see Installing RWAV Bridge.
MCP Host Config (copy/paste)
For VS Code / Roo Code (JSON):
{
"mcpServers": {
"rwav": {
"transport": "stdio",
"command": "rwav-bridge-mcp",
"env": {
"RWAV_DISCOVERY": "auto",
"RWAV_BASE": "auto",
"RWAV_TOOL_ALLOWLIST": "tools,history"
},
"alwaysAllow": [
"tools_now_playing_get",
"tools_play_by_key",
"tools_search_run",
"tools_album_play_now",
"tools_playlist_play_now",
"tools_track_play_now",
"tools_queue_head_get",
"tools_volume_adjust",
"tools_zones_list"
],
"disabled": false
}
}
}
Alternative (static config)
RWAV_DISCOVERY=static
RWAV_BASE=http://localhost:3002
More details and client tips: RWAV MCP Instructions
Windows / Linux (npm)
npm i -g @calibress/rwav-bridge-mcp
Windows (Scoop)
scoop bucket add calibress https://github.com/calibress/scoop-bucket
scoop install rwav-bridge-mcp
macOS (Homebrew)
brew install calibress/rwav/rwav-bridge-mcprwav-bridge-mcp --help→ should print “RWAV Bridge MCP v…”
Note: Recent Homebrew installer runs setup automatically. Only run rwav-bridge-mcp-setup if a GUI client can’t find the binary.
Enable the Bridge in Roon
- Install RWAV Bridge (macOS/Windows/Linux): https://rwav-bridge.co.uk
- In the Roon app: Settings → Extensions → enable “RWAV Bridge”.
That’s it. Your MCP client can now launch the server and call tools like play, pause, next, shuffle/repeat, browse/search, and more.
Why the setup step?
GUI apps don’t inherit your shell PATH. The setup pins the absolute command path so clients can launch reliably every time.
Absolute paths (for manual MCP configs)
- macOS (Apple Silicon):
/opt/homebrew/bin/rwav-bridge-mcp - macOS (Intel):
/usr/local/bin/rwav-bridge-mcp - Windows (npm global):
%APPDATA%\npm\rwav-bridge-mcp.cmd - Linux (npm global): output of
which rwav-bridge-mcp
Recommended env (auto-discovery)
RWAV_DISCOVERY=auto
RWAV_BASE=auto
RWAV_TOOL_ALLOWLIST=tools,history
