Ask Claude, or any AI assistant, about your Engine DJ library: find tracks by BPM, key, genre or your own comments, check the collection for duplicates, missing files and tracks with no cues, read…
engine-dj-mcp is an MCP project maintained in the venut-technologies/engine-dj-mcp repository. The maintainer describes its purpose as “Ask Claude, or any AI assistant, about your Engine DJ library: find tracks by BPM, key, genre or your own comments, check the collection for…”. Read the project documentation for the complete scope.
The documented npm package is engine-dj-mcp. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| Check | Finds |
| missing_files | Tracks whose file is gone from disk |
| unavailable | Tracks Engine has marked unavailable |
| unanalyzed | Tracks Engine has not analysed |
| no_cues | Tracks with no hot cue set |
| no_beatgrid | Tracks with no beatgrid data |
| missing_key | Tracks with no key detected |
| suspicious_bpm | Analysed and tagged tempo disagree, or tempo is outside 60–200 |
| duplicates | Same artist and title, compared regardless of case in any script |
| empty_metadata | No artist or no title |
| orphan_entries | Playlist entries pointing at tracks not in this library — get_playlist_tracks shows where each one sits |
| path_form_mismatch | The file is on disk, but its name there — or a folder's on the way — is in a different Unicode form from the path Engine stored. macOS finds it anyway; Linux… |
| Code | Means |
| invalid_argument | The arguments do not make sense — both playlist_id and playlist_name, an empty list where one is required, or a playlist_name that matches several playlists… |
| library_not_found | library names nothing connected — the refusal lists what is — or the library's header could not be read. |
| ambiguous_library | No library given, and more than one supported library is connected — or the uuid given is shared by copies on different drives. Lists them — see Choosing a… |
| unsupported_schema | The library's version is outside what this server supports. |
| library_needs_recovery | Engine DJ left an unrecovered journal. Launch Engine once. |
| library_busy | Something holds a conflicting lock right now. Retry. |
| index_stale | The index could not be built yet, typically because Engine holds a lock on a first run. Carries retry_after_ms. |
| library_unreadable | The library could not be read; the snapshot taken before the first write could not be made (a full disk, or a Node older than 22.16); or a write's own… |
| search_tracks | |
| get_tracks | |
| get_playlists | |
| get_playlist_tracks | |
| get_track_performance | |
| audit_library | |
| run_sql | |
| list_libraries | |
| refresh_index | |
| create_playlist | |
| add_tracks_to_playlist | |
| remove_tracks_from_playlist | |
| reorder_playlist | |
| update_track_metadata |
{
"mcpServers": {
"engine-dj": {
"command": "npx",
"args": [
"-y",
"engine-dj-mcp"
]
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
Inspect PostgreSQL schemas and run read-only queries with the archived MCP reference server. Review its maintenance status before choosing it.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.