How to Use the AcoustID MCP in Windsurf

Q: How do I configure the AcoustID MCP server in Windsurf?

Open your /.codeium/windsurf/mcpconfig.json file and add the server endpoint. You can also use the Settings menu to navigate to the Cascade MCP Servers UI. Hit refresh in the MCP panel and Cascade will immediately see the new tools.

Q: Can Windsurf and AcoustID identify songs from just a title?

Yes, the searchbyrecording tool handles text-based queries. Cascade passes the track name or artist to find matching recordings and their corresponding AcoustIDs before you even generate an audio fingerprint.

Let Windsurf's Cascade agent identify audio fingerprints and pull MusicBrainz metadata directly into your codebase.

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 Windsurf

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Audio identification MCP Server for Windsurf

The `lookup_by_fingerprint` tool matches raw audio signatures against the AcoustID database to return confidence scores and track details. Cascade grabs your local audio file, generates the Chromaprint, and fires off the request without you writing a single API call. You just tell the agent to catalog a folder of unnamed MP3s. It runs the lookups, parses the JSON responses, and renames the files based on the matched MusicBrainz IDs.

Bi-directional metadata matching

The `get_recording_metadata` tool fetches full release group data. Hand it a known AcoustID, and it returns the associated artists, titles, and release groups. Reverse searches work just as smoothly. Cascade can take an existing MusicBrainz ID and run `search_by_mbid` to find all linked audio fingerprints, which helps when you need to deduplicate tracks in your library.

Direct database submissions

The `submit_fingerprint` tool pushes new tracks to the public registry. It takes the Chromaprint string and duration, plus optional artist and title tags for previously unknown tracks. Building an ingest pipeline usually means context switching between your IDE and terminal. Now your agent handles the submission and logs the newly created AcoustID straight into your application's database.

Setup guide

Set up AcoustID MCP in Windsurf

Prerequisites

Windsurf IDE installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Click the Cascade assistant icon in the sidebar, then click the hammer icon (🔨) at the top of the panel. Select "Configure" to open ~/.codeium/windsurf/mcp_config.json.
2

Add the AcoustID MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Refresh MCPs

Go back to the hammer icon (🔨) in Cascade and click "Refresh". Windsurf will detect the new server. No full restart is needed — the connection is hot-reloaded.
4

Verify in Cascade

Start a new Cascade conversation and ask something like "Show my AcoustID payment history." If connected, Cascade will call the AcoustID tools directly. You will see a green dot next to the server name in the MCP panel.

mcp_config.json

{
  "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 Windsurf

Open your `~/.codeium/windsurf/mcp_config.json` file and add the server endpoint. You can also use the Settings menu to navigate to the Cascade MCP Servers UI. Hit refresh in the MCP panel and Cascade will immediately see the new tools.

Yes, the `search_by_recording` tool handles text-based queries. Cascade passes the track name or artist to find matching recordings and their corresponding AcoustIDs before you even generate an audio fingerprint.

The lookup tool returns an array of matches along with confidence scores. Your agent evaluates those scores to pick the highest probability match or asks you how to handle ambiguous results.

Vinkius manages the server infrastructure, so your single endpoint token covers the access. The underlying database itself is an open-source project.

Only the mathematical Chromaprint strings and track durations leave your machine. Vinkius runs the server in an ephemeral V8 Isolate sandbox, meaning your raw audio files are never uploaded or stored.

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