Pepesto MCP vs Store Builder
A side-by-side look at the Pepesto MCP 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 Pepesto MCP 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 Pepesto MCP when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PEPESTO_API_KEY. - You want tools like
pepesto_oneshot, pepesto_predirect, pepesto_parse.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 59/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | PEPESTO_API_KEY | SB_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 7 | 37 |
| Full listing | View Pepesto MCP | View Store Builder |
Tools & capabilities
Pepesto MCP tools 7
pepesto_oneshotOne-shot: turn recipe URLs, free-form text, and/or an image into a ready-to-checkout cart for a chosen European supermarket. Returns a redirect_url that opens the Pepesto checkout UI for the user to verify and pay. Internally runs parse + products + session (not exposed to agents) with Pepesto's heuristics. Use this when you want the simplest end-to-end flow; use pepesto_parse + pepesto_products + session (not exposed to agents) for finer control.pepesto_predirectTurn a free-form shopping list into a deferred deep link to the Pepesto mobile app, returned as a redirect_url. This is a PUBLIC endpoint: it is FREE to the API client, needs no API key, and returns instantly. Parsing and product matching happen lazily, only after the user opens the link — and the USER (not the API client) is charged when they proceed to checkout in the app. If the app isn't installed, the user is sent to the app store first and the shopping list is preserved until the app opens. This is an end-user / agent-facing handoff (e.g. a person chatting in Claude Desktop who wants to finish shopping on their phone), not a developer-integration endpoint. Choose pepesto_predirect when the cost should fall on the end user and a deferred deep link is acceptable. Choose pepesto_oneshot instead when the client wants the basket matched up front (with prices) and is willing to pay for the matching. PRESENTATION (important): the tool's text output is ready-to-show Markdown — a single tappable, labeled link plus a one-line caption. Surface it to the user exactly as returned; do NOT also paste the long raw URL as plain text. You may add one short sentence telling them to open it on their phone (on a computer, opening it shows a QR code to scan).pepesto_parseParse a recipe from a URL, free-form text, or image into a structured object: title, ingredients, nutrition, instructions, and a KgToken you can pass to pepesto_products to build a real cart. Once the response is returned, show recipe title, image if available (json property `image_url`, don't search for external images, skip rendering the Pepesto image if the image has webp extesion), ingredients, steps, nutrition summary, allergens clearly marked, and portions/servings if available. Don't show kg_token, but mark and save it for the next steps (e.g., /products call).pepesto_suggestSearch Pepesto's recipe graph (1M+ recipes) by free-text query and optional filters (cuisine, dietary tags, ingredients to include/avoid, time, servings). Each result includes a KgToken you can pass to pepesto_products. Returned images are licensed for display in your app or website without attribution. Show recipe title, image if available (json property `image_url`, don't search for external images, skip rendering the Pepesto image if the image has webp extesion), ingredients, steps, nutrition summary, allergens clearly marked, and portions/servings if available. Don't show kg_token, but mark and save it for the next steps (e.g., /products call).pepesto_productsMap one or more recipe KgTokens (and an optional manual shopping list) to concrete supermarket products with prices, images, or currency. Items are merged across recipes to reduce waste; multiple matches per ingredient let you (or the user) pick. Show product title, image if available (json property `image_url`, don't search for external images, skip rendering the Pepesto image if the image has webp extesion)product_id when available linking to an (external) supermarket page (open in a new tab), price, ProductClassification (is_bio, is_frozen, is_substitution) tags. PricePromotion shows if the item is currently on promotion and what's current `promo_percentage`pepesto_catalogDump Pepesto's full indexed catalog for a supermarket (~1-2k SKUs of common cooking ingredients, with names, prices, images, IDs). Optionally pass a webhook_url to receive incremental updates on re-index. Use only when the user has explicitly asked for a catalog dump, market analysis, or storefront build; for normal recipe-to-cart flows use pepesto_oneshot or pepesto_products instead. Cache this query aggressively, no more than one call per day per supermarket is recommended. When presenting supermarket results the user, use the product key as (external) link to the supermarket product itself. Show image if available (json property `image_url`, don't search for external images, skip rendering the Pepesto image if the image has webp extesion)pepesto_creditsReturn the remaining API credits on the configured Pepesto API key.
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
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.
Pepesto MCP
{
"mcpServers": {
"pepesto-mcp": {
"command": "npx",
"args": [
"-y",
"@pepesto/pepesto-mcp"
],
"env": {
"PEPESTO_API_KEY": "YOUR_PEPESTO_API_KEY_HERE"
}
}
}
}
Store Builder
{
"mcpServers": {
"store-builder": {
"command": "npx",
"args": [
"-y",
"sbuilder-mcp"
],
"env": {
"SB_TOKEN": "YOUR_SB_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Pepesto MCP is categorized under E-Commerce and uses a local stdio subprocess. Store Builder belongs to E-Commerce and uses a local stdio subprocess. Pick Pepesto MCP 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.
Pepesto MCP has no declared pricing — check the project's own site. Store Builder 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 pepesto-mcp and store-builder as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Pepesto MCP has a quality signal of 59/100 (Good) with 3 views, 0 installs and 7 GitHub stars. Store Builder has 64/100 (Good) with 1 views, 0 installs and 0 GitHub stars.
