ApparelHub vs Keepa MCP
A side-by-side look at the ApparelHub and Keepa MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ApparelHub for e-commerce work as a local process; choose Keepa 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 ApparelHub when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
APPARELHUB_API_KEY. - You want tools like
check_setup_readiness, list_connectable_providers, connect_fulfillment_provider.
Choose Keepa MCP when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
KEEPA_API_KEY. - You want tools like
get_product, get_price_history, get_sales_rank_history.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 63/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | API key required |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | APPARELHUB_API_KEY | KEEPA_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | 124 | 6 |
| Full listing | View ApparelHub | View Keepa MCP |
Tools & capabilities
ApparelHub tools 124
check_setup_readinessWhat this account already has, what it still needs, and the single next action to take. Returns ready_to_design / ready_to_fulfill / ready_to_sell, a per-store breakdown, and an ordered next_steps list. Start here for any first-time setup, and call it again after each connection to confirm the state actually changed. Read-only, makes no provider calls, and is safe to poll. [#01f20c]list_connectable_providersFulfillment providers and sales channels this account may connect, each marked with how it connects: connect_mode "in_chat" means you can complete it here by asking for a credential, "browser" means you must dispatch an authorization link with start_channel_connect and poll. Also returns where the merchant generates the credential, when there is one. Use this before asking a user for anything, so you ask for the right thing. [#21af2f]connect_fulfillment_providerConnect an API-token fulfillment provider (Printify, Gelato) to a store, entirely in chat. Validates the token first, so a bad token fails before anything is stored. If the token maps to more than one shop the result asks you to pick one and lists them — call again with shop_id set. For Printful use start_channel_connect instead: it needs a browser. Never repeat the token back to the user. [#98598c]connect_sales_channelConnect an API-key sales channel (WooCommerce, Wix) to a store, entirely in chat. For Shopify and TikTok Shop use start_channel_connect instead: they need a browser. Credentials are write-only and are never returned. [#c9093d]start_channel_connectBegin a browser-based connection (Printful, Shopify, TikTok Shop, Fourthwall). Shopify additionally requires shop_url, the merchant myshopify domain — ask for it before calling. Returns an authorization URL to give the user. THE CONNECTION IS NOT FINISHED WHEN THIS RETURNS. You must keep polling check_connection_status (passing the same provider_uuid) until it reports connected, then tell the user. The browser tab where they authorize is NOT this conversation and cannot report back to you, so polling is the only way you or they will learn it worked. Poll every few seconds, up to about two minutes, and if it has not landed by then ask whether they finished authorizing rather than giving up silently. If they need to create an upstream account first, let them, then call this again for a fresh link. [#6d4006]check_connection_statusPoll whether a dispatched connection has completed. Call this repeatedly after start_channel_connect while the user authorizes in their browser, and announce the result when it lands: they cannot see this conversation from the tab they authorized in, so if you do not tell them, nobody does. Read-only, makes no provider call, and is safe to poll every few seconds. connected true means say so and continue setup. connected false means keep waiting. needs_reconnect means retrying will never work and you must dispatch a fresh link with start_channel_connect. [#807361]list_my_workspacesList the workspaces this account can act in, each with its uuid. Agency / multi-brand accounts have more than one (e.g. a workspace per client); a single account just has Default. The store / product / order / design tools operate on the Default workspace unless you pass workspace=<uuid>. Use this FIRST to resolve a workspace by name (e.g. a client's name) to the uuid those tools need. Read-only. [#358d40]list_my_storesList the merchant's ApparelHub stores, each with its fulfillment providers (Printful/Printify) and connected sales channels (Shopify/WooCommerce/Wix). Read-only. [#739377]list_my_designsList the merchant's generated design images (newest first). Read-only. Use these design_uuids with the design/product tools. Pass on_products=false to find orphan designs (designs not used by any live product), the supported way to audit a workspace for unused designs before archiving them. Pass archived=true to list already-archived designs. A design with no full_url carries processing_status: "pending"/"processing" means it is still being made and is worth polling, while "failed" means it gave up and processing_error says why. Branch on processing_error_code rather than matching the message text, and do not retry a design whose failure is a content block — it will fail the same way every time. [#58124e]get_design_collectionList the OTHER designs that came out of the same generation as this one. When generate_image is called with concepts > 1, one generation produces a themed set; every design is saved separately and this is how you find its siblings. The design you ask about is never included, and the list is oldest first. An ordinary design returns an empty list, which is the honest answer, not an error (an inaccessible or unknown uuid also reads as empty, so an empty list does not prove the design exists). Read-only and not metered. Each entry carries title and concept_description: the product name and retail description the model wrote for that concept. Use them to build products without asking the merchant to retype copy the model already produced; either may be null and must never be invented. background_state says whether the design can be lifted off its background: transparent is ready to place, opaque_box can be keyed automatically (process_transparency), opaque_varied cannot be separated and will print WITH its background. Asked for a set, the model often answers with pictures of finished garments rather than flat art, and building a product from one prints a garment onto a garment, so do NOT build a product from an opaque_varied design without telling the user it will print with its background. Do not describe it as "a photograph" either: legitimately textured art reports opaque_varied too. [#f2d543]list_my_productsList the merchant's products with their fulfillment and sales-channel sync status. Each channel entry also carries `health` — what the channel last said about the listing. A channel can remove or deactivate a listing at any time, so check `health`, not just `sync_status`: a product can read 'Synced' historically and still be gone. Pass store_uuid to scope to one store; omit for all products. Read-only. [#06afd6]list_my_ordersList the merchant's recent orders across channels. An order carrying `needs_attention` is one the merchant must act on (the fulfillment provider failed or cancelled it, the buyer cancelled after production started, or it was paid but never sent to production): always tell the user about those, with the `message`. Read-only. [#20d0e7]- +112 more on the listing page
Keepa MCP tools 6
get_productFetch current product details from Keepa for a given Amazon ASIN. Returns: title, brand, category path, current Amazon price, new (3P) price, buy box price, review count, star rating, number of new offers, and latest sales rank. Prices are in USD. A value of "N/A" means the price type is not currently available. Args: - asin (string): Amazon ASIN, e.g. "B08N5WRWNW" - domain (number, optional): Keepa domain id (default 1 = amazon.com) Examples: - "What is the current price of ASIN B08N5WRWNW?" -> use get_product with asin="B08N5WRWNW" - "Show me product details for B07PXGQC1Q" -> use get_product with asin="B07PXGQC1Q" Error handling: - Returns an instructional message if KEEPA_API_KEY is missing. - Returns a not-found message for invalid ASINs.get_price_historyFetch historical price data for an Amazon ASIN from Keepa. Returns a decoded, downsampled time series (at most 60 data points) for: - Amazon price (sold by Amazon directly) - New (3P) price (lowest new third-party price) - Used price (lowest used price) - Buy box price Keepa stores prices in cents. All prices returned are in USD. Keepa time values (minutes since 2011-01-01) are decoded to ISO dates. Args: - asin (string): Amazon ASIN - range (string, optional): Time range. "30d", "6m", "1y", "all". Default: "90d" - domain (number, optional): Keepa domain id (default 1 = amazon.com) Examples: - "Show price history for B08N5WRWNW over the past year" -> range="1y" - "What has the Amazon price been for B07PXGQC1Q in the last 30 days?" -> range="30d"get_sales_rank_historyFetch historical sales rank data for an Amazon ASIN from Keepa. Sales rank (BSR) is a proxy for demand: lower rank = faster sales velocity. Returns a decoded, downsampled time series plus a trend summary. The trend summary indicates whether demand is improving (rank decreasing), worsening (rank increasing), or stable. Args: - asin (string): Amazon ASIN - range (string, optional): Time range. "30d", "6m", "1y", "all". Default: "90d" - domain (number, optional): Keepa domain id (default 1 = amazon.com) Examples: - "Is demand trending up or down for B08N5WRWNW?" -> use get_sales_rank_history - "Show 6-month BSR history for B07PXGQC1Q" -> range="6m"search_productsSearch for Amazon products on Keepa by keyword. Returns a list of matching ASINs. Use get_product on any returned ASIN to fetch full product details, prices, and history. Args: - keyword (string): Search term, e.g. "wireless earbuds" - category_id (number, optional): Restrict to a Keepa category id. - domain (number, optional): Keepa domain id (default 1 = amazon.com) Examples: - "Find products for 'yoga mat'" -> keyword="yoga mat" - "Search Electronics for 'USB-C hub'" -> keyword="USB-C hub", category_id=172282get_best_sellersGet the top-selling ASINs in a Keepa category. Returns an ordered list of ASINs. Find category ids at: https://keepa.com/#!categorytree/1 Common category ids (amazon.com): - 172282: Electronics - 1055398: Computers & Accessories - 3760901: Camera & Photo - 2619533: Musical Instruments - 284507: Kitchen & Dining Args: - category_id (number): Keepa category id - domain (number, optional): Keepa domain id (default 1 = amazon.com) Examples: - "What are the best sellers in Electronics?" -> category_id=172282 - "Top Kitchen products" -> category_id=284507get_dealsFetch current Amazon price-drop deals from Keepa. Returns products where the price has dropped significantly, filtered by minimum price drop percentage and minimum rating. Args: - min_price_drop_pct (number, optional): Minimum % price drop (1-99). Default: 20 - min_rating (number, optional): Min rating 0-50 (45 = 4.5 stars). Default: 40 - page (number, optional): Page offset for pagination. Default: 0 - domain (number, optional): Keepa domain id (default 1 = amazon.com) Examples: - "Show me deals with at least 30% off" -> min_price_drop_pct=30 - "Find highly-rated products on sale" -> min_rating=45, min_price_drop_pct=20
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.
ApparelHub
{
"mcpServers": {
"apparelhub": {
"command": "npx",
"args": [
"-y",
"@apparelhub/mcp-server"
],
"env": {
"APPARELHUB_API_KEY": "YOUR_APPARELHUB_API_KEY_HERE"
}
}
}
}
Keepa MCP
{
"mcpServers": {
"keepa-mcp": {
"command": "npx",
"args": [
"-y",
"keepa-mcp"
],
"env": {
"KEEPA_API_KEY": "YOUR_KEEPA_API_KEY_HERE"
}
}
}
}
Frequently asked questions
ApparelHub is categorized under E-Commerce and uses a local stdio subprocess. Keepa MCP belongs to E-Commerce and uses a local stdio subprocess. Pick ApparelHub for e-commerce work and Keepa 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.
ApparelHub is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: oauth 2.0. Keepa MCP has no declared pricing — check the project's own site. Auth: api key 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 apparelhub and keepa-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ApparelHub has a quality signal of 63/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Keepa MCP has 60/100 (Good) with 7 views, 0 installs and 0 GitHub stars.
