Do I need an API key?

No! AcoustID's public API works without authentication using a default client key for basic lookups.

How does audio fingerprinting work?

AcoustID uses Chromaprint (fpcalc) to generate a fingerprint from audio. This fingerprint is matched against the database to identify the song. You need to run fpcalc on an audio file to get the fingerprint string.

MusicBrainz is an open music encyclopedia that collects music metadata. AcoustID links audio fingerprints to MusicBrainz recordings, enabling song identification through the MusicBrainz ID (MBID).

AcoustID MCP Server for VS Code Copilot 5 tools — connect in under 2 minutes

Name: AcoustID
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 5 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install AcoustID and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About AcoustID MCP Server

Connect to AcoustID and identify music from audio fingerprints through natural conversation — no API key needed for basic use.

GitHub Copilot Agent mode brings AcoustID data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 5 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Song Identification — Identify songs from audio fingerprints (like Shazam)
Recording Search — Search for recordings by name, artist or MusicBrainz ID
MBID Lookup — Find all AcoustIDs linked to a MusicBrainz recording
Metadata Lookup — Get full metadata for recordings including artists and release groups
Fingerprint Submission — Submit new audio fingerprints to expand the database

The AcoustID MCP Server exposes 5 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect AcoustID to VS Code Copilot via MCP

Follow these steps to integrate the AcoustID MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using AcoustID

Ask Copilot: "Using AcoustID, help me...". 5 tools available

Why Use VS Code Copilot with the AcoustID MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with AcoustID through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

AcoustID + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the AcoustID MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

AcoustID MCP Tools for VS Code Copilot (5)

These 5 tools become available when you connect AcoustID to VS Code Copilot via MCP:

get_recording_metadata

Returns all associated MusicBrainz recordings, artists, release groups and fingerprints linked to this AcoustID. Get full metadata for a recording by AcoustID

lookup_by_fingerprint

Returns matching recordings from the AcoustID database with song titles, artists, MusicBrainz IDs and match confidence scores. Requires the fingerprint string and audio duration in seconds. Use meta="recordings" for full recording details. Identify a song by audio fingerprint

search_by_mbid

Returns all AcoustID fingerprints linked to that MusicBrainz recording, useful for finding multiple audio fingerprints of the same song. Search for AcoustIDs by MusicBrainz ID

search_by_recording

Returns matching recordings with AcoustID, MusicBrainz ID, title and artist name. Useful for finding the AcoustID of a known song. Search for recordings by name and/or artist

submit_fingerprint

Requires the Chromaprint fingerprint string and audio duration. Optionally include recording name and artist for new songs. Returns the newly created AcoustID. Submit an audio fingerprint to AcoustID

Example Prompts for AcoustID in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with AcoustID immediately.

"Search for 'Bohemian Rhapsody' by Queen."

"Search recordings by Daft Punk."

"Get metadata for AcoustID 0e5e5b5e-."

Troubleshooting AcoustID MCP Server with VS Code Copilot

Common issues when connecting AcoustID to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

AcoustID + VS Code Copilot FAQ

Common questions about integrating AcoustID MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.