4,500+ servers built on MCP Fusion
Vinkius
AcoustID logo
Vinkius
Claude Desktop logo

How to Use the AcoustID MCP in Claude

Identify songs by audio fingerprint directly inside Claude Desktop using the AcoustID MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

AcoustID MCP on Cursor AI Code Editor MCP Client AcoustID MCP on Claude Desktop App MCP Integration AcoustID MCP on OpenAI Agents SDK MCP Compatible AcoustID MCP on Visual Studio Code MCP Extension Client AcoustID MCP on GitHub Copilot AI Agent MCP Integration AcoustID MCP on Google Gemini AI MCP Integration AcoustID MCP on Lovable AI Development MCP Client AcoustID MCP on Mistral AI Agents MCP Compatible AcoustID MCP on Amazon AWS Bedrock MCP Support
MCP Servers - Free for Subscribers
Claude Desktop

Connect AcoustID MCP to Claude Desktop

Create your Vinkius account to connect AcoustID to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Identify songs directly inside Claude Desktop

Your Claude Desktop agent uses `lookup_by_fingerprint` to identify mystery tracks directly from your chat window. This local setup runs on your machine via stdio, meaning the agent queries the AcoustID database directly. You get immediate metadata back in your sidebar, making it easy to sort audio archives or tag untagged WAV files on your local drive.

Clean up music catalogs with MusicBrainz links

Your local Claude Desktop agent uses `search_by_recording` to cross-reference track lists against the vast MusicBrainz database. Once the agent locates the ID, it invokes `get_recording_metadata` to retrieve release groups and artist credits. You get clean, structured JSON in your chat, verified by our MCP runtime.

Submit new audio fingerprints from your chat

When local audio files do not return a match, Claude Desktop uses `submit_fingerprint` to handle the registration process directly. If you know the song name, the agent appends it to the submission, returning a freshly minted AcoustID. This lets you build a custom cataloging tool inside your desktop workspace without writing a line of python.

Setup guide

Set up AcoustID MCP in Claude Web or Desktop

  1. 1

    Open Claude Settings

    Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

  2. 2

    Add Custom Connector

    Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

  3. 3

    Start a conversation

    Open a new chat. The AcoustID MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about AcoustID MCP in Claude Desktop

Your desktop agent takes an audio fingerprint string you paste into the chat and runs `lookup_by_fingerprint`. It returns the exact song name, artist, and MusicBrainz ID in a few seconds.
Yes, you can connect this MCP Server to claude.ai by adding the remote server URL in your Integrations settings. This lets you search and match audio files from any browser on any device.
No, the agent calls the AcoustID API over the internet using your configured endpoint token. It runs `get_recording_metadata` or `search_by_mbid` on the remote registry, so you do not store gigabytes of audio data locally.
The agent displays all matches sorted by confidence score. It uses the metadata from `get_recording_metadata` to help you pick the correct release group or artist.
The server only processes the raw Chromaprint strings and metadata you explicitly send to the chat. Your actual audio files never leave your local machine, and the Vinkius MCP host runs in an isolated sandbox that destroys session data instantly.

Start using the AcoustID MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 5 tools

We've already built the connector for AcoustID. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 5 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.