FreqBlog Music Metadata
RemoteAbout FreqBlog Music Metadata
Audio features + harmonic set-building for tracks by name/ISRC. Spotify audio-features replacement.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.freqblog.com/mcpclaude mcp add --transport http com-freqblog-music-metadata https://mcp.freqblog.com/mcp{"mcpServers":{"com-freqblog-music-metadata":{"type":"http","url":"https://mcp.freqblog.com/mcp"}}}Open in Cursor{"servers":{"com-freqblog-music-metadata":{"type":"http","url":"https://mcp.freqblog.com/mcp"}}}Open in VS Code{"mcpServers":{"com-freqblog-music-metadata":{"type":"http","url":"https://mcp.freqblog.com/mcp"}}}{"mcpServers":{"com-freqblog-music-metadata":{"serverUrl":"https://mcp.freqblog.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
12| Parameter | Type | Required | Description |
|---|---|---|---|
| isrc | any | No | ISRC, e.g. 'USUM71900001'. |
| mbid | any | No | MusicBrainz recording ID (UUID). The precise key when there is no ISRC, e.g. pre-1986 recordings. |
| track | any | No | Track title. Use with `artist` when known. Supply AT LEAST ONE of track/isrc/mbid/spotify_id. Sending several is fine — they resolve by precedence (track > isrc > mbid > spotify_id) and the rest are ignored. |
| artist | any | No | Artist name. Only used with `track`; required when the title is <=2 characters. |
| spotify_id | any | No | Spotify track ID, 'spotify:track:...' URI, or open.spotify.com URL. Resolved per request by reading the track's title from Spotify's public embed page and matching it against our catalogue (no Spotify IDs are stored) — a title several artists share is ambiguous and misses rather than guessing; prefer track (+artist) or isrc. |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.