Etsy MCP server

@pipeworx/etsy

Search active Etsy listings via the Etsy Open API v3 — scoped to the three endpoints that authenticate with just an API key (no OAuth user token).

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

Tools

— site-wide active-listing search (findAllListingsActive).

• etsysearchlistings(keywords?, limit?, offset?, sorton?, sortorder?, minprice?, maxprice?, taxonomyid?, buyercountry?)

— active listings within one shop (findAllActiveListingsByShop).

• etsysearchshoplistings(shopid, keywords?, limit?, offset?, sorton?, sortorder?)

• etsygetlisting(listing_id) — one listing by ID (getListing).

No sold-price / comps data — Etsy's v3 API has none. Active listings only.

Auth

BYO key only (apiKey), requires an API key. Register a free app at to get a keystring + shared secret. Pass ?apiKey=; the colon-joined : form your "Your Apps" page displays is accepted too, and the pack handles the difference for you (see the trap below).

Etsy's v3 reference marks each endpoint's required auth. Only the three endpoints above are api_key-only; everything else (shop/receipt/user management, listing writes) requires an OAuth user token issued through Etsy's manual commercial-review flow — out of scope for this pack. If Etsy's review later grants broader access, extend this pack rather than building a second one.

Registering an Etsy developer account requires signing in with (or creating) an Etsy account and a password — a human step this pack's author cannot perform on Bruce's behalf. See the open Needs Bruce item for platform-key registration; this pack ships BYOK-gated in the meantime and its own live call has not yet been verified against a real key.

Data sources

Base URL https://openapi.etsy.com/v3/application.

• — Etsy Open API v3.

Traps for the next person:

cannot resolve it by experiment. The apikey reference for these three endpoints documents the bare keystring; the quickstart shows the colon-joined keystring:sharedsecret pair (which is really the Basic-auth credential for the OAuth token endpoint). An app awaiting Etsy's Personal Approval returns a 403 that is byte-identical* to the 403 a fabricated key returns — verified with a negative control on 2026-09-09 (fleet #1279) — so no probe before activation can tell the two header forms apart. The pack therefore sends the keystring and, only on a 403, retries once with the raw value the caller passed. Don't "simplify" that back to one call until a live successful response says which form won.

• **Etsy contradicts itself about the x-api-key header value, and you

results plus a source field) rather than re-mapping field names, since the exact Listing resource shape was only checked against the published OpenAPI reference, not a live authenticated response (no working key was available at build time — see Auth above).

• This pack returns Etsy's response JSON close to verbatim (count +

Quick Start

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

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

What this endpoint actually serves

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

Shortened. The full README is on GitHub.