Log inSubmit server
WebCake Storefront logo

WebCake Storefront

Build, validate, publish, and manage editable WebCake/StoreCake storefronts through AI assistants.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install WebCake Storefront

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": {
    "webcake-storefront": {
      "command": "npx",
      "args": [
        "-y",
        "webcake-storefront-mcp"
      ],
      "env": {
        "WEBCAKE_TOKEN": "YOUR_VALUE_HERE",
        "WEBCAKE_SESSION_ID": "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— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

WebCake Storefront MCP server connects AI assistants to WebCake and StoreCake through the BuilderX storefront component model. It can assemble, validate, save, and publish editable pages, then apply focused changes to individual elements. Store operations cover products, orders, collections, content, promotions, customers, themes, and automation. Reach for it when an agent needs to create or manage a WebCake storefront without manually editing builder JSON.

Use cases

  • Build an editable product landing page with a gallery, price, and order form
  • Create a storefront homepage with featured products and newsletter signup
  • Publish a flash-sale page with a countdown and discounted product grid
  • Manage products, orders, promotions, and content from an AI client

Key features

  • Generate editable BuilderX storefront pages from natural-language prompts
  • Validate page structure before saving
  • Preview writes with dry-run changes
  • Publish selected WebCake sites
  • Manage products, orders, content, customers, and promotions
  • Run locally over stdio or self-hosted Streamable HTTP

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.

6/6 checks healthy over the last 44d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · webcake-storefront-mcp (npm)

Adoption & maintenance

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

GitHub stars4Stargazers on the source repository.
npm downloads1kPackage downloads in the last 30 days.
Last commitTodayMost recent push to the default branch.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How WebCake Storefront works

What WebCake Storefront does

WebCake Storefront exposes the WebCake/StoreCake storefront builder and its backend through Model Context Protocol. Its page-building workflow turns a natural-language request into a page source object containing sections, validates that structure, and saves it to a selected site. Pages remain editable in the storefront builder after creation.

The server also provides access to live-store operations. Supported areas include pages and custom code, products, orders, collections, blog articles, promotions, combos, themes, customers, and automation. The project describes approximately 280 tools across page authoring and store management.

How it works

An MCP-capable client sends requests from an AI assistant to the server. For page work, the assistant can inspect the BuilderX element catalog and layout model, create sections, assemble a page, and run validation before saving. Validation checks include duplicate element IDs, invalid grids, unnamed form fields, and event targets that do not work.

Writes use a dry-run-first workflow. The assistant can preview a proposed change before applying it, and publish_site makes the selected site live. A focused edit can target one element while preserving the other page IDs, styles, and blocks. Site selection happens at runtime through list_my_sites and switch_site.

Setup and configuration

The local setup runs with Node.js 18 or newer:

Terminal
npx -y webcake-storefront-mcp install

The installer can configure Claude Desktop, Claude Code, Cursor, Windsurf, and VS Code. To run the server directly, use npx -y webcake-storefront-mcp. The login command opens the builder connection page and stores credentials locally. A non-interactive installation can receive a token and session ID as command-line arguments.

A self-hosted Streamable HTTP mode is available with serve --port 8787. Clients connect through the /mcp endpoint with a JWT query parameter or, where supported, the x-webcake-jwt header. HTTPS is appropriate when exposing a JWT-based remote URL.

Set WEBCAKE_TOKEN and WEBCAKE_SESSION_ID for authenticated site access. WEBCAKE_ENV selects the local, staging, or production endpoint preset; WEBCAKE_API_URL and WEBCAKE_APP_URL can override those presets. PEXELS_API_KEY is an optional server-side setting for image search. Credentials and the selected site can also be updated through chat and are stored under ~/.webcake-storefront-mcp/.

Tools and capabilities

  • Inspect the BuilderX build guide and element catalog with get_build_guide, list_elements, and get_element.
  • Create sections and validate page structures with new_section and validate_page.
  • Build and save pages, then publish the site.
  • Manage products, variations, carts, orders, promotions, and combos.
  • Work with pages, custom code, collections, blog articles, themes, customers, and automation.
  • Search images through the optional Pexels configuration.

The build-guide and catalog tools can be used without backend credentials, which allows exploration of the component model before connecting to a site.

Limitations and notes

Authenticated reads and writes require a WebCake token and session. The site is selected at runtime rather than through a required site-ID environment variable. Remote JWT URLs contain a personal token and should be treated as credentials. The available page model is BuilderX, so generated pages use the components and layout rules exposed by that model.

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 WebCake Storefront

WebCake Storefront is an MCP server that connects AI assistants to WebCake and StoreCake storefronts through the BuilderX component model. Its main tools build, validate, save, and publish editable pages, while additional tools manage products, orders, content, customers, promotions, themes, and automation.

Install it with `npx -y webcake-storefront-mcp install`. The installer can configure Claude Desktop, Claude Code, Cursor, Windsurf, or VS Code. You can also run `npx -y webcake-storefront-mcp` directly or use the `login` command to connect through the browser.

Yes, WebCake Storefront works with Cursor. The installation command can add its MCP configuration to Cursor, and the server also supports other named MCP clients including Claude Desktop, Claude Code, Windsurf, and VS Code.

Authenticated storefront operations require `WEBCAKE_TOKEN` and `WEBCAKE_SESSION_ID`. The token is a WebCake bearer JWT and the session value is sent as `x-session-id`. Build-guide and element-catalog tools can be used without backend credentials.

Use the page-building tools to assemble and validate the page, preview the write through the dry-run workflow, save it to the selected site, and call `publish_site` to make the site live. Select a site with `list_my_sites` and `switch_site`.

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 PreviewWebCake Storefront AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/webcake-storefront?style=directory)](https://allmcps.com/mcp/webcake-storefront)
HTML Embed
<a href="https://allmcps.com/mcp/webcake-storefront"><img src="https://allmcps.com/api/badge/webcake-storefront?style=directory" alt="WebCake Storefront on AllMCPs" /></a>