Skip to main content
Glama
sonovault-mcp

sonovault-mcp

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SONOVAULT_API_KEYYesYour SonoVault API key.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_tracksA

Search the SonoVault catalog (93M+ tracks) by artist and title. Both are required; there is no free-text search. Returns ISRC, genre, duration, BPM, musical key, artist credits, and release info (album, label, release date) per track. Tempo and key: bpm (full tempo, e.g. 123) and musical key in three notations: key_alphanumeric (e.g. '10B'), key_musical (e.g. 'D', 'F#m') and key_open (Open Key, e.g. '3d'), plus keys[] with one entry per source. All null (keys empty) when the track has not been analysed.

get_trackA

Fetch one track by its SonoVault track ID, with full metadata (ISRC, genre, duration, BPM, musical key, artist credits, releases). Tempo and key: bpm (full tempo, e.g. 123) and musical key in three notations: key_alphanumeric (e.g. '10B'), key_musical (e.g. 'D', 'F#m') and key_open (Open Key, e.g. '3d'), plus keys[] with one entry per source. All null (keys empty) when the track has not been analysed.

lookup_isrcA

Exact lookup of a recording by its ISRC (International Standard Recording Code, e.g. GBDUW0000053). Returns the track's full metadata, including BPM and musical key. Tempo and key: bpm (full tempo, e.g. 123) and musical key in three notations: key_alphanumeric (e.g. '10B'), key_musical (e.g. 'D', 'F#m') and key_open (Open Key, e.g. '3d'), plus keys[] with one entry per source. All null (keys empty) when the track has not been analysed.

get_work_codesA

Find the ISWC work code(s) behind a recording, by ISRC or SonoVault track ID. Useful for royalty and publishing workflows. One recording can carry several ISWCs (medleys, samples).

get_recordings_of_workA

List every recording of a musical work by its ISWC (e.g. T0710204399 or T-071.020.439-9). Returns recordings sorted by popularity, each with a representative ISRC.

get_platform_linksA

Resolve a track to its ID and deep link on every supported platform: Spotify, Apple Music, Tidal, Beatport, Discogs, MusicBrainz, YouTube. Identify the track by exactly one of: SonoVault id, ISRC, or any platform's ID.

resolve_tracksA

Resolve up to 100 inputs in one call to canonical tracks plus cross-platform links. input_type picks the key: 'track_name' (items are {artist, title} objects), 'isrc', 'sonovault_id', or a platform id type ('spotify_id', 'applemusic_id', 'tidal_id', 'beatport_id', 'discogs_id', 'musicbrainz_id'). A discogs_id item is a Discogs track key (release ID plus track position, e.g. '2844-A'), not a bare release ID. Each matched track carries the same fields as get_track, including BPM and musical key. Costs one API credit per line.

search_artistsA

Search artists by name. Returns id, name, country, formation year, release count, and the wikidata_id and musicbrainz_id identifiers for joining against external datasets.

get_artist_releasesA

An artist's releases, newest first. Use the cursor from a previous call for the next page. Optional from/until (YYYY-MM-DD, inclusive) limit it to a release-date range.

search_labelsA

Search record labels by name. Returns id, name, and release count.

get_label_releasesA

A label's releases, newest first, with artist per release. Cursor-paginated. Optional from/until (YYYY-MM-DD, inclusive) limit it to a release-date range; pass the same day for both to see what the label released that day.

search_releasesC

Search releases by title, optionally narrowed by artist name.

get_releaseA

Fetch one release by SonoVault release ID, including its full tracklist with ISRCs, BPM and musical key per track (same bpm/key_* fields as get_track, null when not analysed). Tracks come back in playing order, each with disc_number and track_number; a track whose position is unknown sorts last with both null. A SonoVault release groups every edition of an album onto one record, so the response also carries an editions array naming the real editions behind it, each with its provider, format, release date, barcode, country, track count, label and catalog number (pressings of one album often carry different labels); pass one of their ids as edition to render that edition's numbering instead of the default consensus. musicbrainz_release_ids and musicbrainz_release_group_ids are arrays for the same reason.

list_genresA

The canonical SonoVault genre hierarchy: 25 main genres plus subgenres, with IDs.

browse_tracksA

Discover tracks by filter: label ID, artist ID, genre name or genre ID (from list_genres), or release year. At least one filter is required. Needs a paid SonoVault tier; free-tier keys get a 403.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 15 tools

Disambiguation4/5

Most tools have clearly distinct resource/action targets, but there is some overlap between resolve_tracks, get_platform_links, and the single-track lookup tools. The descriptions distinguish batch resolution from single-track platform-link retrieval, but an agent may still need to pause to choose between resolve_tracks with platform IDs and get_platform_links.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: get_, search_, lookup_, resolve_, list_, and browse_. The convention is predictable throughout and no naming style is mixed.

Tool Count5/5

Fifteen tools is well-scoped for a music catalog metadata server covering tracks, releases, artists, labels, genres, works, and platform links. Each tool appears to earn its place without excessive redundancy.

Completeness4/5

The surface covers the core read-only music catalog lifecycle well: search and lookup for tracks, releases, artists, labels, works, genres, and platform links. Minor gaps exist, such as no direct get_artist or get_label by ID, but agents can work around these via search or release tools.

Maintenance

ActivityMaintained
ResponsivenessLimited data