Summary
Search what is for sale on Reverb, the marketplace for new, used and vintage music gear, from Claude, ChatGPT or Copilot: listings by text, make, condition, price, year, category and country, listing details with shipping and return terms, categories, and shops with their listings. Read-only, no account or token.
Guided setup
Connect Reverb Listings to Microsoft Copilot in 2 minutes
Start a free trial on AnythingMCP Cloud, connect Reverb Listings in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for Reverb Listings
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Reverb Listings, install it, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
Reverb Listings + Microsoft Copilot
Search what is for sale on Reverb, the marketplace for new, used and vintage music gear, from Claude, ChatGPT or Copilot: listings by text, make, condition, price, year, category and country, listing details with shipping and return terms, categories, and shops with their listings. Read-only, no account or token.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
None. This connector needs no account, API key or sign-in.
Step 1 — Get credentials
Setup: nothing to enter. Install the connector and it works. The calls are sent without a token, with the headers Reverb asks for (Accept: application/hal+json, Accept-Version: 3.0 and a User-Agent).
Where to start: reverb_listings_search_listings with a query ("fender telecaster", "sm57") and the filters that fit: make, condition (new or used), price_min and price_max, year_min and year_max, item_region (where the item is) and ships_to (where it can be sent). The answer's humanized_params repeats in words how Reverb understood the search: check it when the results look off. reverb_listings_get_listing then gives the full description, shipping and return terms of one listing.
Categories: reverb_listings_list_categories returns every category with its uuid; pass one as category_uuid to the search ("Acoustic Guitars / 12-String", "Effects and Pedals / Delay").
Shops: every listing names its shop (shop.slug). reverb_listings_get_shop reads its profile, rating and policies; reverb_listings_list_shop_listings lists what it has for sale.
Field notes:
- Prices are objects with
amountas a decimal string ("274.80"),amount_cents,currencyand a ready-to-showdisplay.priceis the listing price andbuyer_pricewhat the buyer pays. They come in USD unlessdisplay_currencyasks for another currency;listing_currencyis the currency the seller listed in. condition.display_nameis the grade of the item (Brand New, Mint, Excellent, Very Good, Good, Fair, Poor, Non Functioning). Theconditionfilter only tells new from used.- Results are paged, and Reverb stops at page 50 of a search however many listings match (
totalcan be far higher). Narrow the search instead of paging deep. yearis free text typed by the seller ("1978", "2009 - 2010", or empty).descriptionin a listing is HTML.- Give the user the
_links.web.hrefof a listing: that is its page on reverb.com. - Rate limit: Reverb documents 2,000 read requests per minute and 10,000 per 10 minutes per application, and answers 429 beyond that. It publishes no separate terms for calls without a token.
- The price guide is not offered: Reverb answers that this endpoint is no longer publicly available.
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Microsoft Copilot
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
- Try it in the agent's Test pane: ask for something that needs the
Reverb Listingstools. - Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.
Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.
Available tools
| Tool | What it does |
|---|---|
reverb_listings_search_listings | Search the public listings on Reverb, the marketplace for new, used and vintage music gear. Combine a free-text query with filters: make… |
reverb_listings_get_listing | Read one Reverb listing by its numeric id (the id of a search result): title, make, model, year, finish, the full description as HTML… |
reverb_listings_list_categories | List every Reverb product category as a flat list (about 320 entries): uuid, full_name with its parent (for example "Acoustic Guitars /… |
reverb_listings_get_shop | Read the public profile of a Reverb shop by its slug (the shop.slug of a listing, or the last part of a reverb.com/shop/ address): name… |
reverb_listings_list_shop_listings | List the live listings of one Reverb shop by its slug, optionally narrowed by a text query or a price range. Returns the same fields as the… |
Example prompts
- "Find used Fender Telecasters from the 1970s under 5,000 USD that ship to Germany."
- "What do Shure SM57 microphones in Excellent condition cost on Reverb right now?"
- "Show the shipping and return terms of this listing."
- "Which delay pedals are listed under 150 USD in the US?"
- "Who is the shop behind this listing, and what else does it sell?"
FAQ
Do I need a Reverb account or token? No. The connector reads the public side of the Reverb API without a token.
What is the difference to the Reverb connector? Reverb Listings searches what anyone has for sale. The Reverb connector manages your own shop (listings, orders, messages, offers, payouts) with your personal access token.
Can it buy or make offers? No. It searches listings, reads a listing with its shipping and return terms, lists categories and reads shops. Nothing installs switched off because there is nothing to switch: it cannot buy, make offers or see orders.
Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.
What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.
The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.
Next steps
Was this guide helpful?