A
licenseB
qualityA
maintenanceEnables AI assistants to build, validate, and publish storefront pages to WebCake/StoreCake sites based on natural language descriptions.
135
77
4
MIT
sbuilder-mcp
by vuluu2k
Related Servers
Alternatives to sbuilder-mcp
No user-submitted related servers found.
Related Servers
PromptSwingofficial
AlicenseNot gradedqualityCmaintenanceEnables an AI assistant to publish a storefront it built to live hosting, read the live site back, add, update or delete a single page, manage the catalogue, orders and reviews, and restore any earlier version in one call. Hosting requires a paid subscription, and a free pre-publish assessment reports which documented signal calls, contrast pairs or hardcoded prices would fail.Apache 2.0- FlicenseNot gradedqualityCmaintenanceEnables AI agents to provide e-commerce customer service with product search, RAG-based FAQ answers, human handoff, and automated security auditing with a review workflow.-
- FlicenseNot gradedqualityCmaintenanceEnables AI coding agents to plan, build, and review websites and product interfaces with a persistent, user-led process, including design direction, component contracts, and implementation review.-
- FlicenseNot gradedqualityCmaintenanceEnable AI agents to autonomously build and deploy full-stack mobile applications.1-
- AlicenseNot gradedqualityDmaintenanceYour AI coding agent tests pages, copy, and flows on simulated users while building.1MIT
TDQS
B3.2/5.0
Scored across 31 tools
Disambiguation4/5
Most tools target clearly distinct operations (add vs move vs duplicate vs remove; find vs call; page_open vs page_create vs publish), and the descriptions explicitly resolve tricky pairs like sb_event vs sb_bind and sb_import vs sb_import_site. Minor overlap remains between sb_connect and sb_site_list (both list sites) and among the several content-insertion tools, but boundaries are largely legible.
Naming Consistency4/5
Every tool shares a uniform sb_ prefix and groups cleanly into namespaces (sb_page_*, sb_media_*, sb_api_*, sb_template_*), which is easy to scan. The only deviation is mixed verb-only (sb_add, sb_set, sb_remove) versus noun_verb (sb_page_open, sb_node_read) forms, but this split is internally systematic and readable.
Tool Count3/5
At 31 tools the surface is heavier than the ideal 3-15 range and pushes into the 'too many' band, though the domain (page building, media, themes, store flows, imports, raw API access) is genuinely broad. Each tool covers a distinct facet, but some (catalog/traits/api_find/api_call) could plausibly be consolidated.
Completeness4/5
Coverage is strong: pages (list/open/create/publish), nodes (add/set/move/remove/read/duplicate), media (list/upload), templates, theme tokens, bindings, store flows, imports, review/look, undo and live-join are all present. The main gaps are explicit page/media deletion or page-update tools, which an agent must fall back to sb_api_call to perform.
Maintenance
ActivityNo data
ResponsivenessNo issues