ApparelHub

What the ApparelHub MCP server does

The ApparelHub MCP server gives an AI agent access to workflow-level operations for a custom-merch store. It connects to the ApparelHub Agent API and exposes 121 tools covering store setup, catalog research, apparel design, product creation, channel listings, order handling, fulfillment issues, channel intelligence, and analytics.

The workflow tools combine dependent operations. For example, ship_product can resolve variants, create or wait for mockup images, create the product, add variants, associate the product with a store, and synchronize it with fulfillment and sales channels. The server also checks for conditions such as negative-margin pricing and known variant problems.

How it works

ApparelHub provides two deployment models with the same agent-facing tool surface:

• The hosted connector runs as remote MCP over HTTP at https://mcp.apparelhub.ai. It uses OAuth authorization and provisions or reuses a connector key on the ApparelHub account, so the API key is not placed in the client configuration.
• The self-run npm package runs locally over stdio. It calls the ApparelHub API using the APPARELHUB_API_KEY environment variable and requires Node.js 20 or newer.

The hosted option is intended for MCP clients that support remote servers and OAuth. The local option suits clients without remote or OAuth support, local development, or users who want the process on their own machine. The hosted deployment includes the imaging dependencies used by design and quality tools. In the self-run setup, those tools can use Python 3 with Pillow and optionally tesseract.

Setup and configuration

For the hosted ApparelHub MCP server, add https://mcp.apparelhub.ai as a remote MCP server in a compatible client, then authenticate and approve access. Claude Code can add it with claude mcp add --transport http apparelhub https://mcp.apparelhub.ai. Clients that read MCP configuration files can use an HTTP server entry with the same URL.

For local installation, run npx -y @apparelhub/mcp-server with APPARELHUB_API_KEY set in the process environment. Create the key from the ApparelHub developer API-key page. The package does not accept the key as a tool argument, and its API host cannot be overridden. Set APPARELHUB_MCP_PYTHON if Python 3 is not available as python3; set APPARELHUB_MCP_TELEMETRY=off to disable the coarse usage signal.

Tools and capabilities

The tool groups support these operations:

• Check account readiness, list connectable providers, and connect fulfillment providers or sales channels.
• List workspaces, stores, designs, products, and orders, including order details.
• Browse and search connected garment catalogs, inspect garment details, and receive garment recommendations.
• Generate, iterate, upload, resize, archive, restore, and delete designs; process transparency and verify design text.
• Create, update, delete, and synchronize products, including channel diagnostics.
• Approve, hold, cancel, confirm, submit, reconcile, and inspect orders, with draft item editing and design-approval holds.
• Report, inspect, and resolve fulfillment issues, including replacement-order creation.
• Review channel performance, opportunities, coverage, listing changes, and configurable listing attributes and settings.

Limitations and notes

The npm package is early access and remains below version 1.0, although its agent-facing tool surface is identified as v1. Local image-processing tools return an installation notice when their dependencies are missing rather than crashing. Browser-based connections are used for some providers, including Printful, Shopify, TikTok Shop, and Fourthwall; API-token providers can be connected in chat. The hosted connector uses one connector key per account and that key counts toward the account's API-key allowance.