find_tracks_by_bpm — FreqBlog Music Metadata MCP Tool Read-only
find_tracks_by_bpm
(find tracks by bpm) is one of 12 tools on the
FreqBlog Music Metadata
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call find_tracks_by_bpm from your client
- Claude Code FreqBlog Music Metadata find_tracks_by_bpm run in your project directory
- Claude Desktop FreqBlog Music Metadata find_tracks_by_bpm ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FreqBlog Music Metadata find_tracks_by_bpm ~/.cursor/mcp.json
- VS Code FreqBlog Music Metadata find_tracks_by_bpm .vscode/mcp.json
- Zed FreqBlog Music Metadata find_tracks_by_bpm ~/.config/zed/settings.json
- Windsurf FreqBlog Music Metadata find_tracks_by_bpm ~/.codeium/windsurf/mcp_config.json
- Cline FreqBlog Music Metadata find_tracks_by_bpm ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FreqBlog Music Metadata find_tracks_by_bpm ~/.gemini/settings.json
- Grok FreqBlog Music Metadata find_tracks_by_bpm .mcp.json (in your project root)
- ChatGPT FreqBlog Music Metadata find_tracks_by_bpm Settings → Connectors → Advanced → Developer mode
- Claude.ai FreqBlog Music Metadata find_tracks_by_bpm Settings → Connectors → Add custom connector
- LangChain FreqBlog Music Metadata find_tracks_by_bpm pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http music-metadata https://mcp.freqblog.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.