A
licenseA
qualityD
maintenanceA comprehensive MCP server for rekordbox database management with real-time database access, enabling track search, playlist operations, library analytics, and DJ history retrieval.
31
MIT
Rekordbox Smart MCP
Related Servers
Alternatives to Rekordbox Smart MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for Spotify playlist curation and management. 18 tools for song analysis, smart playlist creation, top tracks analysis, and automated recommendations.1MIT
- AlicenseAqualityDmaintenanceMCP server for rekordbox DJ database access. Provides read-only querying of tracks, playlists, and DJ session history from encrypted rekordbox SQLite databases using pyrekordbox.25104PythonMIT
- FlicenseNot gradedqualityBmaintenanceMCP server for DJs to scan music folders, validate and suggest metadata via MusicBrainz/iTunes/Spotify, and batch write metadata to audio files with confidence scoring.1-
- AlicenseBqualityBmaintenanceThe ultimate 66-tool Apple Music MCP server for macOS: playback, Spotify playlist importer, listening journal, Replay reports, smart DJ crossfades, and AirPlay.662MIT
- AlicenseAqualityDmaintenanceAn 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.3316 PyPI2MIT
TDQS
C2.9/5.0
Scored across 33 tools
Disambiguation2/5
Several tools overlap significantly: rekordbox_importXml, library_load, and rekordbox_sync's 'import' action all load Rekordbox XML files, while library_search, library_fuzzySearch, and search_keyCompatible all provide search functionality with unclear boundaries. This will likely cause an agent to select the wrong tool.
Naming Consistency2/5
Naming follows a mixed pattern: some tools use verb_noun (playlist_create, library_search), others use noun_verb (track_get, library_load), and camelCase appears inconsistently (buildSmart, keyCompatible, bpmCacheSet). The arbitrary prefixes (dj_, rekordbox_, library_, track_, setlist_) further break predictability.
Tool Count2/5
At 33 tools, the server is over-granular, exceeding the typical recommended range. Many tools could be consolidated (e.g., rekordbox_importXml and library_load are nearly identical), suggesting the count is bloated rather than well-scoped.
Completeness3/5
The server covers most core workflows: library loading and search, playlist CRUD, track updates, history analytics, and setlist suggestions. However, notable gaps exist—no track deletion, and the import/export paths are redundant and confusing, which may cause dead ends for agents.
Maintenance
ActivityInactive
ResponsivenessNo issues