Music search API and MCP server
The AudioAtlas API gives applications and AI assistants music search over more than 185 million tracks: natural-language search, similar tracks, ISRC and ISWC lookup, beat grids and audio identification. The same tools are available to Claude through a remote MCP server.
Endpoints
- Search: natural-language and keyword search with BPM, energy, mood, vocals, catalogue and AI-music filters.
- Similar tracks: nearest neighbours of a track by audio embeddings.
- Lookup: track by id, by metadata, or bulk ISRC lookup with callback.
- Beat grid: beat and downbeat timings for video sync.
- Identify audio: recognise a recording from an audio file.
- Catalogue statistics and artist metrics.
Use AudioAtlas from Claude (MCP)
Connect the remote MCP server with your API key and Claude can search music, find similar tracks and look up rights data directly:
claude mcp add --transport http audioatlas https://audioatlas.com/mcp \
--header "Authorization: Bearer YOUR_API_KEY"The server exposes 12 tools, including search_music, find_similar_tracks, lookup_tracks, get_track, beat_grid, identify_audio and catalog_stats.
Data returned
Title, artist, catalogue, BPM, musical key, energy, mood, genre, vocals, duration, AI-generated indicator, ISRC, ISWC, composers and publishers.
Frequently asked questions
Is there an MCP server for music search?
Yes. AudioAtlas runs a remote MCP server at https://audioatlas.com/mcp. Connect it to Claude with an AudioAtlas API key to search music, find similar tracks and look up ISRC and ISWC.
What can I build with a music search API?
Music recommendation in video editors, sound-alike search for advertising, catalogue tools for publishers, playlist generation, and AI assistants that answer music briefs.
How do I get an API key?
Subscribe on the API page; the key works for both the REST API and the MCP server.