Log inSubmit server
Store Builder logo

Store Builder

Design, populate, inspect, and publish Store Builder storefront pages through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Store Builder

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "store-builder": {
      "command": "npx",
      "args": [
        "-y",
        "sbuilder-mcp"
      ],
      "env": {
        "SB_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

Store Builder MCP server lets an AI agent operate a Store Builder site from setup through publication. It connects over stdio, uses an API key or account credentials, and exposes tools for page structure, store data, media, templates, custom code, rendering, review, and publishing. Agents can edit responsive layouts, bind content to store data, inspect rendered screenshots, and verify live revisions. Reach for it when an agent needs to build or maintain an e-commerce storefront without manual editor操作.

Use cases

  • Build storefront pages from nested responsive sections
  • Populate product and category layouts with store data
  • Inspect mobile and desktop rendering defects
  • Publish page revisions and verify the live storefront
  • Manage shared headers, footers, media, and templates

Key features

  • MCP stdio access to Store Builder sites
  • Responsive page tree editing
  • Store data discovery and binding
  • Template and media-library management
  • Rendered screenshots with layout measurements
  • Draft, version, repair, and publish workflows

Tools37

What Store Builder lets your agent do. Expand a tool for its parameters.

Verified live~8.0k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

5/5 checks healthy over the last 44d

What it can do

From the 37 tools this server returned when we ran it; 37 declare their own safety hints.

Can delete or modify data · 7Handles credentials · 6Makes network requests · 8Read-only tools · 30
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age53 days
Maintainers1

Observed 2026-10-21 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · sbuilder-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads9.6kPackage downloads in the last 30 days.
Last commitTodayMost recent push to the default branch.
Tools exposed37Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Store Builder works

What Store Builder does

Store Builder gives an MCP-compatible AI agent access to the Store Builder site builder and its store APIs. It can list accessible sites, inspect the platform's API catalog, create and manage pages, edit nested page elements, connect content to store data, and publish completed drafts.

The editing model is document-oriented. Agents open a page, inspect its compressed outline or individual nodes, then add, configure, move, duplicate, or remove elements. Pages can include shared global sections and site-specific overlays. The server also supports saved section templates, built-in layouts, media-library operations, custom code, SEO settings, page versions, and live-edit collaboration.

How it works

The server runs as an MCP stdio process. Each request uses the Store Builder API and is limited by the key's scopes, the creating member's role, and the site assigned to that key. A configured SB_SITE makes subsequent tools default to one store; otherwise, the agent can discover site identifiers through account-level operations.

A typical editing sequence starts with sb_connect or a site selection, followed by sb_page_open. The agent can then inspect the outline, read node configuration, search the element catalog, and retrieve inspector controls before making changes. sb_add accepts nested children, allowing a complete section to be created in one operation. sb_set writes style, configuration, and special fields per breakpoint unless a base-layer update is requested.

Most API calls and recovery operations support dry-run behavior. sb_look saves and renders a page at desktop, tablet, and mobile widths, returning screenshots, measured boxes, and detected layout problems. sb_review checks visitor-facing defects and identifies missing pieces in the path to a paid order. sb_publish compiles the draft, reports the live revision, and can verify whether the origin is serving it.

Setup and configuration

Create an AI-agent key from the store's Apps → AI agent screen, then configure the server with an MCP client. The installer can write configuration for supported clients and preserve existing server entries by creating a backup of the modified file. It accepts a site ID and optional site label, and supports a dry-run mode.

A manual configuration uses the npx -y sbuilder-mcp command with SB_API, SB_TOKEN, and optionally SB_SITE in the environment. SB_API defaults to http://localhost:8080. Account email and password can be supplied for account-level actions such as listing sites; the API key remains the normal credential for site operations.

The optional PEXELS_API_KEYS setting belongs on the server and enables photograph search for sb_media_upload. Without it, an agent can still upload a local image or provide a URL for the platform to fetch.

Tools and capabilities

  • Discover sites and API operations with sb_connect, sb_site_list, sb_api_find, and sb_api_call.
  • Create, inspect, edit, duplicate, move, remove, repair, version, and publish pages.
  • Search element types, inspect their controls, build nested sections, and apply responsive settings.
  • Bind nodes to store data and configure cart, navigation, popup, and page actions.
  • Manage templates, media assets, themes, translations, custom code, and live editing.
  • Render pages for visual inspection and review checkout, delivery, cart, and other order-flow gaps.

Limitations and notes

sb_page_open must precede node edits such as add, set, move, or remove. Large page documents are intentionally represented through outlines and targeted node reads rather than raw dumps. Publishing a page that shares global sections can republish those sections across other pages, and the storefront may continue serving a cached revision for up to 60 seconds.

The page type controls routes such as checkout and product URLs; those routes require a published page of the corresponding type. sb_event configures navigation and interface actions, but a purchase action uses data binding instead. Media search depends on server-side Pexels keys, while URL-based image fetching remains available without them.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Store Builder

Store Builder is an MCP server that connects AI agents to Store Builder sites through the platform API and live-edit features. Its main tools discover sites and operations, edit pages and elements, manage media and templates, bind store data, render previews, review order flows, and publish revisions.

Install it with `npx -y sbuilder-mcp install --token YOUR_TOKEN --api YOUR_API_URL --site YOUR_SITE_ID`. The installer can configure detected Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, and Codex clients, or you can add the stdio configuration manually.

Store Builder normally uses `SB_TOKEN` for site operations. `SB_EMAIL` and `SB_PASSWORD` are optional and enable account-level actions such as listing sites, while `SB_API` selects the API endpoint and defaults to `http://localhost:8080`.

Yes. `sb_look` saves the draft, renders it at desktop, tablet, and mobile widths, and returns screenshots, measured element boxes, and detected issues such as overflow or overlap. `sb_review` separately checks visitor-facing defects and gaps in the purchase flow.

Related MCP servers

All in E-Commerce All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewStore Builder AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/store-builder?style=directory)](https://allmcps.com/mcp/store-builder)
HTML Embed
<a href="https://allmcps.com/mcp/store-builder"><img src="https://allmcps.com/api/badge/store-builder?style=directory" alt="Store Builder on AllMCPs" /></a>