Store Builder vs Tanatasa Beauty
A side-by-side look at the Store Builder and Tanatasa Beauty 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 Tanatasa Beauty for e-commerce over a hosted endpoint. 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.
- Its auth model fits you: API key required.
- You have the keys it needs:
SB_TOKEN. - You want tools like
sb_connect, sb_site_list, sb_api_find.
Choose Tanatasa Beauty when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
search_products, get_product, create_cart.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 64/100 · Good | 76/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | No auth required |
| Pricing | Not declared | Free |
| Required env vars | SB_TOKEN | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 37 | 10 |
| Full listing | View Store Builder | View Tanatasa Beauty |
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
Tanatasa Beauty tools 10
search_productsSearch public sellable variants by words, brand/category/purpose, skin type, ingredient, availability and price in SGD cents. Use variant_id when adding items; follow next_page for more results.get_productGet product descriptions, ingredients, usage, images and variants. product accepts a product ID, product slug, variant slug or SKU.create_cartCreate an empty persistent cart without account login. Save cart_id, version and the private guest_token if returned. Pass guest_token on subsequent shopping calls. Account authentication is optional.get_cartRead cart items, coupon, version and checkout lock.set_cart_itemAdd or update a variant using an absolute quantity; zero removes it. Supply the current cart version. Maximum 20 variants and 99 units each; availability is checked.set_cart_couponApply a coupon code or null to remove it. Supply current cart version. Auto discounts also apply.quote_cartReprice the cart with current stock, scheduled prices and discounts. All amounts are SGD cents; shipping is free within Singapore. Stock is not reserved. Save version and total for checkout.create_checkoutPrepare a Tanatasa checkout review link for a quoted cart. Provide quoted version and expected_total in SGD cents. Keep the same idempotency_key and input on retries. Locks cart. Buyer reviews items and enters contact/delivery details on Tanatasa before paying. No payment occurs in this tool; get_order reports progress and webhook-confirmed status.get_orderGet payment and fulfilment status and tracking for a purchase created by this guest session or account connection. Supply guest_token for guest purchases. Payment confirmation comes from Stripe webhooks. Does not update prior purchases.checkout_sessionPrepare checkout from product feed item IDs and quantities without account login. For guests, call create_cart first and supply its guest_token. Optional item metadata is not authoritative. Returns a Tanatasa review link; the buyer enters delivery details and approves payment. Supply a new idempotency_key per purchase and retain it and guest_token on retries.
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_TOKEN": "YOUR_SB_TOKEN_HERE"
}
}
}
}
Tanatasa Beauty
{
"mcpServers": {
"tanatasa": {
"url": "https://tanatasa.sg/mcp"
}
}
}
Frequently asked questions
Store Builder is categorized under E-Commerce and uses a local stdio subprocess. Tanatasa Beauty belongs to E-Commerce and uses a remote HTTP/SSE transport. Pick Store Builder for e-commerce work and Tanatasa Beauty 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. Auth: api key required. Tanatasa Beauty is listed as free. Auth: no auth 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 store-builder and tanatasa 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 64/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Tanatasa Beauty has 76/100 (Great) with 3 views, 0 installs and 0 GitHub stars.
