
Wraps the Radio Browser API to give Claude access to internet radio stations without authentication. You get three tools: search stations by name, list countries with station counts, and browse available genres ranked by popularity. Each station result includes streaming URL, location, tags, and vote count. Useful when you want Claude to find live audio streams, recommend stations by genre or geography, or build radio discovery features. Part of the broader Pipeworx gateway, so you can add it standalone or bundle it with 600+ other data sources. Free tier available, no API keys needed since Radio Browser itself requires no auth.
Radio MCP — wraps Radio Browser API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
search_stations | Search radio stations by name. Returns station name, URL, country, genres, and popularity vote count. Use when looking for a specific station or browsing by keyword. |
get_top_stations | Get trending radio stations ranked by popularity, optionally filtered by country (e.g., 'US', 'GB', 'DE'). Returns station URLs, genres, and vote counts. |
list_countries | Browse available countries with radio stations. Returns country names and station counts to help target your search geographically. |
list_tags | Discover radio genres and tags ranked by station count. Use to explore what categories are available before searching. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"radio": {
"url": "https://gateway.pipeworx.io/radio/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/radio/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Radio data" })
The gateway picks the right tool and fills the arguments automatically.
MIT