npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

amazon-scraper-api-mcp

v0.1.3

Published

MCP (Model Context Protocol) server for Amazon Scraper API - drop into Claude Desktop, Cursor, or any MCP client

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

chocodatachocodata

Keywords

mcpmodel-context-protocolamazonscraperclaudecursorai

Readme

amazon-scraper-api-mcp

npm npm downloads license

MCP (Model Context Protocol) server for Amazon Scraper API. Plugs into Claude Desktop, Cursor, Claude Code, Continue, or any MCP-compatible AI client. Gives your model live Amazon product data as a first-class tool call.

What it unlocks

"Find me the highest-rated wireless earbuds under $150 on amazon.com, then check if they're cheaper on amazon.de"

That's one prompt. Without MCP, your AI can't fetch Amazon pages (Amazon blocks LLM browsing) and has zero recency for prices and stock. With this MCP server, it calls amazon_search + amazon_product directly and comes back with structured data from Amazon Scraper API.

Tools exposed

| Tool | What it does | Typical use | |---|---|---| | amazon_product | Fetch one product by ASIN or URL | "get price + rating for B09HN3Q81F" | | amazon_search | Keyword search with sort/filter | "top 10 cast iron skillets under $50" | | amazon_batch_create | Queue up to 1000 ASINs for async scrape | "scrape all 500 products in my catalog, webhook me when done" | | amazon_batch_status | Poll a batch's progress | "how much of batch xyz is done?" |

Each returns structured JSON: title, price, rating, reviews count, availability, buybox, variants, images, bullets, categories, spec tables.

Benchmark (live production, 2026-04)

| Metric | Value | |---|---| | Median latency (product, US) | ~2.6 s | | P95 latency | ~6 s | | Price / 1,000 requests | $0.50 flat | | Marketplaces | 20+ |

Claude Desktop setup

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "amazon-scraper": {
      "command": "npx",
      "args": ["-y", "amazon-scraper-api-mcp"],
      "env": {
        "ASA_API_KEY": "asa_live_..."
      }
    }
  }
}

Restart Claude Desktop. Tools appear under the MCP icon in the chat composer.

Cursor setup

Settings → MCP → Add server:

  • Command: npx -y amazon-scraper-api-mcp
  • Env: ASA_API_KEY=asa_live_...

Claude Code setup

claude mcp add amazon-scraper -- npx -y amazon-scraper-api-mcp
# then set ASA_API_KEY in the environment Claude Code runs in

Example conversation (Claude Desktop)

You: What's the current price of AirPods Pro 3rd gen on amazon.com?

Claude: [calls amazon_product with ASIN B09HN3Q81F]

The AirPods Pro 3rd gen are currently $199.00 on amazon.com, down from $249.00 (20% off). They have a 4.7-star rating from 58,214 reviews and are in stock, shipping from and sold by Amazon.com with Prime.

You: Compare that to the German Amazon listing.

Claude: [calls amazon_product with query=B09HN3Q81F, domain=de]

On amazon.de the same product is listed at 229.00 EUR. At today's exchange rate that's about $245, roughly 23% more than the US price. German listing ships from Amazon and qualifies for Prime delivery.

Why this vs. a generic "browse the web" MCP

Generic browser tools that try to load amazon.com typically get blocked (robot check) or serve a mobile-stripped page. This server routes every call through Amazon Scraper API, which:

  • Detects and retries robot/CAPTCHA pages through escalating proxy tiers
  • Returns structured JSON (typed fields), not HTML soup
  • Supports 20+ marketplaces with country-matched residential IPs
  • Handles batch (hundreds to thousands of ASINs) with webhook delivery
  • Built-in rate-limit backoff

Error handling

Errors are surfaced to the model as tool errors with a code field and a hint. The model then decides whether to retry or abandon the sub-task. You don't have to write error-handling logic yourself.

Common codes: INVALID_API_KEY, INSUFFICIENT_CREDITS, RATE_LIMITED, target_unreachable, amazon-robot-or-human, extraction_failed, SERVICE_OVERLOADED. Full table: amazonscraperapi.com/docs/errors.

Get an API key

app.amazonscraperapi.com. 1,000 free requests on signup, no credit card required. Enough to test every tool this MCP exposes plus a few dozen productive chats.

Links

License

MIT