Amazon Scraper API

Overview

Amazon Scraper API MCP is a stdio MCP server for Amazon Scraper API. It gives MCP clients structured Amazon product, search, and batch scraping tools backed by Amazon Scraper API.

Installation

The README documents MCP client launch with:

npx -y amazon-scraper-api-mcp

Claude Code setup is documented as:

claude mcp add amazon-scraper -- npx -y amazon-scraper-api-mcp

The source also includes a Dockerfile for building a local stdio image with entrypoint node dist/index.js, but no published Docker/OCI image or docker run command is documented, so the submitted package target is the published npm package.

Configuration

Set ASA_API_KEY in the MCP client environment. The server exits at startup if this variable is missing.

Amazon Scraper API documentation says API keys are obtained from the dashboard and are secret values. The underlying HTTP API authenticates using an api_key query parameter; the MCP server passes the env-sourced key to the official Node SDK.

Capabilities

• amazon_product: fetch structured data for one Amazon product by ASIN, with optional marketplace domain and content language.
• amazon_search: search Amazon by keyword with optional marketplace domain, sort order, start page, and page count.
• amazon_batch_create: queue up to 1000 product/search inputs for async processing, with optional webhook callback URL.
• amazon_batch_status: poll an async batch job by id.

The tools return JSON text from the Amazon Scraper API SDK. Product/search docs describe fields including prices, ratings, reviews count, availability, buybox, variants, images, categories, and sponsored/organic positions.

Limitations

• Requires an Amazon Scraper API account, credits, and a valid ASA_API_KEY.
• API usage is subject to plan-specific rate limits, concurrency limits, and billing. Official docs state only successful 2xx responses are billed.
• Marketplace routing is controlled through the tool domain argument; proxy egress is automatic and cannot be manually configured.
• language only affects presentation content and may fall back silently when unsupported by a marketplace.
• Product endpoint options render_js and screenshot are documented as roadmap parameters that currently return 501, and they are not exposed as MCP tool parameters in the reviewed source.
• Batch webhooks require a public HTTPS callback URL and webhook signature verification by the receiver.
• The checked-in server.json records version 0.1.4, but current package.json, package-lock.json, and npm latest are 0.1.5; the submitted package metadata uses 0.1.5.