How to Use the AcoustID MCP in VS Code Copilot

Q: How does VS Code Copilot share AcoustID configuration across a team?

You save the AcoustID MCP Server configuration in .vscode/mcp.json and push it to your git repository. Every developer opening the project in VS Code can immediately use the tools.

Equip your engineering team to query AcoustID metadata and verify audio fingerprints inside VS Code Copilot with this MCP Server.

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 VS Code Copilot

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Share AcoustID tooling across your VS Code Copilot team

Your team can ask VS Code Copilot to run `lookup_by_fingerprint` to test audio parsing logic directly in your editor. Commit your configuration to `.vscode/mcp.json` so every developer on your team instantly gains access to the AcoustID registry. This shared setup ensures everyone uses the same endpoint token and environment variables. Developers can identify test audio files and verify API responses using our team-wide MCP config.

Automate MusicBrainz mapping in VS Code Copilot

Your VS Code Copilot agent uses `search_by_mbid` to locate all AcoustID fingerprints linked to specific MusicBrainz recordings. It then updates your database schema or seed files directly inside the editor. By running `get_recording_metadata`, the agent ensures your release group data matches the official registry before you commit your code.

Verify audio metadata during code reviews

To verify audio metadata during code reviews, VS Code Copilot runs `search_by_recording` on the tracks defined in your test suite. This prevents broken API calls from reaching production. It also allows you to run `submit_fingerprint` directly from the chat to add missing test assets to the registry during debugging.

Setup guide

Set up AcoustID MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the AcoustID MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the AcoustID tools listed. Try asking: "List my recent AcoustID transactions" and Copilot will invoke them automatically.

.vscode/mcp.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 VS Code Copilot

You save the AcoustID MCP Server configuration in `.vscode/mcp.json` and push it to your git repository. Every developer opening the project in VS Code can immediately use the tools.

Yes, by passing a Chromaprint string to VS Code Copilot, the agent calls `lookup_by_fingerprint` to retrieve the artist, track title, and matching MusicBrainz IDs.

The agent runs lookups sequentially. For large libraries, you can ask Copilot to write a script that loops through your files and calls `get_recording_metadata` for each AcoustID.

You can store your AcoustID credentials in your local environment variables. The configuration file references these variables, keeping your production keys out of git.

Yes, the server only transmits the mathematical Chromaprint string and duration to the AcoustID API. Your source audio files never leave your secure local environment, and the Vinkius MCP sandbox ensures zero data retention.

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