How to Use the AcoustID MCP in Cline

Q: Can Cline use AcoustID to find alternate versions of a song?

The searchbymbid tool does exactly this. It takes a MusicBrainz ID and returns every known audio fingerprint linked to that specific recording, which helps identify different masters or radio edits.

Give Cline the ability to identify songs and fetch MusicBrainz records right inside VS Code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect AcoustID MCP to Cline

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

Setup AcoustID with Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Audio fingerprinting MCP Server

The `lookup_by_fingerprint` tool takes a generated Chromaprint and duration to find matching songs in the database. Cline executes this directly from your VS Code sidebar to identify unknown audio files in your workspace. End-to-end task execution makes this powerful. Ask your agent to build a music tagging script, and it will write the code, call the lookup tool to test it, and show you the working diff.

Deep MusicBrainz integration

The `get_recording_metadata` tool pulls complete track histories. It returns artists, release groups, and all associated fingerprints linked to a specific AcoustID. Text searches bypass the fingerprint requirement entirely. Cline uses `search_by_recording` to look up known song names and grab their exact MusicBrainz IDs to populate your local database.

Fingerprint submission workflow

The `submit_fingerprint` tool adds uncataloged tracks to the registry. You provide the raw fingerprint string, duration, and optional metadata like the artist name. Doing this manually involves curl commands and API keys. Your VS Code agent handles the payload construction, fires the request, and captures the new AcoustID for your application to use immediately.

Setup guide

Set up AcoustID MCP in Cline

Prerequisites

VS Code with Cline extension installed
Active Vinkius subscription with a valid endpoint token

1

Open Cline MCP settings

Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.
2

Add a remote server

Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type acoustid-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.
3

Enable the server

After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.
4

Start using tools

Return to the Cline chat and ask: "Check my latest AcoustID refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings

{
  "mcpServers": {
    "acoustid-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by AcoustID. 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.

Why Choose Vinkius

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

Connect AcoustID now

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 Cline

Open the Cline sidebar and click the MCP Servers icon. Navigate to the Remote Servers tab to add the Vinkius URL, or grab it directly from the built-in Marketplace tab.

The `search_by_mbid` tool does exactly this. It takes a MusicBrainz ID and returns every known audio fingerprint linked to that specific recording, which helps identify different masters or radio edits.

The server expects the raw fingerprint string. Your agent can write a quick Python or Node script to generate that string from your local audio file before passing it to the lookup tool.

Standard APIs require you to write boilerplate connection code and manage authentication. The MCP standard lets your agent natively call these endpoints as built-in tools without writing any integration logic.

The server only processes Chromaprint hashes, track durations, and basic text queries like artist names. Everything executes inside a zero-trust environment, and the connection drops the moment your query finishes.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript