PoloPan Fashion MCP Server vs TrustRails MCP Server
A side-by-side look at the PoloPan Fashion MCP Server and TrustRails MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose PoloPan Fashion MCP Server for e-commerce work as a local process; choose TrustRails 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 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.
Choose TrustRails MCP Server when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TRUSTRAILS_API_KEY. - You want tools like
search_products, get_product.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 63/100 · Good | 55/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 | None listed | TRUSTRAILS_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 19 | 2 |
| Full listing | View PoloPan Fashion MCP Server | View TrustRails MCP Server |
Tools & capabilities
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
TrustRails MCP Server tools 2
search_productsHOW TO CALL THIS TOOL — read before every call: Decompose the user's request into filters first. Only what's left over goes in query. STEP 1: brand name → brand filter. STEP 2: product category → category filter. STEP 3: price → min_price/max_price. STEP 4: RAM, storage, screen size, resolution, refresh rate, wattage, Wi-Fi generation → constraints. STEP 5: what remains → query. BAD: query='Sony headphones under £200' | GOOD: brand='Sony', category='Headphones', max_price=200, no query. BAD: query='tablet' | GOOD: category='Tablets', no query. BAD: query='macbook neo' | GOOD: brand='Apple', category='Laptops', query='neo'. BAD: query='Samsung QLED TV' | GOOD: brand='Samsung', category='TVs', query='qled'. If brand+category alone cover what the user wants, omit query entirely. Only put differentiating terms in query: model lines (neo, ultra, oled), variants, model numbers (WH-1000XM5, s25 ultra). Query words must appear in the title, except words naming the category ('router' in Networking) and bare numbers or specs ('4070', '16GB'), which are ignored when finding products and only rank them. Put a model number with its prefix ('RTX 4070', not '4070') and check each title for it. Leave out use-case words like gaming, cheap or best. CROSS-CATEGORY NOTE: Gaming headsets → category='Headphones', query='gaming headset'. The Gaming category is consoles/controllers/accessories only. Always set lite=true (it still carries `attributes`). If 0 results, broaden the query or drop filters (but never present a near miss as meeting a requirement). Searches 26,000+ UK electronics products across 7 retailers with price comparison. Prices are in GBP. Every listing is new (refurbished and used are excluded). PRICE COMPARISON: for a final pick with offer_count > 1, get_product returns offers[] (sorted in-stock first, then cheapest): show the cheapest in-stock retailer, the other prices with the difference and the exact saving among in-stock offers. Before claiming a saving, read offers[].title (from get_product): they must name the same model; if they differ, don't claim one. Before recommending any pick, check its title is the product type asked for (not a cable, accessory or adapter). COMPARING SPECS: compare products from the `attributes` in the search results, not by calling get_product on each. Every spec known for a product is there as {status, value}, or {status, values} when conflicting, without sources; names and units are as in `constraints`. 'confirmed' (two or more retailers state the same value) and 'inferred' (one retailer's title states it) are both the product's spec: state the value. Only `conflicting` (retailers disagree: say so, don't pick one) or a missing name (unknown) needs a caveat. A product with no `attributes` has none of these seven specs known: say so only if the user asked about one. Call get_product only for your final 1-3 picks, and only when you need what search lacks: what only the retailer's description has (processor, GPU, ports, weight, battery), or every retailer's offer and buy link (search results carry only the best offer's purchase_url (cheapest in stock)). A pick with offer_count 1 needs no call unless the user asked for a description-only detail. Don't guess those details from titles. SPEC REQUIREMENTS: put exact requirements in `constraints`, not in query, and always set `category` (and brand if known) with `constraints`: a search of only specs is rejected. If a requirement is ambiguous (e.g. '16GB' could be RAM or storage), ask the user or search without that constraint. With constraints, every product has `constraint_status` per name: 'matched' = a retailer's title states a value that meets it. 'unverified' = not known to meet it: check `attributes[name]`, where `conflicting` means retailers disagree and missing means unknown. Never treat 'unverified' as a match or say a product meets a requirement because it was returned: tell the user it is unconfirmed. Products whose stated value fails are left out (`excluded_by_constraints`). Matched results come first, also with sort='price_asc'. With constraints, `total` counts the products that match every constraint and `unverified_total` the unverified products that passed the other filters (only some may be in `products`). If `total` is 0, say no product is known to meet every requirement and offer the unverified ones only as unconfirmed. If `candidates_truncated` is true, the first 2,000 candidates in the chosen sort order were checked and more exist: add a brand or category, or a narrower query, and search again before saying nothing matches. If the search was already narrowed, tell the user the results may be incomplete. STOCK: availability is in_stock, low_stock, out_of_stock or unknown (the retailer gave no stock signal: say so, don't assume). When availability is out_of_stock, mention it as an alternative and suggest checking back — do not silently omit it. purchase_url is a trustrails.app/go/ redirect through an affiliate link; TrustRails may earn a commission, and the price is the same. Colour variants have separate barcodes and are separate products: when price matters, search again without the colour or check other colours of the same model.get_productGet full details for a single product by ID. Returns `attributes`: structured specs read from retailer titles, each name mapping to {status, value, sources}; a conflicting one has values: [{value, sources}] instead of value and sources. Names and units as in the search constraints argument. status: 'confirmed' = two or more retailers state the same value; 'inferred' = one retailer's title states it; 'conflicting' = retailers state different values (none is picked, tell the user they disagree; a retailer can appear under two values, so read offers[].title to see which listing states which); a missing name = unknown. Also returns specs.description, the retailer's own prose: use it only for details attributes do not cover (processor, GPU, ports, weight, battery, features); if it doesn't give a detail, tell the user it isn't listed. It can describe another configuration or a maximum ('up to 32GB'), so it never overrides or fills in an attribute: if an attribute is missing or conflicting, that spec is unknown or unconfirmed, and you may mention what the description says only as 'the retailer's description mentions X, unconfirmed'. It also returns pricing, availability, delivery time, and all retailer offers with per-retailer pricing (offers[].stock is a unit count only when the retailer supplies one, otherwise null). Accepts both canonical product IDs and original retailer offer IDs. Use this after search_products only for your final 1-3 picks, and only when you need what search lacks: details only the description has, or every retailer's offer and buy link. Search results already carry `attributes` to compare specs.
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.
PoloPan Fashion MCP Server
{
"mcpServers": {
"polopan-fashion-mcp-server": {
"command": "npx",
"args": [
"-y",
"polopan-products-mcp"
]
}
}
}
TrustRails MCP Server
{
"mcpServers": {
"server-3": {
"command": "npx",
"args": [
"-y",
"@trustrails/mcp-server"
],
"env": {
"TRUSTRAILS_API_KEY": "YOUR_TRUSTRAILS_API_KEY_HERE"
}
}
}
}
Frequently asked questions
PoloPan Fashion MCP Server is categorized under E-Commerce and uses a local stdio subprocess. TrustRails MCP Server belongs to E-Commerce and uses a local stdio subprocess. Pick PoloPan Fashion MCP Server for e-commerce work and TrustRails 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.
PoloPan Fashion MCP Server has no declared pricing — check the project's own site. TrustRails 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 polopan-fashion-mcp-server and server-3 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, PoloPan Fashion MCP Server has a quality signal of 63/100 (Good) with 1 views, 0 installs and 1 GitHub stars. TrustRails MCP Server has 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars.
