Easyparser — Amazon Product & Seller Data vs PoloPan Fashion MCP Server
A side-by-side look at the Easyparser — Amazon Product & Seller Data and PoloPan Fashion MCP Server 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 declaredVerdict: choose Easyparser — Amazon Product & Seller Data for e-commerce work as a local process; choose PoloPan Fashion MCP Server 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 PoloPan Fashion MCP Server when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You want tools like
region.get_current, region.set_current, region.list_supported.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Easyparser — Amazon Product & Seller Data | |
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 60/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | EASYPARSER_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 17 | 19 |
| Full listing | View Easyparser — Amazon Product & Seller Data | View PoloPan Fashion MCP Server |
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
PoloPan Fashion MCP Server tools 19
region.get_currentGet the currently active shopping destination country, currency code, symbol, phone code, and catalog scope mode from persistent local configuration (~/.polopan/region.json).region.set_currentSet the active shopping country/region using any natural country name, city (e.g. 'Dubai', 'London', 'California', 'Paris'), 2-letter ISO code ('US', 'GB', 'IN', 'AE', 'CA'), or currency ('USD', 'AED', 'GBP', 'EUR'). Saves to persistent local JSON (~/.polopan/region.json) so the user never needs to be asked again across turns and sessions.region.list_supportedSearch the 240+ supported destination countries with localized currency codes, symbols, flags, phone codes, and price groups from live platform settings.address.get_currentGet the default delivery/shipping address saved for the currently active region from local configuration (~/.polopan/region.json). WHEN TO USE (CRITICAL ANTI-SHORTCIRCUIT RULE): - ALWAYS call this BEFORE generating 1-click checkout links to check if the user already has a saved delivery address for their destination country. - If 'has_address' is false, DO NOT emit a naked checkout link. Prompt the user naturally for their shipping address (First Name, Street Address, City, Postal Code, Phone & Email) and save it using 'address.save'. - If 'has_address' is true, inform the user you are prefilling their saved address and proceed with checkout.address.saveSave a customer delivery shipping address mapped to the active region in ~/.polopan/region.json. Matches Flutter app (newapp) address schema: firstName, lastName, address1, address2, city, province, zip, country, phone, email, type.address.list_savedList all saved customer delivery addresses stored in ~/.polopan/region.json, optionally filtered by country.address.set_defaultSet an existing address as the default shipping address for its country in ~/.polopan/region.json.address.deleteDelete a saved delivery address by ID from ~/.polopan/region.json.products.search.textSearch PoloPan catalog products using a text keyword query with optional multi-attribute filters. Returns matching fashion items with available in-stock sizes, product specifications, shipping/return policies, discounted pricing, and verified purchase URLs (https://s.polopan.com/p/{handle}). Automatically localized to active country / 240+ destination regions. PURPOSE & DISAMBIGUATION: - Primary text-based catalog search tool for fashion discovery across apparel, footwear, and accessories. - Distinct from 'products.search.image_url' / 'products.search.image_upload': Use this tool for textual queries and keyword filters, NOT for visual image search. - Distinct from 'products.search.alternatives': Use this tool for open discovery queries, NOT for finding direct visual substitutes of a known product handle. - Distinct from 'looks.curation.by_occasion': Use this tool to search individual products, NOT complete multi-piece outfit looks. WHEN TO USE: - When a user searches for clothing or fashion styles using keywords, brand names, colors, or categories (e.g. 'black leather jacket', 'floral summer midi dress', 'men linen shirts'). - When refining catalog searches with structured filters like price ranges, gender, sizes, country regions, or vendor brands. WHEN NOT TO USE: - Do NOT use when the user provides an image URL or image file (use 'products.search.image_url' or 'products.search.image_upload'). - Do NOT use when searching for cheaper/higher-end substitutes of a specific known product (use 'products.search.alternatives'). - Do NOT use to find curated complete occasion outfits (use 'looks.curation.by_occasion'). BEHAVIOR & SAFETY: - Read-only and idempotent with no persistent state modifications. - Automatically sanitizes and enriches product records with verified PoloPan short permalinks (https://s.polopan.com/p/{handle}), computed in-stock size lists, and human-readable shipping and return policy strings. - Handles pagination and multi-attribute filtering deterministically. PARAMETERS & CONSTRAINTS: - 'query' (string, required): Free-text search query or style keyword (e.g. 'black linen shirt', 'oversized hoodie'). - 'country' (string, optional): Target country name, city, currency, or ISO-2 code (e.g. 'US', 'United States', 'UK', 'Dubai', 'CA', 'IN'). Defaults to active saved region. - 'mode' (enum, optional): Catalog mode: 'global' (ships to country) or 'local' (domestic only). - 'page' (integer >= 1, default 1): Pagination page number. - 'page_size' (integer 1-100, default 20): Number of products returned per page. - 'sort_by' (enum, default 'relevance'): Ranking criterion ('relevance', 'price', 'title'). - 'sort_order' (enum, default 'desc'): Sort direction ('asc' for ascending, 'desc' for descending). - 'gender' (string, optional): Target demographic filter ('men', 'women', or 'unisex'). - 'size' (array of strings, optional): Size filter array (e.g. ['S', 'M', 'L', 'XL', '32', '40']). - 'price_min' (number, optional): Minimum price threshold in local currency. - 'price_max' (number, optional): Maximum price threshold in local currency. - 'vendor' (array of strings, optional): List of brand or vendor names to filter by. MANDATORY AGENT INSTRUCTIONS: 1. Always communicate available in-stock sizes, fast dispatch SLA, and return policy for each product (Negative return days = 'Exchange only |X| days'). 2. When presenting or shortlisting products, display the product specifications table (Fabric, Pattern, Collar, Sleeves, Fit, Care). 3. Return the clean base link (https://s.polopan.com/p/{handle}) during browsing. Provide direct checkout link (https://s.polopan.com/p/{handle}/{size_index}) ONLY after the user's size is finalized.products.search.image_urlSearch PoloPan catalog products using visual image similarity from a publicly accessible image URL with optional multi-attribute filters. Returns visually similar products with available sizes, pricing, and verified purchase URLs (https://s.polopan.com/p/{handle}). Automatically localized to active country / 240+ destination regions. PURPOSE & DISAMBIGUATION: - Performs reverse visual search using computer-vision embeddings for a remote image URL. - Distinct from 'products.search.text': Use this tool when you have an image URL, NOT for textual keyword queries. - Distinct from 'products.search.image_upload': Use this tool for publicly hosted HTTP(S) image URLs, NOT for local file paths or base64 data. - Distinct from 'vision.outfit.detect_pieces': Use this tool to search catalog items matching an entire single-garment image, NOT for segmenting multi-garment influencer photos into bounding boxes. WHEN TO USE: - When the user shares a web link to an image (e.g. Pinterest, Instagram, blog post) and wants to find visually matching products in the PoloPan catalog. WHEN NOT TO USE: - Do NOT use when the image is stored on local disk or as base64 data (use 'products.search.image_upload'). - Do NOT use when searching by text descriptions (use 'products.search.text'). - Do NOT use when you need to crop/isolate individual outfit pieces from a full-body model photo (use 'vision.outfit.detect_pieces'). BEHAVIOR & SAFETY: - Read-only and idempotent with no persistent state modifications. - Downloads the image, generates visual embeddings, and retrieves ranked catalog matches. - Enriches all returned items with verified PoloPan purchase links and stock metadata. PARAMETERS & CONSTRAINTS: - 'image_url' (string, required): Publicly accessible HTTP(S) URL of the image to search for visual matches. - 'country' (string, optional): Target country name, city, currency, or ISO-2 code (e.g. 'US', 'United States', 'UK', 'Dubai', 'CA', 'IN'). Defaults to active saved region. - 'mode' (enum, optional): Catalog mode: 'global' (ships to country) or 'local' (domestic only). - 'page' (integer >= 1, default 1): Pagination page number. - 'page_size' (integer 1-100, default 20): Number of candidate items returned per page. - 'sort_by' (enum, default 'relevance'): Ranking attribute ('relevance', 'price', 'title'). - 'sort_order' (enum, default 'desc'): Sort order ('asc' or 'desc'). - 'gender' (string, optional): Target gender filter ('men', 'women', or 'unisex'). - 'size' (array of strings, optional): Filter by available size labels. - 'price_min' (number, optional): Minimum price threshold. - 'price_max' (number, optional): Maximum price threshold. - 'vendor' (array of strings, optional): Brand filter array. - 'personalize' (boolean, default false): Whether to apply personalized ranking weights.products.search.image_uploadUpload a local image file (or base64 string) and search PoloPan catalog products using visual image similarity. Returns matching products with available in-stock sizes, pricing, and verified purchase URLs (https://s.polopan.com/p/{handle}). Automatically localized to active country / 240+ destination regions. PURPOSE & DISAMBIGUATION: - Performs reverse visual search by uploading a local or base64-encoded image to secure temporary storage, then querying visual embeddings. - Distinct from 'products.search.image_url': Use this tool when the image file is local on the user's machine or in base64 format, NOT already on a public URL. - Distinct from 'vision.outfit.detect_pieces': Use this tool to search for products matching a single garment, NOT for decomposing full multi-piece outfits into bounding boxes. WHEN TO USE: - When a user uploads a local photo/screenshot or supplies base64 image data to find matching fashion products in the catalog. WHEN NOT TO USE: - Do NOT use when the image is already accessible via a public web URL (use 'products.search.image_url'). - Do NOT use for text-only searches (use 'products.search.text'). BEHAVIOR & SAFETY: - Read-only catalog query with temporary image upload artifact (automatically expires after 'expiry_hours', default 24h). - Resolves MIME types automatically if not explicitly provided. - Enriches all returned items with verified PoloPan purchase links and stock metadata. PARAMETERS & CONSTRAINTS: - 'image_path' (string, optional): Local file system path to the image file (one of image_path or image_base64 is required). - 'image_base64' (string, optional): Base64-encoded image data string. - 'country' (string, optional): Target country name, city, currency, or ISO-2 code (e.g. 'US', 'United States', 'UK', 'Dubai', 'CA', 'IN'). Defaults to active saved region. - 'mode' (enum, optional): Catalog mode: 'global' (ships to country) or 'local' (domestic only). - 'content_type' (string, default 'image/jpeg'): MIME type of the uploaded image (e.g. 'image/jpeg', 'image/png', 'image/webp'). - 'expiry_hours' (integer 1-168, default 24): Temporary upload lifetime in hours before expiration. - 'page' (integer >= 1, default 1): Pagination page number. - 'page_size' (integer 1-100, default 20): Number of items per page. - 'sort_by' (enum, default 'relevance'): Sorting attribute ('relevance', 'price', 'title'). - 'sort_order' (enum, default 'desc'): Sort direction ('asc' or 'desc'). - 'gender' (string, optional): Target gender filter ('men', 'women', or 'unisex'). - 'size' (array of strings, optional): Size filter array. - 'price_min' (number, optional): Minimum price threshold. - 'price_max' (number, optional): Maximum price threshold. - 'vendor' (array of strings, optional): Brand filter array. - 'personalize' (boolean, default false): Whether to personalize search ranking.vision.outfit.detect_piecesDeconstruct an outfit image or influencer photo into individual fashion pieces (e.g. Upper-body garment, Lower-body garment, Dress, Footwear, Bag, Headwear) with normalized bounding box coordinates and detection confidence scores. PURPOSE & DISAMBIGUATION: - Computer-vision object detection tool designed to analyze multi-item outfit photographs and isolate individual garments with their spatial coordinates. - Distinct from 'products.search.image_url' / 'products.search.image_upload': Use this tool to segment a full outfit into pieces before querying, NOT to directly retrieve catalog search results. - Distinct from 'looks.curation.recommend': Use this tool for image-based piece decomposition, NOT text-based styling suggestions. WHEN TO USE: - When the user provides a full-body model photo, street style snapshot, or celebrity outfit and wants to identify each individual clothing piece (jacket, top, pants, shoes, bag) to find matching products for each piece. WHEN NOT TO USE: - Do NOT use when the image contains only a single standalone garment (use 'products.search.image_url' or 'products.search.image_upload' directly). - Do NOT use for text-only searches (use 'products.search.text'). BEHAVIOR & SAFETY: - Read-only and idempotent with no persistent state modifications. - Supports input via local file path ('image_path'), base64 string ('image_base64'), or public URL ('image_url'). Exactly one source must be provided. - Returns an array of detected piece objects with 'label', 'confidence' (0.0 to 1.0), and normalized 'box' coordinates [ymin, xmin, ymax, xmax]. PARAMETERS & CONSTRAINTS: - 'image_path' (string, optional): Local file system path to the outfit image (e.g. '/tmp/outfit.jpg'). - 'image_base64' (string, optional): Base64-encoded image data string. - 'image_url' (string, optional): Public HTTP(S) URL of the image. - 'threshold' (number 0.05-0.95, default 0.22): Detection confidence threshold for bounding box filtering.- +7 more on the listing page
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"
}
}
}
}
PoloPan Fashion MCP Server
{
"mcpServers": {
"polopan-fashion-mcp-server": {
"command": "npx",
"args": [
"-y",
"polopan-products-mcp"
]
}
}
}
Frequently asked questions
Easyparser — Amazon Product & Seller Data is categorized under E-Commerce and uses a local stdio subprocess. PoloPan Fashion MCP Server belongs to E-Commerce and uses a local stdio subprocess. Pick Easyparser — Amazon Product & Seller Data for e-commerce work and PoloPan Fashion MCP Server 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. PoloPan Fashion MCP Server has no declared pricing — check the project's own site. 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 polopan-fashion-mcp-server 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 3 views, 0 installs and 0 GitHub stars. PoloPan Fashion MCP Server has 63/100 (Good) with 1 views, 0 installs and 1 GitHub stars.
