Skip to main content
Glama
thejens

Lyngdorf MCP Server

by thejens
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Lyngdorf MCP Server

No user-submitted related servers found.

    Related Servers

    • sonora-mcp by Sonora-Multiroom

      sonora-mcpofficial

      Sonora-Multiroom
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP 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.
      -

    • lyrion-mcp

      SimoneB79
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables an AI agent to inspect and control Lyrion Music Server (Logitech Media Server) players via the LMS JSON-RPC API, including playback, volume, playlists, favorites, radio, and library search/browse.
      MIT

    • wing-mcp-server

      bawaaaaah
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables control of a Behringer WING digital mixing console through MCP clients, exposing 116 typed tools for mixing, processing, automation, presets, scenes, and other console features, along with a web dashboard.
      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 43 tools

    Disambiguation4/5

    Most tools have distinct purposes, but some pairs like 'play' and 'pause' (both toggle playback) or 'powerOn'/'powerOff'/'togglePower' could cause confusion due to overlapping functionality. The majority, however, target specific resources and actions clearly.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern throughout, with clear prefixes like 'get', 'set', 'list', and action verbs. All use camelCase uniformly, making them predictable and easy to parse.

    Tool Count2/5

    With 43 tools, the set feels excessive for controlling audio devices. Many tools could be consolidated (e.g., separate get/set for each audio parameter) without losing functionality, leading to a bloated interface that may overwhelm agents.

    Completeness5/5

    The tool set comprehensively covers the domain of Lyngdorf audio device control, including discovery, status retrieval, configuration (balance, bass, treble, etc.), playback management, and power operations. No obvious gaps exist for typical use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources