get_audio_features — FreqBlog Music Metadata MCP Tool Read-only
get_audio_features
(get audio features) 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 get_audio_features from your client
- Claude Code FreqBlog Music Metadata get_audio_features run in your project directory
- Claude Desktop FreqBlog Music Metadata get_audio_features ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FreqBlog Music Metadata get_audio_features ~/.cursor/mcp.json
- VS Code FreqBlog Music Metadata get_audio_features .vscode/mcp.json
- Zed FreqBlog Music Metadata get_audio_features ~/.config/zed/settings.json
- Windsurf FreqBlog Music Metadata get_audio_features ~/.codeium/windsurf/mcp_config.json
- Cline FreqBlog Music Metadata get_audio_features ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FreqBlog Music Metadata get_audio_features ~/.gemini/settings.json
- Grok FreqBlog Music Metadata get_audio_features .mcp.json (in your project root)
- ChatGPT FreqBlog Music Metadata get_audio_features Settings → Connectors → Advanced → Developer mode
- Claude.ai FreqBlog Music Metadata get_audio_features Settings → Connectors → Add custom connector
- LangChain FreqBlog Music Metadata get_audio_features 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.