radiobrowser-api-mcp
Related Servers
Alternatives to radiobrowser-api-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients such as Claude, Cursor, and VS Code Copilot to search more than 50,000 internet radio stations by name, genre, country, or language and retrieve their direct stream URLs. It also surfaces the most popular and trending stations along with country and genre listings, with no API key or account required.51MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants and autonomous agents to discover, search, and stream internet radio stations worldwide through Radio Browser, with browsing by country, language, genre, or popularity and playback control via MCP.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server that wraps the Radio Browser API to search radio stations, list countries, and discover genres. Enables AI agents to find and browse radio stations without authentication.18 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to search the Radio Browser directory for live internet radio stations and return working stream URLs, supporting queries by country, genre, popularity, or specific station.MIT
- AlicenseAqualityCmaintenanceEnables controlling a Lyrion Music Server through MCP tools for playback control, library search, and queue management.129 npmMIT
- AlicenseAqualityDmaintenanceMCP server that enables natural language control of internet radio from Claude Code, with access to 30,000+ global stations, auto-playback via mpv, and a real-time status line with audio spectrum visualization.7MIT
TDQS
Scored across 29 tools
Several tools have unclear boundaries: search_radio_stations and find_stations_by_name both search by station name, and advanced_station_search also accepts name plus many other filters. The large family of find_stations_by_* endpoints is largely subsumed by advanced_station_search, creating avoidable overlap.
Most tools follow readable snake_case verb_noun patterns such as list_*, get_*, and find_stations_by_*. However, search_radio_stations breaks the find_stations_by_name convention, advanced_station_search is not verb-led, and get_now_playing uses a different structure, so consistency is only moderate.
29 tools is above the 25+ threshold and makes the server feel heavy. While each endpoint may map to a real API operation, the redundancy between search tools and the large number of near-identical find_stations_by_* tools could be reduced.
The surface covers the major workflows: searching/listening to stations, getting now-playing info, voting and click tracking, adding stations, and browsing directory statistics and metadata. It lacks update/delete station operations, but those are less central and likely require credentials or admin privileges.