Bonanza MCP server

@pipeworx/bonanza

Search Bonanza marketplace listings via the "Bonapitit" API (api.bonanza.com/docs) — an eBay-Trading-API-compatible read/write API. Orders are seller-scoped on this API (need a logged-in user's auth token), so this pack is search + item detail only. No sold-price data.

Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.

Tools

keyword search (findItemsByKeywords).

• bonanzasearch(keywords, entriesperpage?, pagenumber?, sort_order?) —

— category browse (findItemsByCategory).

• bonanzasearchbycategory(categoryid, entriesperpage?, page_number?)

• bonanzagetitem(item_id) — single listing detail (getSingleItem).

Auth

BYO key only (apiKey), requires an API key. Register a free devID/certID at — a business-identity account with a ~1-2 day manual approval. Pass ?apiKey= or : (colon-joined; certID is accepted but unused by these three read calls).

BYO is the settled posture, not a stopgap: the platform-registration question was ruled on 2026-09-06 (fleet #1278) — Pipeworx will not fund or register a platform devID, so callers always bring their own. A keyless call refuses with "requires an API key" and points at the registration URL. Note the request shape has not been verified against a live response (see Data sources) — the first caller with a real devID exercises it live.

Data sources

client-rendered SPA; the actual wire format (base URL, headers, body encoding) is NOT visible in the static HTML and had to be reconstructed from the open-source PHP SDK: .

• — Bonapitit reference. The docs site is a

Traps for the next person:

every call below (secure/write calls use secure_request instead and also need a user auth token — out of scope here).

• Base URL is https://api.bonanza.com/apirequests/standardrequest for

field: the call name (lower-camel, e.g. findItemsByKeywords) whose value is the JSON-serialized request object. This is not a JSON body and not a REST-ish query string — easy to get wrong.

• The request body is application/x-www-form-urlencoded with exactly ONE

(Bonanza's old internal name, "Bonanzle") — not X-BONANZA-*.

• Auth headers are X-BONANZLE-API-DEV-NAME / X-BONANZLE-API-CERT-NAME

Registering an account needs a password and business details Bruce has to enter himself; until that key exists, treat the exact response field names as unverified against the community SDK/docs, not against a real payload.

• This pack has never been called against a live Bonanza response.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "bonanza": {
      "url": "https://gateway.pipeworx.io/bonanza/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/bonanza/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Shortened. The full README is on GitHub.