A
licenseNot graded
qualityB
maintenanceMCP 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.
0
MIT
radiobrowser-api-mcp
by maxim75
Related Servers
Alternatives to radiobrowser-api-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables controlling a Lyrion Music Server through MCP tools for playback control, library search, and queue management.124 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
- FlicenseAqualityCmaintenanceMCP server for KaboomKartell radio, enabling AI assistants to query live tracks, vote for songs, and access radio stats and schedule.15-
- FlicenseAqualityDmaintenanceExposes Spotify controls as MCP tools for playback, playlist management, and AI playlist generation; includes a web app and supports multi-user profiles.14-
- AlicenseNot gradedqualityBmaintenanceEnables searching and retrieving audiobooks, authors, and tracks from LibriVox through an MCP interface.189 npmMIT
TDQS
B3/5.0
Scored across 29 tools
Disambiguation2/5
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.
Naming Consistency3/5
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.
Tool Count2/5
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.
Completeness4/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues