FreqBlog Music Metadata
Fetch BPM, key, mood, and genre audio features for real tracks when Spotify-style audio-features APIs are unavailable.
Overview
FreqBlog Music Metadata is an MCP server for the Build phase that returns BPM, key, mood, and genre audio features for real tracks as a Spotify audio-features alternative.
What is this MCP server?
- Audio features: BPM, key, mood, and genre for real tracks
- Positioned as a Spotify audio-features API replacement
- FreqBlog Music Metadata remote at mcp.freqblog.com
- Streamable HTTP MCP v1.0.0
- Features: BPM, key, mood, genre for real tracks
- Remote URL https://mcp.freqblog.com/mcp
- Server version 1.0.0
What problem does it solve?
Spotify audio-features gaps block playlist, DJ, and discovery features unless you bolt on another metadata source by hand.
Who is it for?
Indie builders making music apps, blogs, or agent workflows that need danceability-style signals without Spotify’s deprecated features.
Skip if: Products that need full stream playback, lyric licensing, or label-grade rights data from one MCP.
What do I get? / Deliverables
Your agent can query structured BPM, key, mood, and genre features via MCP while you focus on app logic.
- MCP connection to FreqBlog music metadata service
- Structured BPM, key, mood, and genre fields for agent-driven features
- Integration path for apps that previously relied on Spotify audio-features
Recommended MCP Servers
Journey fit
Music and media apps integrate metadata during build when playlists, recommendations, or editorial features need structured audio signals. Integrations covers third-party MCP services that enrich your product data model without hosting models yourself.
How it compares
Track audio-features data MCP, not a DAW plugin or a general-purpose media transcoding skill.
Common Questions / FAQ
Who is FreqBlog Music Metadata for?
Solo builders and small teams building music discovery, DJ, or content tools who need BPM, key, mood, and genre features via an agent-friendly API.
When should I use FreqBlog Music Metadata?
Use it during build and integrations when you are wiring recommendation, sorting, or editorial features that depend on audio feature vectors for real tracks.
How do I add FreqBlog Music Metadata to my agent?
Add the streamable HTTP remote https://mcp.freqblog.com/mcp to your MCP client, follow FreqBlog auth if required, and call the metadata tools from your agent when resolving tracks.