2,500+ MCP servers ready to use
Vinkius

AcoustID MCP Server for LlamaIndex 5 tools — connect in under 2 minutes

Built by Vinkius GDPR 5 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add AcoustID as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to AcoustID. "
            "You have 5 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in AcoustID?"
    )
    print(response)

asyncio.run(main())
AcoustID
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.

LlamaIndex agents combine AcoustID tool responses with indexed documents for comprehensive, grounded answers. Connect 5 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

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

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

01

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.py and run: python agent.py

04

Explore tools

The agent discovers 5 tools from AcoustID

Why Use LlamaIndex with the AcoustID MCP Server

LlamaIndex provides unique advantages when paired with AcoustID through the Model Context Protocol.

01

Data-first architecture: LlamaIndex agents combine AcoustID tool responses with indexed documents for comprehensive, grounded answers

02

Query pipeline framework lets you chain AcoustID tool calls with transformations, filters, and re-rankers in a typed pipeline

03

Multi-source reasoning: agents can query AcoustID, a vector store, and a SQL database in a single turn and synthesize results

04

Observability integrations show exactly what AcoustID tools were called, what data was returned, and how it influenced the final answer

AcoustID + LlamaIndex Use Cases

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

01

Hybrid search: combine AcoustID real-time data with embedded document indexes for answers that are both current and comprehensive

02

Data enrichment: query AcoustID to augment indexed data with live information before generating user-facing responses

03

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying AcoustID for fresh data

04

Analytical workflows: chain AcoustID queries with LlamaIndex's data connectors to build multi-source analytical reports

AcoustID MCP Tools for LlamaIndex (5)

These 5 tools become available when you connect AcoustID to LlamaIndex via MCP:

01

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

02

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

03

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

04

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

05

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 LlamaIndex

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

01

"Search for 'Bohemian Rhapsody' by Queen."

02

"Search recordings by Daft Punk."

03

"Get metadata for AcoustID 0e5e5b5e-."

Troubleshooting AcoustID MCP Server with LlamaIndex

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

01

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

AcoustID + LlamaIndex FAQ

Common questions about integrating AcoustID MCP Server with LlamaIndex.

01

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
02

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query AcoustID tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
03

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

Connect AcoustID to LlamaIndex

Get your token, paste the configuration, and start using 5 tools in under 2 minutes. No API key management needed.