Skip to main content
Glama
TheDavidKoen

deadwax

by TheDavidKoen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to deadwax

No user-submitted related servers found.

    Related Servers

    • Navidrome-MCP

      Blakeem
      A
      license
      B
      quality
      A
      maintenance
      Analyze listening patterns, create custom playlists, discover missing albums, validate radio streams, and provide personalized recommendations through natural language.
      2
      64 npm
      93
      AGPL 3.0

    • spotify-mcp

      seenws
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to build and edit Spotify playlists from natural language descriptions.
      7
      52 npm
      MIT

    • Luminous MCP Server

      esoltys
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects AI assistants to a local music library for full-text search and filtering of tracks, albums, artists, genres, composers, and lyrics, plus listening analytics and metadata hygiene audits. Also lets users generate and populate playlists and control playback (play, pause, seek, volume) in a running player instance.
      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

    A4.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: check_feasibility checks a brief before track selection, query_library searches local tracks, validate_playlist checks a proposed playlist, and enrich_artist retrieves external artist background. The descriptions explicitly distinguish the two check-style tools by workflow phase and data source.

    Naming Consistency5/5

    All four names follow a consistent snake_case verb_noun pattern: validate_playlist, enrich_artist, check_feasibility, query_library. The verbs are distinct and predictable for their actions.

    Tool Count5/5

    Four tools is well-scoped for a focused playlist-assistant server, with each tool covering a separate workflow stage. There is no redundant or filler tool.

    Completeness4/5

    The set covers feasibility checking, library search, playlist validation, and artist enrichment, which supports the core playlist-building workflow. Minor gaps remain around explicitly creating, saving, or exporting a playlist, but agents can work around this by presenting validated playlists.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources