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 CrewAI 5 tools — connect in under 2 minutes

Name: AcoustID
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 5 Tools Framework

Connect your CrewAI agents to AcoustID through Vinkius, pass the Edge URL in the `mcps` parameter and every AcoustID tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

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.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="AcoustID Specialist",
    goal="Help users interact with AcoustID effectively",
    backstory=(
        "You are an expert at leveraging AcoustID tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in AcoustID "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 5 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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.

When paired with CrewAI, AcoustID becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call AcoustID tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

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 CrewAI 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 CrewAI via MCP

Follow these steps to integrate the AcoustID MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 5 tools from AcoustID

Why Use CrewAI with the AcoustID MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with AcoustID through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

AcoustID + CrewAI Use Cases

Practical scenarios where CrewAI combined with the AcoustID MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries AcoustID for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries AcoustID, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain AcoustID tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries AcoustID against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

AcoustID MCP Tools for CrewAI (5)

These 5 tools become available when you connect AcoustID to CrewAI 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 CrewAI

Ready-to-use prompts you can give your CrewAI 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 CrewAI

Common issues when connecting AcoustID to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

AcoustID + CrewAI FAQ

Common questions about integrating AcoustID MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.