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

How to Use the AcoustID MCP in Claude Code

Run AcoustID lookups and audio fingerprint matching straight from your terminal with Claude Code.

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 Code

Connect AcoustID MCP to Claude Code

Create your Vinkius account to connect AcoustID to Claude Code 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

Terminal-native MCP Server matching with Claude Code

The `lookup_by_fingerprint` tool accepts a Chromaprint string and duration to return matching recordings and confidence scores. You run this entirely headless, feeding local audio data directly into the matching engine. Piping these results into shell scripts changes how you process bulk media. Tell your CLI agent to scan a directory of WAV files, and it will generate the prints, run the lookups, and output a clean JSON map of the results.

Command-line metadata retrieval

The `get_recording_metadata` tool fetches artist and release group information. It queries the database using an existing AcoustID to pull down the full MusicBrainz record. Finding specific tracks by name is just as fast. The `search_by_recording` tool lets you type a song title into your terminal, returning the exact IDs needed for your backend database.

Automated fingerprint ingestion

The `submit_fingerprint` tool pushes new audio signatures to the public database. It takes the mathematical audio representation along with track duration to register new songs. CI/CD pipelines can trigger this automatically. When a new master track drops into your AWS S3 bucket, your headless agent can generate the print and submit it to the registry without human intervention.

Setup guide

Set up AcoustID MCP in Claude Code

Prerequisites

  • Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Run the add command

    Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.

  2. 2

    Verify the connection

    Start a Claude Code session and type /mcp to list connected servers. You should see acoustid-mcp with a green status indicator.

  3. 3

    Start using tools

    Ask Claude Code something like "Check my latest AcoustID transactions." It will automatically discover and invoke the available AcoustID tools.

Terminal
claude mcp add --transport http acoustid-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

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 Code

Run `claude mcp add --transport http vinkius-acoustid -- ` in your terminal. Make sure to put all connection flags before the server name. Check your `~/.claude.json` file to verify the configuration.
Yes, by combining local scripting with the `search_by_mbid` tool. The agent can find tracks sharing the same MusicBrainz ID but different audio fingerprints, helping you spot redundant files.
The CLI client requires no GUI or browser. You can run these tools inside Docker containers, GitHub Actions, or remote SSH sessions to process audio files entirely in the background.
The tools do not process raw audio files directly. They expect the mathematical Chromaprint string, which your terminal agent can generate using command-line tools like `fpcalc` before calling the server.
Raw audio never leaves your local machine. The server only receives mathematical Chromaprint hashes and duration integers, processed through Vinkius's strict V8 Isolate Sandbox before being instantly discarded.

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.