Easyparser — Amazon Product & Seller Data vs Amazon In MCP
A side-by-side look at the Easyparser — Amazon Product & Seller Data and Amazon In MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Easyparser — Amazon Product & Seller DataE-Commerce · Local subprocess (stdio)Real-time Amazon product, seller, and search data for AI agents across 21 marketplaces.60GoodAuth: not declared
Amazon In MCPE-Commerce · Local subprocess (stdio)Shop on amazon.in via LLM. Three tools: product search with "cheapest in stock" + "best value" picks, full product details (price, MRP, discount, rating, stock, seller), and Keepa price history chart links. No API keys, direct HTML scraping with retry on bot-check. Install: npx amazon-in-mcp-server.60GoodAuth: no auth requiredVerdict: choose Easyparser — Amazon Product & Seller Data for e-commerce work as a local process; choose Amazon In MCP for e-commerce as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Easyparser — Amazon Product & Seller Data when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
EASYPARSER_API_KEY. - You want tools like
get_product_detail, get_product_offers, search_products.
Choose Amazon In MCP when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
search_amazon_in, get_product, price_history_link.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Easyparser — Amazon Product & Seller Data | Amazon In MCP |
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 60/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | EASYPARSER_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 9 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 17 | 3 |
| Full listing | View Easyparser — Amazon Product & Seller Data | View Amazon In MCP |
Tools & capabilities
Easyparser — Amazon Product & Seller Data tools 17
get_product_detailFetch complete, structured information about a single Amazon product: title, brand, images, feature bullets, description, Buy Box price and availability, Prime eligibility, rating and review count, Best Sellers Rank, category path, variants, specifications, and top reviews. This is the primary tool for product analysis, listing enrichment, and price monitoring. Use this tool when you need a full product profile. If you only need competing seller prices, use get_product_offers instead (cheaper context). If you only need the sales rank, use get_bestseller_rank. If you only need shipping dimensions or the FBA fee category, use get_package_dimensions. Provide EITHER the identifier field OR url — never both. Costs 1 credit; set a_plus_content to true only when the user explicitly asks about enhanced brand content, as it costs 1 extra credit.get_product_offersFetch the list of seller offers for an Amazon product: every merchant selling the item with their price, shipping cost, condition (new/used), fulfillment type (FBA/FBM), and seller rating. Also returns the Buy Box winner. This is the tool for competitive price analysis, reseller monitoring, and availability tracking. Use this tool when the question is about WHO sells the product and at WHAT price. If you need the product's own details (title, images, rating), use get_product_detail instead. Each requested page costs 1 credit. Start with a single page (default) and only increase max_page if the user needs the full offer list. Use the condition and shipping filters to narrow results instead of paginating — it is cheaper.search_productsSearch Amazon by keyword or a full search/category URL and get structured product listings: ASIN, title, price, rating, review count, Prime status, and badges (Best Seller, Amazon's Choice) for each result. Also returns the available refinement filters (category, brand, price range) with their IDs. Use this tool for market research, keyword analysis, and product discovery. If the user already has an ASIN or product URL, do NOT search — use get_product_detail directly. Each page costs 1 credit. One page typically returns 20-40 products, which is enough for most questions. Use sort_by and exclude_sponsored to improve result quality instead of fetching more pages. To filter by category or brand, first run one search and read the refinements field in the response to discover valid filter IDs, then pass them in refinements.lookup_productConvert an external product identifier (UPC, EAN, GTIN, ISBN, JAN, MINSAN) into the corresponding Amazon ASIN, with an essential product snapshot. This is the bridge between manufacturer/retail barcodes and the Amazon ecosystem. Use this tool when the user has a barcode or standard product code and wants to find the matching Amazon listing. Typical workflows: catalog matching, inventory synchronization, converting supplier data into Amazon ASINs. Also accepts ASIN as input type if you need to validate one. You MUST set identifier_type to match the code you have — guessing the wrong type returns no results. UPC is 12 digits, EAN/GTIN is 13, ISBN is 10 or 13 (books). If the user gives a keyword instead of a code, use search_products instead. Costs 1 credit.get_sales_historyRetrieve a product's historical performance over up to 12 months: weekly aggregated trends for estimated views/traffic, sales, price, and Best Sellers Rank. This is Easyparser's 'time machine' — the deepest competitive-intelligence tool in this server. Use this tool for trend forecasting, seasonality analysis, conversion-rate estimation, and investment/sourcing due diligence. Do NOT use it for a simple current price check — get_product_detail is 5x cheaper for that. IMPORTANT cost rule: the base cost is 5 credits, and each month of history adds 1 credit (3 months = 8 credits, 12 months = 17 credits). Always ask the user how far back they need, or default to 3 months for a quick trend read. The history array in the response is aggregated by WEEK, not by day.get_bestseller_rankGet a product's current Best Sellers Rank (BSR): its numerical rank in main categories and sub-category node identifiers. A lightweight, single-purpose tool for popularity and demand tracking. Use this tool when you only need the rank — e.g. 'Is this product selling well?' or daily rank monitoring. Lower rank number means higher sales velocity. If you also need price, rating or content, use get_product_detail instead (it includes BSR along with everything else). For historical rank trends, use get_sales_history. Costs 1 credit.get_package_dimensionsGet a product's precise physical and logistical attributes: package height, width, length, weight, and its Amazon fee category (e.g. Computers, Apparel). This is the FBA fee-estimation and shipping-cost tool. Use this tool when the question is about shipping, storage, FBA fees, or warehouse planning. Do NOT use it for general product info — get_product_detail includes a human-readable dimensions string, but only THIS tool returns the structured fee category and exact measurements needed for fee calculation. Costs 1 credit.get_seller_profileUnmask the legal identity and reputation of any Amazon merchant: legal business name, registered business address, and granular feedback trends over 30/90/365 days and lifetime. This is the supplier-verification and brand-protection tool. Use this tool when the user asks 'who is this seller?', 'is this merchant legitimate?', or needs a supplier's legal entity for compliance or invoicing. To see WHAT the seller sells, use get_seller_products. To read individual buyer reviews about the seller, use get_seller_feedback. Provide EITHER seller_id OR url — never both. You can discover a product's seller by calling get_product_offers first. Costs 1 credit.get_seller_productsExtract a seller's full product catalog: every ASIN they sell with brand, category, price, Prime status, variant counts, and rating data. Also returns dynamic refinement filters (department, shipping, sustainability) for drilling into the catalog. Use this tool for competitor inventory analysis, stock monitoring, and pricing-strategy research. If you need the seller's legal identity or reputation instead of their products, use get_seller_profile. Each page costs 1 credit. Start with one page and use sort_by (e.g. 'exact-aware-popularity-rank' for best sellers first) to surface the most relevant products early. Provide EITHER seller_id OR url — never both.get_seller_feedbackRead individual buyer feedback entries for an Amazon seller: star ratings, comment text, and dates — filterable by rating range and time period. This is the reputation deep-dive tool. Use this tool when the user wants to read actual buyer comments about a seller, analyze complaint patterns, or audit service quality. For aggregate reputation scores (30/90/365-day percentages) without individual comments, get_seller_profile is sufficient and cheaper in context. Each page costs 1 credit. To find dissatisfied customers, set max_rating to 3 instead of paging through everything.list_operationsList all Easyparser operations available in this server, with their parameters, credit costs, and example use cases. Works WITHOUT an API key — call this first to understand what the server can do, or when you are unsure which tool fits the user's question. Also returns the list of supported Amazon marketplace domains.list_bulk_jobsList the user's bulk extraction jobs with their progress: operation, domain, status, total/completed/failed/invalid item counts, and timestamps. This reads the SAME data as the Bulk Requests page in the Easyparser web app — so it can see and track jobs the user started from the app UI, not just jobs submitted through this MCP server. Use this tool when the user asks about their bulk jobs: "is my job done?", "what bulk jobs are running?", "did the DETAIL batch finish?". Each row includes a group_id — pass it to get_bulk_job_items to drill into individual items, or to get_bulk_webhook_logs to check webhook deliveries. Statuses: pending (queued), processing (running), completed (all items succeeded), partial_success (some items failed or were dropped — check failed_items/invalid_items counts), failed. This tool is free of per-call credits (monitoring endpoints do not consume credits).- +5 more on the listing page
Amazon In MCP tools 3
search_amazon_inSearch amazon.in (Amazon India) for products by keyword and return ranked listings. Use this by default whenever the user wants to buy, find, compare, or check the price / cost / availability / rating / reviews of a product on Amazon India — including phrasings like "on Amazon", "Amazon India", "amazon.in", "find me a…", "cheapest…", or "what's the price of…". Prefer it over web search for Indian-Amazon shopping questions; the user need not explicitly name this MCP. This tool scrapes the public amazon.in search page (no API key needed). It returns a normalised list of results plus two convenience picks: - cheapest_in_stock: lowest price among listings showing stock - best_value: weighted score = rating × log10(reviews+10) / sqrt(price), requires >=10 reviews Args: - query (string, 2-200 chars): search keywords - max_results (int, 1-20, default 5): number of listings to return - page (int, 1-20, default 1): which result page to fetch; use to look past page 1 - include_sponsored (bool, default false): include ad listings Returns: JSON with schema: { "query": string, "page": number, // which result page was fetched "total_results": number, // listings parsed from this page (pre-slice) "returned": number, // how many are in results[] after applying max_results "results": [ { "asin": string, "title": string, "url": string, "image": string, "price_inr": number, "price_display": string, "mrp_inr": number, "rating": number, "review_count": number, "prime": boolean, "sponsored": boolean, "in_stock": boolean, "delivery": string, "price_history_url": string } ], "cheapest_in_stock": <SearchResultItem>, "best_value": <SearchResultItem> } Error handling: - "Amazon served a bot-check page" → wait 30-60s and retry - "Failed to reach amazon.in" → transient network or throttlingget_productFetch a single amazon.in product's details by ASIN or URL. Use this by default whenever the user pastes an amazon.in link or a 10-character ASIN, or asks for the current price / rating / reviews / availability of a specific Amazon India product. Prefer it over web search or training-data guesses. Scrapes the product page and returns price, MRP, discount %, rating, review count, availability, bullets, brand, seller, delivery info, and a Keepa price-history URL. Args: - asin_or_url (string): plain 10-char ASIN (e.g., "B0BDHWDR12") or any amazon.in product URL containing /dp/<ASIN> Returns: JSON with schema: { "asin": string, "title": string, "url": string, "image": string, "price_inr": number, "price_display": string, "mrp_inr": number, "discount_percent": number, "rating": number, "review_count": number, "in_stock": boolean, "availability": string, "bullets": string[], "brand": string, "seller": string, "delivery": string, "price_history_url": string } Error handling: - "Could not extract ASIN" → input was not a valid ASIN or amazon.in URL - "Bot-check page" → retry after a delayprice_history_linkBuild a Keepa.com price-history URL for an amazon.in ASIN. No network call. Keepa renders historical price charts in the browser using the format keepa.com/#!product/12-<ASIN>, where 12 is the amazon.in domain code. This tool is offline — just a deterministic URL builder. Args: - asin_or_url (string): plain ASIN or amazon.in URL containing /dp/<ASIN> Returns: JSON { "asin": string, "price_history_url": string }
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Easyparser — Amazon Product & Seller Data
{
"mcpServers": {
"easyparser-amazon-product-seller-data": {
"command": "npx",
"args": [
"-y",
"easyparser-mcp"
],
"env": {
"EASYPARSER_API_KEY": "YOUR_EASYPARSER_API_KEY_HERE"
}
}
}
}
Amazon In MCP
{
"mcpServers": {
"justadityaraj-amazon-in-mcp": {
"command": "npx",
"args": [
"-y",
"amazon-in-mcp-server"
]
}
}
}
Frequently asked questions
Easyparser — Amazon Product & Seller Data is categorized under E-Commerce and uses a local stdio subprocess. Amazon In MCP belongs to E-Commerce and uses a local stdio subprocess. Pick Easyparser — Amazon Product & Seller Data for e-commerce work and Amazon In MCP for e-commerce.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Easyparser — Amazon Product & Seller Data has no declared pricing — check the project's own site. Amazon In MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add easyparser-amazon-product-seller-data and justadityaraj-amazon-in-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Easyparser — Amazon Product & Seller Data has a quality signal of 60/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Amazon In MCP has 60/100 (Good) with 3 views, 0 installs and 9 GitHub stars.
