Compatible with every major AI agent and IDE
What is the Reverb MCP Server?
Connect your Reverb seller account to any AI agent to manage your musical gear marketplace operations through natural conversation.
What you can do
- Listing Management — Create, update, publish, or end listings and manage drafts efficiently using
create_listingandlist_drafts. - Order Fulfillment — Retrieve orders, mark them as shipped or picked up, and track your seller sales with
retrieve_ordersandship_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.
How it works
- Subscribe to this server
- Enter your Reverb Personal Access Token
- Start managing your gear shop from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Gear Sellers — quickly update prices or end listings without navigating the web interface
- Shop Managers — handle customer inquiries and order shipping statuses directly from your workflow
- Power Users — automate reporting on payouts and sales performance
Built-in capabilities (30)
Add listings to a sale
Bump a listing
Requires a JSON payload matching Reverb listing schema. Create a new Reverb listing
Delete a draft listing
Delete an image from a listing
Disable vacation mode for the shop
Enable vacation mode for the shop
End an active Reverb listing
Can filter by SKU or state. Find seller listings
Get bump info for a listing
Get received feedback
Get sent feedback
Find image IDs for a listing
Get payment information for an order
Get eligible payment methods
Get line items for a payout
Get vacation mode status
Leave feedback for a buyer
List messages and conversations
List all draft listings
List earnings payouts
Mark an order as picked up
Publish a draft Reverb listing
Remove a bump from a listing
Remove listings from a sale
Reply to a conversation
Retrieve selling orders
Mark an order as shipped
Update an existing Reverb listing
View seller sales
Why VS Code Copilot?
GitHub Copilot Agent mode brings Reverb data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 30 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
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
Reverb in VS Code Copilot
Reverb and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Reverb to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Reverb in VS Code Copilot
The Reverb 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. All 30 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* 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
How Vinkius secures
Reverb for VS Code Copilot
Every tool call from VS Code Copilot to the Reverb MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see my unpublished listings or drafts?
Yes, you can use the list_drafts tool to retrieve all listings that are currently in draft state but not yet live on the marketplace.
How do I update the shipping status of a sold item?
Use the ship_order tool. You will need to provide the order ID and relevant shipping details to mark the transaction as fulfilled.
Is it possible to reply to buyer messages directly?
Absolutely. Use list_conversations to find the thread and reply_to_conversation to send your message back to the buyer.
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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
OpenSea
35 toolsAccess the world's leading NFT marketplace — query collections, track floor prices, inspect NFT metadata, and monitor wallet balances across multiple chains.

Illumidesk
10 toolsManage campuses, courses, and users via Illumidesk LMS API.

ANP (Revendedores de Combustíveis)
2 toolsAccess official Brazilian fuel and LPG reseller data from ANP — query gas stations and cooking gas providers by location or CNPJ.

Universities List
1 toolsGlobal university database — search higher education institutions by name and country via AI.
