Skip to main content
Glama

Related Servers

Alternatives to spotify-discovery-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to turn music requests into traceable local DJ collections by scanning and indexing audio, planning tracklists, managing durable download jobs, and preparing hash-checked playlists, manifests, and experimental rekordbox exports for DJ app handoff.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server for bulk Spotify operations enabling batch playlist creation, library exports, and large-scale library management with confidence scoring and human-in-the-loop for uncertain matches.
      33
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to build and edit Spotify playlists from natural language descriptions.
      7
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables DJs to retrieve BPM, key/Camelot, energy, and other track metadata with provider provenance, score transitions, plan setlists, and control Spotify playlists and playback with staged, revalidated writes for safety.
      MIT
    • A
      license
      A
      quality
      C
      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
      31 PyPI
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    The tools map to explicit workflow steps, and the descriptions clearly separate similar stages such as discovery_begin vs. discovery_fill and discovery_review vs. discovery_status. Minor ambiguity remains because begin/fill and review/status are adjacent stages whose names alone do not convey their conditional usage.

    Naming Consistency4/5

    Most workflow tools share a discovery_ prefix and follow a verb_noun style, while verify_tracks, mark_recommended, and forget break the namespace. The deviations are still readable and clearly scoped as research or repair operations.

    Tool Count5/5

    Eight tools is well-matched to a structured discovery pipeline: each tool corresponds to a distinct run step, read-only status, or repair action. There is no obvious bloat or missing count-driven need.

    Completeness4/5

    The set covers the full lane lifecycle from starting a run through verification, review, finishing, and status, plus repair tools for history and learned sources. It lacks explicit abort/reset or lane-management tools, but lane configuration is intentionally handled via lanes.json, so gaps are minor.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data