Store Builder vs Thingery
A side-by-side look at the Store Builder and Thingery MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Store Builder for e-commerce work as a local process; choose Thingery 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 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.
Choose Thingery when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DATABASE_URL. - You want tools like
describe_category, search_items, get_item.
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 | Not declared | Not declared |
| Pricing | Not declared | Free |
| Required env vars | SB_APISB_TOKENSB_SITESB_SITE_NAMESB_EMAILSB_PASSWORDPEXELS_API_KEYS | DATABASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 37 | 16 |
| Full listing | View Store Builder | View Thingery |
Tools & capabilities
Store Builder tools 37
sb_connectLog in and list the sites this account can operate. Call this first. Reads SB_EMAIL and SB_PASSWORD from the environment unless you pass them.sb_site_listList the sites this account can operate.sb_api_findFind API operations by intent (query), or get a call sheet (id): parameters, credential, body fields and handler caveats. Reaches all 892 operations.sb_api_callCall an operation from sb_api_find (id), or a route the catalog lacks (method+path); dry run by default. pick selects fields, max_items caps lists, item_offset skips items. Lists over 60 KB say so.sb_page_openOpen a page for editing and return its outline. Call before any sb_add / sb_set / sb_move / sb_remove. Find page ids with sb_api_find "list pages". Or form_id: edit that form's field document (fields, specials.formRules on its root).sb_page_repairRename a page root that is not "ROOT" (sppro_1, rt_<hex> — left by older seeds) to ROOT, for one page or, without page_id, every page on the site. Draft only; a published page is listed for re-publishing. dry_run (default true) lists what would change.sb_outlineThe open page as a compressed tree — id, type, name, child count, band, and whether a node is a shared global or a site overlay. Never the raw document: a real page is hundreds of KB of JSON.sb_node_readOne node in full — style, config, specials, per-breakpoint overrides, bindings.sb_catalog_searchFind an element type by what it does — or OMIT query to browse every type, the only way to meet one you would not have searched for. detail:true adds the AI hints, as does sb_traits_for. query "icon:<word>" lists icon names.sb_traits_forThis element's INSPECTOR, as a person sees it: tabs, groups, and every control name — with what each DECLARED control writes, and the AI hints for using the element. Read this before styling an element; pass control to read one control in full.sb_addAdd an element — or a whole NESTED subtree — under a parent. One call builds a complete section: pass children rather than calling this once per node.sb_setWrite style, config or specials keys on one node, or on many through edits (one save, one live frame). Per BREAKPOINT by default; base:true writes the fallback layer, right for a value that should not vary.- +25 more on the listing page
Thingery tools 16
describe_categoryList categories and their declared attribute fields — the self-describing schema for agents. Declared fields get validated on create; undeclared keys are allowed, searchable, and their real use is surfaced via `undeclared_in_usesearch_itemsHybrid semantic + keyword search with price/category/condition/attribute filters (any attribute key, declared or not)get_itemFetch one listing by idcreate_listingPublish an item — core fields plus a flexible `attributes` object (declared keys validated, extras pass through and stay searchable)add_item_imageAttach a photo to a listing (base64 in, stored server-side — no URLs needed; max 5 MB decoded). Images are re-encoded at ingest: metadata (EXIF/GPS/XMP) stripped, downscaled to ≤ 2000 px, animated GIFs stored as stills; large PNGs may be rejected — prefer JPEGmy_listingsYour listings by statusupdate_listingMark reserved/sold, adjust price, edit text or attributesget_payout_setupStripe Express onboarding URL + status — optional, enables platform paymentcreate_orderOrder an item — returns a Stripe Checkout URL (stripe mode) or tracks an off-platform orderget_orderOne of your orders (buyer or seller side): status, tracking, deadlinescancel_orderCancel while cancellable; paid orders refund insteadrecord_trackingRecord carrier + tracking code; auto carrier tracker when EasyPost is configured- +4 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.
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"
}
}
}
}
Thingery
{
"mcpServers": {
"thingery": {
"command": "npx",
"args": [
"-y",
"thingery"
],
"env": {
"DATABASE_URL": "YOUR_DATABASE_URL_HERE"
}
}
}
}
Frequently asked questions
Store Builder is categorized under E-Commerce and uses a local stdio subprocess. Thingery belongs to E-Commerce and uses a local stdio subprocess. Pick Store Builder for e-commerce work and Thingery 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.
Store Builder has no declared pricing — check the project's own site. Thingery is listed as free. 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 store-builder and thingery as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Store Builder has a quality signal of 63/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Thingery has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.
