A
licenseB
qualityC
maintenanceMCP server that provides LLM tools to interact with Lyrion Music Server (LMS), enabling player control, playback management, playlist operations, and music library search.
55
24 npm
MIT
roon-mcp
by bestimmaa
Related Servers
Alternatives to roon-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for Spotify that lets AI agents search music, control playback, and manage playlists via the Spotify Web API.1921 npmMIT
- AlicenseNot gradedqualityCmaintenanceA comprehensive MCP server that enables AI assistants to control music playback, manage users and access, configure providers, and administer a Music Assistant setup through natural language commands.MIT
- AlicenseAqualityBmaintenanceMCP server to control Spotify conversationally from Claude, Cursor, and other AI clients.11151 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Apple Music that lets AI assistants manage playlists, control playback, and browse the music library.96MIT
sonora-mcpofficial
FlicenseNot gradedqualityCmaintenanceMCP server that wraps the Multiroom Audio Hub v2 REST API, providing 24 tools to control multiroom audio systems. Enables AI assistants to manage inputs, outputs, groups, routes, playback, and master mute.-
TDQS
A4.5/5.0
Scored across 9 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: control_playback handles transport commands, play_now starts a single item, enqueue_and_play builds a queue, search_music finds candidates, get_tracks_for expands them, etc. No two tools overlap in functionality.
Naming Consistency4/5
Tool names follow a mostly consistent snake_case pattern with verbs leading (list_zones, set_volume, get_tracks_for). However, 'now_playing' and 'play_now' are verb-phrase based, and 'mute' is a single verb, introducing minor inconsistency.
Tool Count5/5
With 9 tools, the server is well-scoped for a Roon music control system. Each tool handles a essential aspect (search, playback, queue, volume, zone management) without being bloated or underpowered.
Completeness4/5
Core workflows are covered: search, browse, play, control, volume, and state. Minor gaps exist, such as no playlist management or fine-grained queue manipulation (e.g., insert, remove), but these are not critical for basic operation.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive