Skip to main content
Glama
shermozle

lms-mcp

by shermozle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to lms-mcp

No user-submitted related servers found.

    Related Servers

    • Lyrion MCP Server

      edk4971
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to control a Lyrion Music Server (LMS/Squeezebox) for playback, search, library browsing, and player management.
      -

    • mcp-spotify

      obrien-matthew
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Spotify that enables playlist building and music discovery through 19 tools, allowing LLM agents to search tracks/artists/albums, manage playlists, control playback, and access personal listening data.
      20
      MIT

    • roon-mcp

      bestimmaa
      A
      license
      A
      quality
      C
      maintenance
      MCP server to control the Roon music player, enabling AI agents to search music, manage playback, and adjust volume across zones.
      9
      13 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 55 tools

    Disambiguation3/5

    Some overlapping actions exist, e.g., `play_pause` and `playlist_action` both control playback, and multiple `play_*` tools target different sources but with similar verbs. Tools like `get_current_playlist` and `get_playlists` are distinct but the naming could cause confusion. Overall, most tools have clear targets, but a few ambiguity points lower the score.

    Naming Consistency4/5

    Most tools follow a consistent `verb_noun` pattern (e.g., `add_favorite`, `clear_playlist`, `search_tracks`). However, there are minor deviations like `playlist_action` (noun_noun) and `play_pause` (verb_verb), and `jump_to_playlist_index` uses a preposition. These are infrequent, so the overall consistency is good.

    Tool Count2/5

    With 55 tools, the server is very large. While LMS is a complex domain, many tools are highly specialized (e.g., individual set commands for balance, bass, treble) and could be combined. The high count makes it harder for agents to navigate and select the right tool, exceeding the typical well-scoped range.

    Completeness5/5

    The tool set covers virtually all aspects of LMS: playback, playlist management, search, player settings, synchronization, library browsing, app integration, and favorites. There are no obvious dead ends or missing operations for a music server of this level.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources