ACRCloud Music Recognition MCP. Pinpoint music details from audio and metadata.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
ACRCloud Music Recognition. Identify songs from audio URLs and search global music databases. This server lets your AI agent pinpoint music by analyzing audio files, querying tracks by ISRC, and finding artists or albums by name.
It pulls rich metadata, including Spotify and YouTube links, directly into your workflow.
What your AI agents can do
Get track by isrc
Gets detailed metadata for a track using its ISRC code.
Identify music from url
Identifies a song by analyzing an audio file URL (MP3, WAV).
Search albums
Searches for music albums using a title or artist name.
Sends an audio URL and returns the song's title, artist, album, and metadata.
Retrieves complete metadata for a single track using its unique ISRC identifier.
Finds albums by filtering using an artist name or album title.
Finds artist profiles using a provided artist name.
Locates tracks by searching across names, artist names, or partial lyrics.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
ACRCloud Music Recognition: 5 Tools for Media Metadata
Use these tools to analyze audio files, look up tracks by ISRC, and search the global music database by artist, album, or name.
019d8412get track by isrc
Gets detailed metadata for a track using its ISRC code.
019d8412identify music from url
Identifies a song by analyzing an audio file URL (MP3, WAV).
019d8412search albums
Searches for music albums using a title or artist name.
019d8412search artists
Searches for music artists by name.
019d8412search tracks
Searches for music tracks using name, artist name, or lyric fragments.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with ACRCloud Music Recognition, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You'll hook up your AI agent to ACRCloud to pinpoint songs and pull rich music metadata. You can make your agent use the identify_music_from_url tool to analyze an audio file URL—MP3 or WAV—and get the song's title, artist, and album right away. You can use get_track_by_isrc to pull full details on a single track using its unique ISRC code.
You'll find artist profiles by running search_artists with an artist name. You can find albums by filtering using search_albums with an artist name or album title. You'll locate specific tracks using search_tracks by name, artist name, or even partial lyrics.
How ACRCloud Music Recognition MCP Works
- 1 Subscribe to the ACRCloud server and provide your credentials (Access Key, Secret, Host).
- 2 Your AI client sends a query (e.g., an audio URL, an ISRC, or an artist name) to the relevant tool.
- 3 The server executes the lookup and returns structured data containing the song's metadata, links, and confidence scores.
The bottom line is that you get reliable, structured music data without leaving your AI workflow.
Who Is ACRCloud Music Recognition MCP For?
This is for anyone whose job requires connecting media data to a structured workflow. Think content creators who need background music IDs, developers building media applications, or researchers who need to track music usage. If your job involves knowing what song is playing or where to find a track's metadata, you need this.
Checks background music for copyright metadata or finds the ID for a track they want to use in a video project.
Builds applications that need to identify music streams or retrieve rich metadata (like Spotify/YouTube links) for user-facing features.
Indexes large collections of media, ensuring every track has proper metadata and links for future retrieval.
What Changes When You Connect
- Instant Identification: Send an audio URL and your agent gets the song title, artist, and album instantly. You don't have to manually run Shazam or check multiple APIs.
- Metadata Certainty: Need absolute proof of a track? Use
get_track_by_isrc. The ISRC code provides a unique, unambiguous lookup for precise metadata. - Direct Streaming Links: The server pulls direct IDs and links for Spotify, YouTube, and other major platforms. This saves the step of having to find the track manually after identification.
- Structured Search Paths: You don't just search vaguely. You can use
search_artiststo narrow down an artist, thensearch_albumsfor their work, and finallysearch_trackswithin that context. - Confidence Scoring: The output includes confidence scores and professional analytics. This lets your agent tell you how sure it is about the identification, which is crucial for reliable workflows.
Real-World Use Cases
Investigating background music for a video project
A content creator hears a song and needs to know the artist for copyright clearance. They send the audio sample URL to the agent. The agent uses identify_music_from_url and immediately returns the full metadata, including streaming links, letting the creator move right to licensing.
Building a music data lookup tool
A developer wants to build a feature that lets users search by unique identifiers. They use get_track_by_isrc to validate a user-provided ISRC code, getting the full track details. They then use search_artists to pull a list of related artists for the user to explore.
Analyzing a band's discography
A music enthusiast wants to see everything Daft Punk has done. They first use search_artists to confirm the artist. Next, they use search_albums to pull a list of albums, and then search_tracks to pull popular songs from a specific album, building a complete profile.
Verifying a track's existence and links
A researcher finds a track name and an album name but needs to confirm its official metadata. They first use search_tracks to find the match, and then they can use the resulting metadata to get the specific Spotify or YouTube links.
The Tradeoffs
Searching for everything at once
Trying to ask the agent, 'What are the links, the artists, and the tracks for this song?' in one vague prompt. The agent might fail or only use one tool.
→
Break it down. First, run identify_music_from_url to get the core ID. Then, use get_track_by_isrc if you have the ISRC. Finally, use search_artists if you need related artists. Chain the tools explicitly.
Ignoring unique identifiers
Just giving the agent a track name like 'Blinding Lights' and hoping it finds the right one. Ambiguity is a killer.
→
If possible, always start with the ISRC code. Use get_track_by_isrc first. If you don't have the ISRC, use search_tracks with the name, but be ready to narrow the results.
Assuming one tool covers all needs
Thinking search_tracks will give you the Spotify link. It won't; it only finds the track record. You need to run the result through the full identification or ISRC lookup to get the links.
→
When It Fits, When It Doesn't
Use this server if your primary goal is connecting audio media to structured, verifiable metadata. Specifically, if you have an audio file URL, an ISRC code, or a known artist/album name, these tools handle the lookup. Don't use this if you just need a general search engine; this is specialized media intelligence. Also, don't rely on it for genre analysis or mood detection; it only works with specific identifiers. If your input is a vague description like 'sad 80s synth-pop,' you'll need to search by name and hope for the best. For the best results, always prioritize using get_track_by_isrc or identify_music_from_url.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by ACRCloud. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 5 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Finding music details shouldn't feel like a scavenger hunt.
Before this, finding a track's full metadata meant a dozen steps: you'd copy the song title, paste it into a search, find the album, then copy the album name, check the artist's official page, and finally, search for the specific track to get the right link. It was a mess of manual copy-pasting and clicking through disparate websites.
Now, you send the audio URL to your agent. The agent uses `identify_music_from_url` and gives you the full, structured data set—artist, album, and direct links for Spotify and YouTube—in one go. You just get the answer.
ACRCloud Music Recognition MCP Server: Pinpoint music data instantly.
You skip the manual process of searching through artist pages, checking multiple database types, and trying to match names. The agent handles the ISRC lookup, the URL fingerprinting, and the name searches automatically.
It’s a single point of truth for music data. You feed it the media, and it gives you the structured metadata you need to build something.
Common Questions About ACRCloud Music Recognition MCP
How do I use the identify_music_from_url tool with ACRCloud Music Recognition? +
Just send the URL of the audio file (MP3, WAV). The agent runs identify_music_from_url and returns the song details, artist, and album metadata.
Is there a tool to search by song name only? +
Yes, use search_tracks. This tool searches for tracks based on name, artist name, or partial lyrics. Remember, the more detail you provide, the better the results.
How do I get metadata using the ISRC code? +
Use the get_track_by_isrc tool. This is the most precise way to get track metadata because the ISRC code is a unique global identifier.
Does ACRCloud Music Recognition handle multiple search types? +
Yes. You can use search_artists to narrow the scope, then search_albums to find all the work by that artist, and finally search_tracks for specific songs.
What happens if my audio file is corrupted? +
The system will return an error message indicating the file could not be processed. You need to check the file integrity and provide a valid URL for the agent to run identify_music_from_url.
How do I set up my credentials for `identify_music_from_url`? +
You must provide your ACRCloud Access Key, Secret, and Host details. These credentials are required for the server to authenticate with ACRCloud and process your audio files.
What is the difference between `search_tracks` and `get_track_by_isrc`? +
Use search_tracks when you know general info like a partial lyric or artist name. Use get_track_by_isrc when you have the specific ISRC code for guaranteed precision.
Can `search_albums` handle complex queries, like searching by a genre? +
No, search_albums searches only by album title or artist name. If you need to filter by genre, you should use a dedicated database query tool instead.
How do I get ACRCloud credentials? +
Sign up at the ACRCloud Console, create a 'Music Recognition' project, and you will find your Access Key, Secret, and Host in the project settings.
Which audio formats are supported for identification? +
ACRCloud supports most common audio formats including MP3, WAV, AAC, and OGG. The agent will download the file from the provided URL and send it for fingerprinting.
Can I find the ISRC code for a specific track? +
Yes! When you identify a song or search for metadata, the acr_music_search tool returns industry-standard identifiers like ISRC, allowing you to track specific recordings across different systems.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Agify
Predict the age of a person based on their first name using the Agify.io API.
DeckMatch
Match startup pitch decks with investors using AI that analyzes fit, tracks outreach, and surfaces the right funding connections.
LLM ROUGE & BLEU Evaluator
Evaluate AI text generation quality. Compute exact mathematical BLEU and ROUGE scores comparing generated text to reference documents.
You might also like
Meshy (3D AI)
Transform text and images into high-quality 3D models using Meshy's generative AI directly from your agent.
Gitee
Collaborative code hosting and development platform — manage repositories, issues, and pull requests via AI.
IBGE Serviços de Dados
Access official Brazilian statistics, geographic data, economic classifications (CNAE), and demographic insights directly from IBGE.