ApparelHub vs Store Builder
A side-by-side look at the ApparelHub and Store Builder 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 Store Builder 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.
- You have the keys it needs:
APPARELHUB_API_KEY, APPARELHUB_MCP_TELEMETRY, APPARELHUB_MCP_PYTHON.
Choose Store Builder when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SB_API, SB_TOKEN, SB_SITE, SB_SITE_NAME, SB_EMAIL, SB_PASSWORD, PEXELS_API_KEYS. - You want tools like
sb_connect, sb_site_list, sb_api_find.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 36/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | APPARELHUB_API_KEYAPPARELHUB_MCP_TELEMETRYAPPARELHUB_MCP_PYTHON |
Tools & capabilities
ApparelHub tools
No tool names declared yet. Check the project README from the listing page.
Store Builder tools 37
sb_connectLog in, list the sites this account can operate, report which credentials are presentsb_site_listList the sites this account can operatesb_api_findFind API operations by intent — one line per match — then read one operation's call sheet by id: real parameter schemas, the credential it needs, and the body's fields read off the handler that decodes them, each carrying the trap its own doc comment recordssb_api_callExecute an operation, or any route by method+path; dry run by default. Field selection and local result pagination; `merge` for whole-record PUTs, `If-Match`, multipart `filesb_page_openOpen a page for editing and return its outline — or, with `form_id`, a form's field document (fields, defaults, dependent-field rules)sb_outlineThe open page as a compressed tree — never a raw document dumpsb_node_readOne node in full, with a warning if it is a shared globalsb_catalog_searchFind an element by what it should do, using the platform's own AI hintssb_traits_forAn element's inspector — tabs, groups, controls and what each declared one writes — plus its AI hints, defaults and containment rulessb_addAdd an element — or a whole nested subtree — in one callsb_setWrite style/config/specials. Per breakpoint by defaultsb_moveMove a node to another parent- +25 more on the
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",
"APPARELHUB_MCP_TELEMETRY": "YOUR_APPARELHUB_MCP_TELEMETRY_HERE",
"APPARELHUB_MCP_PYTHON": "YOUR_APPARELHUB_MCP_PYTHON_HERE"
}
}
}
}
Store Builder
{
"mcpServers": {
"store-builder": {
"command": "npx",
"args": [
"-y",
"sbuilder-mcp"
],
"env": {
"SB_API": "YOUR_SB_API_HERE",
"SB_TOKEN": "YOUR_SB_TOKEN_HERE",
"SB_SITE": "YOUR_SB_SITE_HERE",
"SB_SITE_NAME": "YOUR_SB_SITE_NAME_HERE",
"SB_EMAIL": "YOUR_SB_EMAIL_HERE",
"SB_PASSWORD": "YOUR_SB_PASSWORD_HERE",
"PEXELS_API_KEYS": "YOUR_PEXELS_API_KEYS_HERE"
}
}
}
}
Frequently asked questions
ApparelHub is categorized under E-Commerce and uses a local stdio subprocess. Store Builder belongs to E-Commerce and uses a local stdio subprocess. Pick ApparelHub for e-commerce work and Store Builder 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. Store Builder 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 apparelhub and store-builder 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 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Store Builder has 57/100 (Good) with 0 views, 0 installs and 0 GitHub stars.