amazon-in-mcp

What it does

Three tools your LLM can call against amazon.in:

No API keys. No accounts. Runs locally over stdio. Direct HTML scraping with rotating user agents and retry on bot-check pages.

Related MCP server: Amazon Product Intelligence Agent

Quick start

1. Install (Claude Code):

git clone https://github.com/justadityaraj/amazon-in-mcp.git
cd amazon-in-mcp && npm install && npm run build
claude mcp add amazon-in -- node "$PWD/dist/index.js"

2. Restart your MCP client (Claude Code, Cursor, Claude Desktop, etc.)

3. Ask:

"Find me a good 1TB external SSD on amazon.in under ₹10,000. Best value pick."

Your LLM will call search_amazon_in, rank by value, and hand back a real product with current price and a Keepa link for price history.

What it looks like

A real call to search_amazon_in("wireless mouse", max_results=3) returns:

{
  "query": "wireless mouse",
  "page": 1,
  "total_results": 3,
  "results": [
    {
      "asin": "B0CQRNWJM2",
      "title": "ZEBRONICS Blanc Slim Wireless Mouse...",
      "url": "https://www.amazon.in/dp/B0CQRNWJM2?tag=artech-21",
      "price_inr": 423,
      "mrp_inr": 799,
      "rating": 4.0,
      "review_count": 7801,
      "in_stock": true,
      "delivery": "FREE delivery Tomorrow",
      "price_history_url": "https://keepa.com/#!product/12-B0CQRNWJM2"
    }
  ],
  "cheapest_in_stock": { "asin": "...", "price_inr": 199, "...": "..." },
  "best_value":        { "asin": "...", "rating": 4.3, "...": "..." }
}

get_product adds bullets[], brand, seller, discount_percent, availability.

Configure your MCP client

claude mcp add amazon-in -- node /absolute/path/to/amazon-in-mcp/dist/index.js

Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "amazon-in": {
      "command": "node",
      "args": ["/absolute/path/to/amazon-in-mcp/dist/index.js"]
    }
  }
}

Same JSON config as Claude Desktop. Drop it into the client's MCP settings file.

Configuration

All optional. Set these in the env block of your MCP client config; defaults preserve the original behavior.

Example — route through a proxy and shorten the cache to 30 s:

{
  "mcpServers": {
    "amazon-in": {
      "command": "node",
      "args": ["/path/to/dist/index.js"],
      "env": {
        "AMAZON_IN_PROXY": "http://user:pass@proxy.example:8080",
        "AMAZON_IN_CACHE_TTL_MS": "30000"
      }
    }
  }
}

Automatic routing (no need to say "use the Amazon MCP")

Once installed, the server tells your client to reach for these tools on its own. It ships MCP server instructions (returned in the initialize handshake) that instruct the model to use search_amazon_in / get_product by default for any amazon.in shopping, price, availability, or reviews question — including when you just paste an amazon.in link or an ASIN. The tool descriptions carry the same trigger keywords as a fallback for clients that read tool descriptions but not server instructions.

So you can ask "find me a mechanical keyboard under 3000" or paste a product link and the client routes to this server without you naming it. Note this is model-level guidance surfaced by the host (Claude Code, Claude Desktop, Cursor, …), not a hard protocol guarantee — a client that ignores server instructions and tool descriptions won't be forced to route.

Image search

The server intentionally doesn't accept image input — keeps it provider-agnostic. Instead, paste the image into your LLM client, ask it to describe the product, and it'll call search_amazon_in with the right keywords automatically. Works the same in every MCP-capable client.

How "best value" is scored

Among in-stock listings with at least 10 reviews:

$$ \text{score} = \frac{\text{rating} \times \log_{10}(\text{reviews} + 10)}{\sqrt{\text{price}}} $$

The highest score wins. cheapest_in_stock is just the lowest price_inr among in-stock items — useful when you want raw cheapness instead of balance.

Robustness

Expect ~1–5% of requests to fail with a bot-check during heavy use. Wait 30–60 seconds and retry, run from a different network, or set AMAZON_IN_PROXY.

How this project is funded

By default, amazon.in URLs returned by this server include the author's Amazon Associates tag (artech-21). If you (or your LLM) click through and buy something, the author earns a small commission. You pay the same price. This is the only way the project stays free, MIT, and actively maintained.

Override or disable anytime with the AMAZON_IN_AFFILIATE_TAG env var:

Example — your own tag:

{
  "mcpServers": {
    "amazon-in": {
      "command": "node",
      "args": ["/path/to/dist/index.js"],
      "env": { "AMAZON_IN_AFFILIATE_TAG": "yourtag-21" }
    }
  }
}

Roadmap

• Publish to npm so install becomes npx -y amazon-in-mcp-server

• Optional Keepa API support (user-supplied key) for real price-history data

• Filter helpers — min_rating, min_reviews, under_price

• Smoke-test suite with cached HTML fixtures

Development

npm install
npm run dev      # tsx watch
npm run build    # tsc → dist/
npm start        # node dist/index.js

Test interactively with the MCP Inspector:

npx @modelcontextprotocol/inspector node dist/index.js

Project layout:

src/
  index.ts        # MCP server + 3 tool registrations
  scraper.ts      # fetch with UA rotation, retry, bot-check, proxy, cache
  parse.ts        # cheerio selectors for search + product pages
  cache.ts        # in-memory TTL + LRU cache
  constants.ts    # UAs, headers, tuning constants, affiliate/proxy/cache config
  types.ts        # SearchResultItem, ProductDetail

Disclaimer

Fetches publicly accessible amazon.in pages for personal research and assistant use. Does not bypass authentication, paywalls, or CAPTCHAs — when Amazon serves a bot-check the tool stops and reports the error.

You are responsible for using this in line with Amazon's Terms of Service and any local laws. No warranty about uptime, accuracy, or fitness for any purpose. DOM selectors are best-effort and may break when Amazon updates its layout. PRs welcome.

License

MIT © Aditya Raj Singh

Issues, bug reports, and selector fixes welcome — Amazon's DOM shifts every few months, so this will break occasionally and need community help to keep current.