AudD Music Recognition

io.auddPublished by audd.ioOfficial publisherv1.0.0Updated Oct 26, 2026

Music recognition with AudD: identify songs, monitor streams, call the API, plus account tools

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote AudD server that lets an assistant identify songs, monitor audio streams, call the AudD API and manage the account.

What you can do
  • Identify songs from audio the assistant submits for recognition
  • Monitor audio streams for music matches
  • Call the AudD API directly for other recognition requests
  • Manage the AudD account through account tools
When to use it
Useful when you want an assistant to recognize music, check what is playing in a stream, or work with AudD's recognition API without writing integration code yourself.
Requirements
A remote MCP endpoint at mcp.audd.io over streamable HTTP; OAuth sign-in is required, so an AudD account is needed. No environment variables or headers are declared.
Before you install
Access is tied to an OAuth-authorized AudD account, and account tools may change account data. Recognition requests send audio or stream references to AudD's service, and AudD plans may charge for API usage; check quota and pricing before heavy use.

Installation

In SourceWeft

  1. Open AudD Music Recognition in the dashboard and add it to a workspace.
  2. Connect the required 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/io.audd%2Faudd/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "audd-music-recognition": {
      "type": "http",
      "url": "https://mcp.audd.io/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 18, 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.

Other Audd integrations

AudD Billing & Usage

io.audd

AudD account tools: usage stats, billing, API token, plans, payment links, API docs, and API calls

Streamable HTTPWeb executable
Knowledge & MemoryNot indexed yetOct 18, 2026