Shoporacle vs Store Builder — MCP Server Comparison | AllMCPs
Shoporacle vs Store Builder
A side-by-side look at the Shoporacle 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 Shoporacle for e-commerce work over a hosted endpoint; 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 Shoporacle when
You need dedicated capabilities in the E-Commerce domain.
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 present
sb_site_listList the sites this account can operate
sb_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 records
sb_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 `file
sb_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 dump
sb_node_readOne node in full, with a warning if it is a shared global
sb_catalog_searchFind an element by what it should do, using the platform's own AI hints
sb_traits_forAn element's inspector — tabs, groups, controls and what each declared one writes — plus its AI hints, defaults and containment rules
sb_addAdd an element — or a whole nested subtree — in one call
sb_setWrite style/config/specials. Per breakpoint by default
sb_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.
Shoporacle is categorized under E-Commerce and uses a remote HTTP/SSE transport. Store Builder belongs to E-Commerce and uses a local stdio subprocess. Pick Shoporacle 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.
Shoporacle has no declared pricing — check the project's own site. 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 shoporacle and store-builder as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Shoporacle has a quality signal of 32/100 (Emerging) with 1 views, 0 installs and 0 GitHub stars. Store Builder has 57/100 (Good) with 0 views, 0 installs and 0 GitHub stars.