Skip to main content
Glama
Sign In
mmalkus

bluesound-mcp

by mmalkus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to bluesound-mcp

No user-submitted related servers found.

    Related Servers

    • Roomcast

      samoturk
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables playing audio from public playlist or media URLs on Sonos, Google Cast, and DLNA speakers in a home LAN, selecting rooms by name. Provides a queue that can be inspected, reordered, skipped, and stopped through natural-language requests from any MCP client.
      MIT

    • sonos-ts-mcp

      Tommertom
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to control Sonos audio devices over a local network using UPnP/SOAP protocols, supporting playback, volume, queue management, zone grouping, and music library browsing.
      59
      41 npm
      15
      MIT

    • harmony-mcp

      sapn95
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables controlling a Logitech Harmony Hub over its local WebSocket API, including listing activities and devices, starting activities, powering off, and sending IR commands.
      49 npm
      MIT

    • Lyrion MCP Server

      edk4971
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to control a Lyrion Music Server (LMS/Squeezebox) for playback, search, library browsing, and player management.
      -
    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

    A3.5/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes. The only potential confusion is between list_players and discover_players, but their descriptions clearly differentiate config-based vs network-scan discovery.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., list_players, load_preset, set_shuffle). The naming is uniform and predictable.

    Tool Count4/5

    With 19 tools, the set is slightly larger than the typical 3-15 range but still reasonable for a music-control server covering discovery, playback, presets, browsing, searching, and grouping. No tools feel redundant.

    Completeness4/5

    The tool surface covers core operations: player discovery, playback control, preset management, music browsing/searching, and grouping. Missing queue management or detailed track info, but the essential functionality is present.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources