sonovault-mcp connects an AI assistant to the SonoVault music metadata API. Through that connection, an assistant can search and look up music records, resolve identifiers, and retrieve information about tracks, artists, labels, and releases. The server exposes read-only tools, so it is for finding and organizing information rather than editing a catalog. Results can include identifiers and links across music platforms, as well as track and release details available from the API.
It also supports requests that connect recordings to compositions, resolve multiple inputs together, and inspect release tracklists or editions. What is returned depends on the relevant API data and the access level of the SonoVault account.
What can sonovault-mcp do?
The server exposes tools for music search and lookup, identifier resolution, and catalog exploration. Track-related results can include genre, label, release date, ISRC, BPM, and musical key; BPM and key may be null when a track has not been analysed. Release lookups can return tracklists and edition details.
- Search tracks, artists, labels, and releases, and retrieve artist or label releases.
- Look up a track by ISRC or SonoVault ID, and map recordings to compositions with ISWC work codes.
- Resolve up to 100 track names, ISRCs, or platform IDs in one call.
- Return platform IDs and links for Spotify, Apple Music, Tidal, Beatport, Discogs, MusicBrainz, and YouTube.
- Browse tracks by artist, label, genre, or year with a paid SonoVault API tier.
How sonovault-mcp connects and authenticates
sonovault-mcp runs locally and communicates with an MCP client over stdio. It sends requests to the SonoVault API using a SonoVault API key supplied to the server through an environment variable. The README names Claude Desktop, Claude Code, Cursor, VS Code with GitHub Copilot, Windsurf, and other clients that support MCP over stdio. The verified setup describes local stdio; a hosted HTTP mode is not documented in the available facts.
Who is sonovault-mcp best for?
It is suited to people who want an AI assistant to search music metadata, match identifiers, inspect artist or label releases, or resolve batches of track references. A SonoVault API key is required. The free account tier includes a monthly request allowance and supports search, ISRC lookup, and platform links; track catalog browsing requires a paid API tier. Paid plans add browsing and the new releases feed, with larger request allowances at higher tiers.
What sonovault-mcp can access and change
With its API key, the server can request music metadata and identifiers from SonoVault, including track, artist, label, release, and platform-link information available to that account. Its tools are read-only: they do not modify catalog records, so there are no catalog edits or deletion actions to undo. Free-tier access cannot browse the catalog, and the server does not provide lyrics, audio previews, or artwork. Requests are subject to monthly quotas and burst limits; exceeding available credits can result in a declined request.
Alternatives to sonovault-mcp
For other MCP options in the directory, Supabase MCP Server is a database-oriented option, while Google Drive MCP is a file-oriented option. These are adjacent choices rather than verified substitutes for SonoVault’s music metadata API. Choose between them based on whether the task concerns music records, database work, or files; their capabilities should be checked on their own listing pages.