Connector guide11-minute read29 MCP tools7 languages

Connect Reverb to Microsoft Copilot via MCP

Reverb API for sellers of music gear: own listings with draft, update and publish, orders and shipping with tracking, buyer messages, offers, refund requests, payouts and shop data. Personal access token.

HCBy HelpCode teamUpdated 11 min read Open-source on GitHub

No credit card · 7-day trial · Self-host alternative available

Reverb

Reverb

Reverb API for sellers of music gear: own listings with draft, update and publish, orders and shipping with tracking, buyer messages, offers, refund requests, payouts and shop data. Personal access token.

tools

29

Region

INTL

Category

E-commerce

Authentication

Bearer Token

Required env vars

REVERB_TOKEN
Install in one click on Cloud

7-day free trial · No credit card

  • 7-day free trial
    No credit card required
  • GDPR & SOC 2 ready
    EU data residency, audit logs
  • Open-source on GitHub
    Open source · AGPL-3.0
  • Works with ChatGPT, Claude, Gemini
    Any MCP-compatible client

Summary

Reverb API for sellers of music gear: own listings with draft, update and publish, orders and shipping with tracking, buyer messages, offers, refund requests, payouts and shop data. Personal access token.

Guided setup

Connect Reverb to Microsoft Copilot in 2 minutes

Start a free trial on AnythingMCP Cloud, connect Reverb 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

Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.

Reverb · live via MCP
Share
Opus 4.7

Claude is AI and can make mistakes. Please double-check responses.

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Reverb, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Reverb + Microsoft Copilot

Reverb API for sellers of music gear: own listings with draft, update and publish, orders and shipping with tracking, buyer messages, offers, refund requests, payouts and shop data. Personal access 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:

REVERB_TOKEN

Step 1 — Get credentials

Setting up takes about 3 minutes.

  1. Sign in at reverb.com, open your user menu and go to My Profile.
  2. Click the API & Integrations tab, then Generate New Token.
  3. Enter a name and tick the scopes: public, read_listings, write_listings, read_orders, write_orders, read_messages, write_messages, read_offers, write_offers, read_payouts and read_profile. A tool whose scope is missing is refused.
  4. Copy the token into REVERB_TOKEN. Personal access tokens do not expire.

Reverb asks every seller to have billing set up and at least one listing made by hand on reverb.com before using the API.

Where to start: reverb_list_orders_awaiting_shipment shows what has to be shipped. reverb_list_my_listings shows your live listings (state all adds drafts and ended ones); reverb_get_shop shows the shop and its shipping profiles.

Listings: create a draft with reverb_create_listing (category uuid from reverb_list_categories, condition uuid from reverb_list_listing_conditions, shipping profile id from reverb_get_shop), change it with reverb_update_listing, and put it on sale with reverb_publish_listing. reverb_list_my_drafts lists unpublished drafts and reverb_get_listing reads one listing. Find a listing by your SKU with reverb_list_my_listings and sku. Only the conditions Brand New, B-Stock and Mint with inventory can hold more than one unit; a used item is a single piece and cannot be relisted once sold. Setting inventory to 0 ends the listing. reverb_end_listing is installed switched off.

Orders: reverb_list_orders (all, filter by last change), reverb_list_orders_awaiting_shipment, reverb_get_order. Ship only when status is paid, with reverb_ship_order (provider from reverb_list_shipping_providers and the tracking number); local pickups are closed with reverb_mark_order_picked_up. Shipping labels are not bought through this connector.

Messages and offers: reverb_list_conversations, reverb_get_conversation and reverb_send_message handle buyer messages. reverb_list_offers and reverb_get_offer read offers on your listings; reverb_decline_offer turns one down. reverb_accept_offer and reverb_counter_offer are installed switched off, because both commit you to a price.

Refunds and payouts: reverb_list_refund_requests reads refund requests. reverb_respond_to_refund_request and reverb_create_refund_request are installed switched off: approving a refund credits the buyer and debits you at once. reverb_list_payouts and reverb_list_payout_line_items read what Reverb paid to your bank and the fees per order.

Formats: money is an object with amount (decimal string such as 95.00), amount_cents, currency and display; send amount and currency. Dates are ISO 8601 with an offset. Ids: orders use the order number, listings the numeric listing id, categories and conditions a uuid.

Paging and links: Reverb answers in HAL JSON. Lists carry _links.next and _links.prev; when next is missing you are on the last page. Use page and per_page to move. Each object also lists the actions open to it under _links.

Errors: 401 means the token is wrong or lacks the scope; 404 not found; 406 the action would break a rule of the current state; 412 a validation error with message and errors per field; 429 too many calls.

Rate limits: reads 2,000 per minute or 10,000 per 10 minutes; writes 600 per minute or 3,000 per 10 minutes. Avoid syncing the whole shop at once.

Sandbox: sandbox.reverb.com is a separate site with its own accounts and tokens; this connector calls the production API.

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 shows YOUR_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.

  1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
  2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
  3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
  4. 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.
  5. Try it in the agent's Test pane: ask for something that needs the Reverb tools.
  6. 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

ToolWhat it does
reverb_list_my_listingsList your own listings with their id, title, make, model, sku, condition, price (amount and currency), inventory and _links (the listing…
reverb_list_my_draftsList your draft listings (created but not yet published) with the same fields as reverb_list_my_listings: id, title, make, model, sku…
reverb_get_listingRead one listing by id with the fields a listing is created from: title, make, model, finish, year, description, condition, categories…
reverb_create_listingCreate a listing as a draft on your Reverb shop. It is not visible to buyers until reverb_publish_listing is called. Give at least a title…
reverb_update_listingUpdate one of your listings (draft or live): only the fields given change. Typical uses: price, inventory, description, photos, shipping…
reverb_publish_listingPublish a draft listing so buyers can see and buy it. The draft must be complete (make and model known, category, condition, price, photos…
reverb_end_listingEnd a live listing so it can no longer be bought. Reason not_sold simply takes it down. Reason reverb_sale says you found the buyer on…
reverb_list_ordersList the orders you sold, all statuses: order_number, status (unpaid, payment_pending, pending_review, blocked, paid, shipped, picked_up…
reverb_list_orders_awaiting_shipmentList paid orders that still have to be shipped, with the same fields as reverb_list_orders (order_number, title, quantity, buyer_name…
reverb_get_orderRead one sold order by its order number: order_number, status (unpaid, payment_pending, pending_review, blocked, paid, shipped, picked_up…
reverb_ship_orderMark a paid order as shipped with the carrier and the tracking number. With send_notification true Reverb emails the buyer that the item is…
reverb_mark_order_picked_upMark a local pickup order as picked up by the buyer (orders with shipping_method local). The order status becomes picked_up. Use it only…
reverb_list_shipping_providersList the shipping providers (carriers) Reverb accepts when an order is marked shipped. Use the provider name exactly as listed in…
reverb_list_conversationsList your message conversations on Reverb, each with its id (needed to read or answer it) and _links. With unread_only true only…
reverb_get_conversationRead one conversation in detail, with its messages in chronological order (oldest first), so the whole exchange with the buyer can be…
reverb_send_messageReply in an existing conversation. The other party receives the message on Reverb at once and it cannot be taken back, so write it as the…
reverb_list_offersList the active offers (Reverb calls them negotiations) buyers made on your listings, each with its id for reverb_get_offer and the answer…
reverb_get_offerRead the details of one offer (negotiation) by id: the listing it is on, the prices offered so far and its current state, with _links to…
reverb_decline_offerDecline a buyer's offer on one of your listings. The negotiation ends without a sale and the decline cannot be taken back; no price is…
reverb_accept_offerAccept a buyer's offer. This is binding: you agree to sell the item at the offered price and shipping price, and the buyer can pay at once.…
reverb_counter_offerAnswer a buyer's offer with a counter-offer: your price and, optionally, a shipping price. A counter-offer is binding if the buyer accepts…
reverb_list_refund_requestsList refund requests on your sales, by default the active ones (pending_seller_response and conditionally_approved): id, state, amount…
reverb_respond_to_refund_requestAnswer a refund request: conditionally_approved (you will refund once the item is back; the request stays open), approved (refund now…
reverb_create_refund_requestStart a refund on one of your sold orders as the seller, full or partial. It is created as conditionally approved; the money moves when the…
reverb_list_payoutsList the payouts Reverb sent to your bank account: per payout total (amount and currency), created_at, updated_at and _links.line_items…
reverb_list_payout_line_itemsList the lines of one payout, one per order: order_id, sale_date, sale_price, payout_currency and the fees taken (selling_fee…
reverb_get_shopRead your shop: id, name, description and shipping_profiles[] (id and name), whose ids go into shipping_profile_id of a listing. Shipping…
reverb_list_categoriesList all Reverb categories as one flat list with their uuid and name. The uuid is what the categories of a listing take. A long list; some…
reverb_list_listing_conditionsList the conditions your shop may use on listings (Non functioning, Poor, Fair, Good, Very Good, Excellent, Mint, B-Stock, Brand New): uuid…

Example prompts

  • "Which Reverb orders are awaiting shipment?"
  • "Draft a listing for my 2019 Gibson Les Paul Standard in Excellent condition at 2,200 USD."
  • "Which offers from buyers are open on my listings?"
  • "Ship order 12345678 with UPS tracking 1Z999AA10123456784."
  • "Show my payouts from the last month and their line items."

FAQ

Where do I get the token? On reverb.com: user menu, My Profile, API & Integrations, Generate New Token, with the listing, order, message, offer, payout and profile scopes. Personal access tokens do not expire. Reverb asks for billing and one listing made by hand before the API works.

What does it cover? Your own shop: listings from draft to publish, orders and shipping, buyer conversations, offers, refund requests, payouts and shop data. Searching the whole marketplace without a token is the Reverb Listings connector.

Which tools install switched off? reverb_end_listing, reverb_accept_offer, reverb_counter_offer, reverb_respond_to_refund_request and reverb_create_refund_request, because they sell, refund or end a listing. Switch them on on the connector page only if the AI should use them.

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?

Connect Reverb to Microsoft Copilot in 2 minutes

Start a free trial on AnythingMCP Cloud, connect Reverb in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.

Related guides

Connectors

Connect Reverb to ChatGPT via MCP: Orders and Payouts

Reverb API for sellers of music gear: own listings with draft, update and publish, orders and shipping with tracking, buyer messages, offers, refund requests, payouts and shop data. Personal access token.

Connectors

Connect Reverb to Claude via MCP: Listings and Orders

Reverb API for sellers of music gear: own listings with draft, update and publish, orders and shipping with tracking, buyer messages, offers, refund requests, payouts and shop data. Personal access token.

Connectors

Connect Reverb to Cursor via MCP: Listings and Orders

Reverb API for sellers of music gear: own listings with draft, update and publish, orders and shipping with tracking, buyer messages, offers, refund requests, payouts and shop data. Personal access token.

Connectors

Connect Reverb to Gemini CLI via MCP

Reverb API for sellers of music gear: own listings with draft, update and publish, orders and shipping with tracking, buyer messages, offers, refund requests, payouts and shop data. Personal access token.

Connectors

Connect Reverb to Meta Muse via MCP

Reverb API for sellers of music gear: own listings with draft, update and publish, orders and shipping with tracking, buyer messages, offers, refund requests, payouts and shop data. Personal access token.

Connectors

Reverb MCP Server: Listings, Orders and Payouts

Reverb API for sellers of music gear: own listings with draft, update and publish, orders and shipping with tracking, buyer messages, offers, refund requests, payouts and shop data. Personal access token.