mcpField
S
shopdata

shopdata

Local
github.com/CloudCorpRecordsBusiness & Marketing0Updated 3d ago

About shopdata

shopdata is a local bridge to the HasData Amazon MCP server, returning public Amazon data as JSON. It retrieves products and reviews by ASIN, searches by keyword, and provides seller profiles and catalogues.

Key features

  1. 01Fetch product details by ASIN
  2. 02Retrieve paginated customer reviews
  3. 03Search Amazon by keyword
  4. 04Look up seller storefront profiles
  5. 05Browse seller product catalogues

Use cases

  1. 01Check product details and other-seller offers
  2. 02Filter reviews by rating or search term
  3. 03Compare results for different search terms
  4. 04Inspect seller profiles and listed products

MCP support

It exposes HasData Amazon tools as an MCP server and forwards calls to the upstream service. The tools are read-only and include no purchase, checkout, or account operations.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"cloudcorprecords-shopdata": {
"command": "npx",
"args": [
"-y",
"@reneturcios/shopdata"
]
}
}
}
Run commandnpx -y @reneturcios/shopdata

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@reneturcios/shopdata0.1.0
ocighcr.io/cloudcorprecords/shopdata:0.1.0

Tools

5

Saved tool list · updated 2d ago

ParameterTypeRequiredDescription
asinstringYesThe Amazon Standard Identification Number (ASIN) of the product.
domainenumNoAmazon domain to use. Default is www.amazon.com.www.amazon.com | www.amazon.de | www.amazon.co.uk | www.amazon.ae | www.amazon.com.au | www.amazon.com.be | www.amazon.com.br | www.amazon.ca | www.amazon.eg | www.amazon.es | www.amazon.fr | www.amazon.ie | www.amazon.in | www.amazon.it | www.amazon.co.jp | www.amazon.com.mx | www.amazon.nl | www.amazon.pl | www.amazon.sa | www.amazon.se | www.amazon.sg | www.amazon.com.tr | www.amazon.co.za
languageenumNoOptional Amazon language code. Supported values depend on the selected domain.AR | BN | CS | DA | DE | EN | ES | FR | HI | IT | JP | KN | ML | MR | NL | PL | PT | SV | TA | TE | TR | ZH
deliveryZipstringNoPostal code of the delivery location.
otherSellersbooleanNoAlso collect the offers of other sellers competing for this item. This takes an extra request to Amazon and costs 5 credits on top of the base. Default is false.
shippingLocationstringNoThe two-letter country code to define the country of the delivery address. Provide one exact documented value (238 allowed), e.g. `AU`, `CA`.

Details

From the project README

shopdata

shopdata is a small local bridge to the hosted HasData Amazon MCP server, which returns public Amazon data as JSON. Give it an ASIN and it fetches that product's details or its customer reviews; give it a keyword and it runs a search on a chosen Amazon domain; give it a seller ID and it returns the seller's public storefront profile or the catalogue that seller offers.

The bridge keeps no Amazon data of its own. It serves the upstream server's tool list locally, exactly as captured from the live endpoint, and forwards each tool call upstream, returning the result untouched. The captured surface is read-only: there is no purchase, checkout, or account tool in it.

Tools

  • hasdata_amazon_product_getProductDetails — fetch one product page by ASIN. Required: asin. Optional: domain, language, deliveryZip, shippingLocation, otherSellers (also collect the other-sellers offers block).
  • hasdata_amazon_reviews_getProductReviews — paginated customer reviews for an ASIN. Required: asin. Optional: domain, language, page, searchTerm, reviewerType, stars, format, mediaType, sortBy.
  • hasdata_amazon_search_getSearchResults — keyword search on a chosen Amazon domain. Required: q. Optional: domain, language, page, deliveryZip, shippingLocation, sortBy.
  • hasdata_amazon_seller_getSellerDetails — public storefront profile for a seller. Required: sellerId. Optional: domain, language.
  • hasdata_amazon_seller_products_getSellerProducts — paginated catalogue offered by a seller. Required: sellerId. Optional: domain, language, page.

Configuration

  • HASDATA_AMAZON_MCP_URL (optional) — override the upstream endpoint. Defaults to https://mcp.hasdata.com/mcp?apis=amazon, query string included. (The override hook is this rebuild's own labelled reconstruction.)
  • HASDATA_API_KEY (optional) — when set, every upstream request carries an x-api-key: <key> header with the caller's own HasData API key. When it is not set, no key header is sent, and no Authorization header is sent in either case. (The env and header names are pinned by the original's registry record; forwarding the key from this env var is a labelled reconstruction — the original surface was captured keyless.)
Forwarding mechanics

On the first tool call the client opens a streamable HTTP session with the upstream: a JSON-RPC initialize request (protocolVersion 2025-03-26, clientInfo name shopdata), then a notifications/initialized notification, then the tools/call request carrying the caller's arguments unchanged. When the upstream answers initialize with an Mcp-Session-Id header, that value rides on every later request of the session, which is reused for the life of the process. Replies may arrive as plain JSON or as server-sent events; both are read.

Successful upstream results pass through verbatim, including any isError flag the upstream sets. Failures — a JSON-RPC error, a non-2xx status, an unreadable response, or a request that cannot be completed — come back as an isError result whose text starts with shopdata error: (this rendering is this rebuild's own labelled reconstruction).

CLI

Each tool is also a subcommand taking one JSON argument string:

npx @reneturcios/shopdata hasdata_amazon_product_getProductDetails '{"asin":"B07FZ8S74R"}'
npx @reneturcios/shopdata hasdata_amazon_search_getSearchResults '{"q":"noise cancelling headphones","sortBy":"priceLowToHigh"}'
npx @reneturcios/shopdata --version

Exit codes: 0 on success, 1 on an isError result, 2 on a usage error.

MCP server

npx -y @reneturcios/shopdata mcp

MCP client config:

{
  "mcpServers": {
    "shopdata": {
      "command": "npx",
      "args": ["-y", "@reneturcios/shopdata", "mcp"]
    }
  }
}

Docker

docker run -i ghcr.io/cloudcorprecords/shopdata
docker run --rm ghcr.io/cloudcorprecords/shopdata --version

The container's default command is mcp, so the first form is a stdio MCP server; any other arguments reach the CLI normally.

Development

npm install
npm run build
npm test
npm run dev

The test suite runs entirely against a stubbed JSON-RPC upstream — no live network calls.

License

MIT — see LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.