4,000+ servers built on vurb.ts
Vinkius

Reverb MCP Server for CrewAIGive CrewAI instant access to 30 tools to Add To Sale, Bump Listing, Create Listing, and more

MCP Inspector GDPR Free for Subscribers

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

Ask AI about this MCP Server for CrewAI

The Reverb MCP Server for CrewAI is a standout in the Ecommerce category — giving your AI agent 30 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Reverb Specialist",
    goal="Help users interact with Reverb effectively",
    backstory=(
        "You are an expert at leveraging Reverb 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 Reverb "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 30 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Reverb
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 Reverb MCP Server

Connect your Reverb seller account to any AI agent to manage your musical gear marketplace operations through natural conversation.

When paired with CrewAI, Reverb becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Reverb 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

  • Listing Management — Create, update, publish, or end listings and manage drafts efficiently using create_listing and list_drafts.
  • Order Fulfillment — Retrieve orders, mark them as shipped or picked up, and track your seller sales with retrieve_orders and ship_order.
  • Financial Insights — Access payment methods, list payouts, and inspect specific payout line items via list_payouts.
  • Customer Engagement — List conversations, reply to buyers, and manage feedback received or sent using reply_to_conversation.
  • Shop Operations — Toggle vacation mode and check your shop's current status with get_vacation_status.

The Reverb MCP Server exposes 30 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 30 Reverb tools available for CrewAI

When CrewAI connects to Reverb through Vinkius, your AI agent gets direct access to every tool listed below — spanning marketplace, musical-instruments, order-fulfillment, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

add

Add to sale on Reverb

Add listings to a sale

bump

Bump listing on Reverb

Bump a listing

create

Create listing on Reverb

Requires a JSON payload matching Reverb listing schema. Create a new Reverb listing

delete

Delete draft on Reverb

Delete a draft listing

delete

Delete listing image on Reverb

Delete an image from a listing

disable

Disable vacation mode on Reverb

Disable vacation mode for the shop

enable

Enable vacation mode on Reverb

Enable vacation mode for the shop

end

End listing on Reverb

End an active Reverb listing

find

Find listings on Reverb

Can filter by SKU or state. Find seller listings

get

Get bump info on Reverb

Get bump info for a listing

get

Get feedback received on Reverb

Get received feedback

get

Get feedback sent on Reverb

Get sent feedback

get

Get listing images on Reverb

Find image IDs for a listing

get

Get order payment on Reverb

Get payment information for an order

get

Get payment methods on Reverb

Get eligible payment methods

get

Get payout line items on Reverb

Get line items for a payout

get

Get vacation status on Reverb

Get vacation mode status

leave

Leave feedback on Reverb

Leave feedback for a buyer

list

List conversations on Reverb

List messages and conversations

list

List drafts on Reverb

List all draft listings

list

List payouts on Reverb

List earnings payouts

mark

Mark order picked up on Reverb

Mark an order as picked up

publish

Publish listing on Reverb

Publish a draft Reverb listing

remove

Remove bump on Reverb

Remove a bump from a listing

remove

Remove from sale on Reverb

Remove listings from a sale

reply

Reply to conversation on Reverb

Reply to a conversation

retrieve

Retrieve orders on Reverb

Retrieve selling orders

ship

Ship order on Reverb

Mark an order as shipped

update

Update listing on Reverb

Update an existing Reverb listing

view

View seller sales on Reverb

View seller sales

Connect Reverb to CrewAI via MCP

Follow these steps to wire Reverb into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py. CrewAI auto-discovers 30 tools from Reverb

Why Use CrewAI with the Reverb MCP Server

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

01

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

02

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

03

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

04

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

Reverb + CrewAI Use Cases

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

01

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

02

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

03

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

04

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

Example Prompts for Reverb in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Reverb immediately.

01

"Find all my active listings with the SKU 'GUITAR-001'."

02

"Check if my shop is currently in vacation mode."

03

"List my recent payouts and their amounts."

Troubleshooting Reverb MCP Server with CrewAI

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

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Reverb + CrewAI FAQ

Common questions about integrating Reverb MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Explore More MCP Servers

View all →