ApparelHub vs Ozon Seller MCP Server
A side-by-side look at the ApparelHub and Ozon Seller 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 ApparelHub for e-commerce work as a local process; choose Ozon Seller 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 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 Ozon Seller MCP Server 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:
OZON_CLIENT_ID, OZON_API_KEY. - You want tools like
get_seller_info, list_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 | 52/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 | OZON_CLIENT_IDOZON_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 6 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 124 | 26 |
| Full listing | View ApparelHub | View Ozon Seller MCP Server |
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
Ozon Seller MCP Server tools 26
get_seller_infoVerify credentials, get account infolist_productsList products with status filtersget_productProduct card: attributes, status, imagescreate_productCreate new products (up to 100 at once)update_productUpdate product attributes and descriptionarchive_productHide product from storefrontunarchive_productRestore product to active saleget_pricesCurrent prices and price indexupdate_pricesUpdate prices (up to 1000 products at once)get_stocksStock levels across all warehousesupdate_stocksUpdate FBS warehouse stockslist_fbo_ordersList FBO orders- +14 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.
ApparelHub
{
"mcpServers": {
"apparelhub": {
"command": "npx",
"args": [
"-y",
"@apparelhub/mcp-server"
],
"env": {
"APPARELHUB_API_KEY": "YOUR_APPARELHUB_API_KEY_HERE"
}
}
}
}
Ozon Seller MCP Server
{
"mcpServers": {
"ozon-seller-mcp-server": {
"command": "npx",
"args": [
"-y",
"@woyax/mcp-ozon-seller"
],
"env": {
"OZON_CLIENT_ID": "YOUR_OZON_CLIENT_ID_HERE",
"OZON_API_KEY": "YOUR_OZON_API_KEY_HERE"
}
}
}
}
Frequently asked questions
ApparelHub is categorized under E-Commerce and uses a local stdio subprocess. Ozon Seller MCP Server belongs to E-Commerce and uses a local stdio subprocess. Pick ApparelHub for e-commerce work and Ozon Seller 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.
ApparelHub is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: oauth 2.0. Ozon Seller MCP Server 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 ozon-seller-mcp-server 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. Ozon Seller MCP Server has 52/100 (Good) with 5 views, 0 installs and 6 GitHub stars.
