engine-dj-mcp
Related Servers
Alternatives to engine-dj-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to search and audit a Serato DJ library by BPM and Camelot key, browse crates, detect duplicates and missing files, and stage new crates for review before writing.648 npmMIT
- FlicenseNot gradedqualityAmaintenanceConnects 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.-
- AlicenseNot gradedqualityCmaintenanceEnables local AI assistants to control and explore the macOS Music app through 12 tools for playback, playlists, songs, albums, and metadata, with full privacy and no network access.Apache 2.0
- AlicenseAqualityBmaintenanceEnables MCP-aware AI clients to read, query, and modify a Lexicon DJ library through structured tool calls, including searching tracks, managing tags, and curating playlists or smartlists.13MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to directly access and manage your local Prompteka prompt library on macOS. It allows assistants to read, search, create, and organize prompts and folders by connecting directly to the app's SQLite database.9 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
TDQS
Scored across 9 tools
Each tool targets a distinct resource and action: index refresh, playlist tracks, search, track metadata, playlist tree, performance data, health audit, SQL escape hatch, and library listing. No two tools overlap in purpose, and descriptions make boundaries clear.
All tools follow a consistent snake_case verb_noun pattern: refresh_index, get_playlist_tracks, search_tracks, get_tracks, get_playlists, get_track_performance, audit_library, run_sql, list_libraries. Verbs are clear and uniform in style.
With 9 tools, the server is well-scoped for a DJ library management domain. It covers discovery, search, retrieval, playlist inspection, performance analysis, health auditing, index maintenance, and a SQL fallback—each tool earns its place without bloat.
The tool surface is complete for a read/analysis-oriented server: library listing, search, track and playlist retrieval, performance data decoding, health audits, index refresh, and an escape hatch (run_sql) for uncovered questions. No obvious operations are missing given the server's stated purpose.