E-commerce Sales Signals MCP: Amazon bestsellers, eBay sold prices, TikTok Shop, Etsy shop sales
What is actually selling, as MCP tools: Amazon Best Sellers ranks, Amazon reviews, confirmed eBay sold prices, TikTok Shop sales estimates and Etsy shop sales counters, in one hosted bundle. One Actor per sales signal.
Hosted remote MCP server (Streamable HTTP) on Apify's MCP gateway. Client config plus a small open-source stdio proxy server. No Actor source.
Disclosure: entries marked "(maintained by us)" are Actors I maintain on Apify Store (publisher publicrecords). Every other Actor is independent, made by its own publisher and picked on merit (Store usage, ratings and recent maintenance). This repo is not affiliated with those publishers or with the sites the Actors read.
MCP endpoint
Auth: sign in with Apify (OAuth) when your client prompts, or send an Apify API token as a Bearer token. Runs are billed on your own Apify account under each Actor's own Store pricing; see each Store page.
Tools
The Apify gateway also exposes helper tools to read run results (get-actor-run, get-dataset-items). Want fewer tools? Drop any Actor from the tools= list.
Who it's for
- Product research: which items are selling now, by marketplace?
- Resellers: what did this item actually sell for on eBay recently?
- Brands and agencies: how fast are a competitor's reviews or shop sales growing?
- Analysts: track bestseller ranks and sales counters over time.
Example prompts
- List today's top 20 Amazon Best Sellers in
<category> with prices.
- What did
<item> sell for on eBay in the last 30 days? Give min, median and max.
- How many sales did these Etsy shops show today:
<shop1>, <shop2>? Read again next week and give the difference.
- Which TikTok Shop products in
<category> have the highest sales estimates?
Cursor / Claude Code / any remote-MCP client
Claude Code:
Claude Desktop (local bridge)
Local stdio server (open source)
This repo also ships a small MCP server in src/ for clients that only run local stdio servers. It answers initialize and tools/list locally from tools.json, which is generated from each Actor's public input schema and checked for drift in CI and weekly, so any client or directory can inspect the tools with no token. tools/call is forwarded to the hosted Apify MCP endpoint above with your own APIFY_TOKEN; without a token a call returns a clear error instead of running anything. The token is only sent in the Authorization header and is never logged.
Or from a clone:
Optional env: APIFY_ACTORS (comma-separated subset of the Actors above) and APIFY_MCP_URL (full endpoint override).
Tests run against an in-memory mock server, with no network and no token: npm test. Requires Node.js 18+.
Python (uvx/pip)
A matching Python version of this server lives in python/, built on the official mcp Python SDK: same tools, same APIFY_TOKEN, same hosted endpoint. Requires Python 3.10+.
Or with pip: pip install ecommerce-sales-mcp, then run ecommerce-sales-mcp. Python tests: cd python && pip install -e ".[test]" && env -u APIFY_TOKEN python -m pytest.
See also
Registry
Official MCP Registry name: io.github.GeminiGeorge22/ecommerce-sales-mcp
License
MIT, for this documentation, config and the proxy server code in src/. Each Actor belongs to its publisher.
