AudioAtlas

com.audioatlasPublished by audioatlas.comOfficial publisherv1.0.0Updated Oct 31, 2026

Music search over 185M+ tracks: describe a sound, find similar songs, ISRC/ISWC lookup, beat grids.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote AudioAtlas server that lets an assistant search a catalog of over 185 million music tracks by description, similarity, ISRC/ISWC or beat grid.

What you can do
  • Search a large music catalog by describing a sound or mood.
  • Find tracks similar to a given song.
  • Look up tracks by ISRC or ISWC identifiers.
  • Retrieve beat grid data for tracks.
When to use it
Useful when an assistant needs to find music by description or similarity, resolve ISRC/ISWC identifiers, or get beat grid data for tracks, for example in music discovery, licensing research or DJ-style workflows.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package. Requires an AudioAtlas API key sent as a bearer token in the Authorization header, obtained through an AudioAtlas API subscription.
Before you install
The API key is a secret sent in the Authorization header; keep it out of logs and shared transcripts. Access depends on a paid AudioAtlas API subscription, and search queries are sent to AudioAtlas servers.

Installation

In SourceWeft

  1. Open AudioAtlas in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.audioatlas%2Faudioatlas/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "audioatlas": {
      "type": "http",
      "url": "https://audioatlas.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 31, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.