# FreqBlog Music Metadata MCP server

Audio features (BPM, key, mood, genre) for real tracks - a Spotify audio-features replacement.

## Links
- Registry page: https://www.getdrio.com/mcp/com-freqblog-music-metadata

## Install
- Endpoint: https://mcp.freqblog.com/mcp
- Auth: Not captured

## Setup notes
- Remote endpoint: https://mcp.freqblog.com/mcp

## Tools
- get_audio_features - Get audio features for ONE track — BPM, musical key (name + Camelot + Open Key),
    energy, danceability, valence, acousticness, instrumentalness, liveness, speechiness,
    loudness, mood, mood_vector, genre, time signature, duration and more.

    This is the drop-in replacement for Spotify's deprecated /audio-features endpoint.
    Provide EXACTLY ONE identifier:
      - `track` (optionally with `artist`) — e.g. track="Blinding Lights", artist="The Weeknd".
      - `isrc` — e.g. "USUM71900001".
      - `mbid` — a MusicBrainz recording UUID.
      - `spotify_id` — a Spotify track ID, URI, or URL.

    Returns a JSON object of features. Some feature fields may be null for tracks resolved
    via the fallback catalogs (only audio-derived values are present for fully analysed
    tracks). If a track name is not yet in the catalog, the API queues an on-demand
    analysis and this tool reports that it is queued — retry in ~30s-2min. If you only
    have a fuzzy or partial name, call search_catalog first to find the exact track.
     Endpoint: https://mcp.freqblog.com/mcp
- get_audio_features_batch - Get audio features for MANY tracks in one call (up to 50) — ideal for analysing a
    whole playlist at once. Pass a list of {track, artist?} objects.

    Returns counts (`found` / `not_found`) plus a per-track `results` array, where each
    entry's `result` is the same feature object as get_audio_features (or null when not
    found). Each track consumes one quota unit. For a single track, use get_audio_features.
     Endpoint: https://mcp.freqblog.com/mcp
- search_catalog - Full-text search the catalog by any mix of track / artist / album tokens. Use this to
    resolve a fuzzy, partial, or misspelled name into concrete tracks BEFORE calling
    get_audio_features.

    Returns lightweight stubs (itunes_track_id, track_name, artist_name, album, etc.) ranked
    by relevance — NOT audio features. Take the best match's track_name + artist_name and
    pass them to get_audio_features, or reuse its itunes_track_id as a `track_id` seed for
    discovery tools.
     Endpoint: https://mcp.freqblog.com/mcp
- find_tracks_by_bpm - Find catalog tracks near a target tempo. Returns tracks whose BPM is within
    +/-`tolerance` of `bpm`, ordered by closeness then popularity — useful for DJ set
    planning, workout playlists, or tempo-matching. Each returned track carries full audio
    features. To also constrain by musical key, combine with find_tracks_by_key.
     Endpoint: https://mcp.freqblog.com/mcp
- find_tracks_by_key - Find catalog tracks in a given musical key — for harmonic mixing and key-locked
    playlists. `key` accepts Camelot ("8A"), Open Key ("1m"), or a key name ("A-Minor",
    "F#-Major"). Returns tracks ordered by popularity, each with full audio features. To
    discover which keys mix well with a given key first, use find_compatible_keys.
     Endpoint: https://mcp.freqblog.com/mcp
- find_compatible_keys - Given a Camelot key (e.g. "8A", "12B"), return the harmonically compatible keys for DJ
    mixing — the same key, the relative major/minor, and the adjacent +/-1 keys on the
    Camelot wheel. With `extended=true` also returns the +7/-7 energy-boost / energy-drop
    keys. Pure music theory — no catalog lookup and no quota cost. Pair with find_tracks_by_key
    to then pull actual tracks in each compatible key.
     Endpoint: https://mcp.freqblog.com/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: com.freqblog
- Version: 1.0.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Jun 7, 2026
- Source: https://registry.modelcontextprotocol.io