How to Use the Freesound MCP in CrewAI

Q: Can a CrewAI team use this MCP server to both find and upload sounds to Freesound?

Yes. One agent can use searchsounds to ensure a sound doesn't already exist, and another agent can use uploadsound to contribute a new one. This prevents duplicates.

Q: How does an agent get information about a sound pack?

The agent just needs to call the getpack tool with the pack's ID number. It will get back all the pack's details, including the list of sounds it contains.

Deploy a CrewAI team to autonomously discover, analyze, and catalog audio assets from Freesound for your projects.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Freesound MCP to CrewAI

Create your Vinkius account to connect Freesound to CrewAI 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 Freesound with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

The Researcher & Librarian Crew

Assign a 'Researcher' agent the `search_sounds` tool. Its only job is to find potential audio clips based on a project brief. It passes a list of sound IDs to the next agent. A 'Librarian' agent takes that list of IDs. It uses `get_sound` to check each one's license, duration, and quality. If a sound meets the criteria, the Librarian approves it and passes the ID to the Downloader agent.

Build a Content Pipeline with CrewAI

This is perfect for a production pipeline. A 'Downloader' agent receives approved sound IDs and uses `download_sound` to fetch the high-quality files. A 'Tagger' agent could then take those files and use `describe_sound` to prepare them for another system. You can even have a 'Moderator' agent that uses `get_pending_uploads` to manage your own team's contributions to Freesound. This MCP server gives each agent a clear job.

Your Autonomous Sound Designer

Imagine a crew for sound design. The 'Scout' agent uses `get_user_sounds` and `get_pack` to find prolific creators or curated collections that match a certain style, like 'sci-fi UI sounds'. It passes these creators and packs to a 'Curator' agent, which analyzes the individual sounds and builds a final collection for a human designer to review. It's a powerful way to sift through Freesound's massive library.

Setup guide

Set up Freesound MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Freesound tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Freesound Analyst",
    goal="Access and analyze Freesound data via MCP.",
    backstory="Expert analyst with direct Freesound access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Freesound transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

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

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Freesound Analyst",
        goal="Access and analyze Freesound data via MCP.",
        backstory="Expert analyst with direct Freesound access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Freesound transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

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

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 Freesound. 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 Freesound 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 Freesound MCP in CrewAI

When you define your agents, you can pass a filtered list of tools to each one. Give your 'researcher' agent just `search_sounds` and your 'downloader' agent just `download_sound`. This enforces role separation.

Yes. One agent can use `search_sounds` to ensure a sound doesn't already exist, and another agent can use `upload_sound` to contribute a new one. This prevents duplicates.

You pass the MCP server URL, which includes your Vinkius token, directly into your CrewAI agent definitions. Vinkius handles the connection and authentication, so your agents just need to focus on their tasks.

The agent just needs to call the `get_pack` tool with the pack's ID number. It will get back all the pack's details, including the list of sounds it contains.

All data, including sound files and user metadata, is handled within temporary, single-use environments on Vinkius. Nothing is logged or stored. Your Freesound credentials are not exposed to the MCP server; it only uses the Vinkius-provided token for access.

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