Skip to main content
Glama
Galb-collab

rekordbox-mcp

by Galb-collab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to rekordbox-mcp

No user-submitted related servers found.

    Related Servers

    • rekordbox-mcp

      davehenke
      A
      license
      A
      quality
      D
      maintenance
      MCP server for rekordbox DJ database access. Provides read-only querying of tracks, playlists, and DJ session history from encrypted rekordbox SQLite databases using pyrekordbox.
      25
      119
      Python
      MIT

    • Tempo

      amarisaster
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for Spotify control and synchronized lyrics retrieval that enables playback management, queue navigation, and music search capabilities. It also features perception tools for real-time track analysis, including BPM, key detection, and timestamped lyrics.
      120 npm
      3
      Apache 2.0

    • beatport-mcp-server

      ivo-toby
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides access to the Beatport API for music discovery and data retrieval, enabling users to search for tracks, artists, labels, releases, and charts through natural language.
      4
      MIT

    • PostgreSQL MCP Server

      versatilecoder
      F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server that enables database operations, schema management, and statistics via natural language through SQL queries and resources.
      19 npm
      -
    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 31 tools

    Disambiguation4/5

    Most tools target distinct resource-action pairs, but there is some overlap between general search_tracks and specialized filters like get_tracks_by_key or search_tracks_by_filename. Single vs batch variants are clearly distinguished by singular/plural naming.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern (get_, search_, create_, delete_, add_, remove_, import_, etc.). Singular and plural forms clearly differentiate single-item and batch operations.

    Tool Count2/5

    With 31 tools, the server exceeds the typical 3-15 range and even the 25-tool threshold. While the scope covers tracks, playlists, history, and maintenance, the sheer number may be overwhelming for agents.

    Completeness3/5

    Core track and playlist workflows are covered (import, search, create, add/remove), but there are notable gaps: no update track metadata, no rename playlist, and no general delete track (only broken tracks). History session coverage is thorough.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources