Shopgoodwill MCP server

ShopGoodwill Auctions

Search active auctions, closed auctions with realized sale prices, and per-item detail from shopgoodwill.com — the online auction site run by Goodwill member organizations (170+ regional sellers listing cameras, jewelry, watches, art, electronics, instruments and collectibles).

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

The closed-auction search is the comps value: it returns what lots actually sold for (final hammer price and bid count), reaching back roughly 90 days.

Tools

Timestamps carry no timezone marker and are US Pacific (site convention).

Auth

None. The search and item-detail endpoints answer without credentials.

Data sources

(search, active and closed) and https://buyerapi.shopgoodwill.com/api/itemDetail/GetItemDetailModelByItemId/{id} (item detail) — the same JSON backend the shopgoodwill.com web app uses.

• ShopGoodwill buyer API: https://buyerapi.shopgoodwill.com/api/Search/ItemListing

scottmconway/shopgoodwill-scripts.

• Request shapes documented by the community client

Upstream quirks (measured 2026-09-05)

lowPrice/highPrice must be "0"/"999999"-style strings, never empty.

• A wrong or incomplete search body returns zero rows with a clean 200 —

100, get 40, no error); pagination is via page. The tools' per_page is applied client-side.

• pageSize is silently ignored — every page is exactly 40 rows (ask 5 or

closedAuctionDaysBack value requested.

• The closed-auction archive reaches back ~90 days regardless of the

• A nonexistent item id returns a 404 with an empty body.

Quick Start

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

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

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/shopgoodwill/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.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

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

Shortened. The full README is on GitHub.