sbuilder-mcp
Related Servers
Alternatives to sbuilder-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to build, edit, preview, and publish websites through natural language, including managing pages, designs, products, and site publishing.MIT- AlicenseBqualityBmaintenanceEnables AI assistants to build, validate, and publish storefront pages to WebCake/StoreCake sites based on natural language descriptions.133474 npm5MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create and iteratively edit browser games, web apps, and websites from natural-language prompts, track builds, preview results, and request publication.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to build and update complete applications, including creating, updating, publishing, previewing, and configuring databases, security, permissions, and server-side integrations.Apache 2.0

PromptSwingofficial
AlicenseNot gradedqualityBmaintenanceEnables 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.15 npmApache 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.-
TDQS
Scored across 39 tools
Most tools have a crisp, distinct job (sb_add/sb_set/sb_move/sb_remove, sb_media_list vs sb_media_upload, sb_api_find vs sb_api_call), and the descriptions actively fence off look-alikes ("Not sb_code", "Not the custom-code element", sb_page_version vs sb_undo vs sb_page_state). The weak spots are sb_store, which is a mega-action tool whose checkout/form/chrome/menu/overlay/global actions overlap with sb_page_create, sb_template_use and sb_page_open(form_id), and the cluster of read-only inspectors (sb_outline, sb_node_read, sb_page_state, sb_review) that need careful reading to keep apart.
Everything is snake_case under a uniform sb_ prefix, with predictable families (sb_page_*, sb_media_*, sb_api_*, sb_import*). The ordering is inconsistent though: some names are noun_verb (sb_site_list, sb_node_read, sb_page_open, sb_catalog_search) and others verb-only (sb_add, sb_set, sb_publish, sb_undo), and sb_templates vs sb_template_use mixes plural and singular for the same resource.
39 tools is far past the comfortable range for a single agent surface; the tool list alone is a large context cost before any work begins. The domain is genuinely broad (page editing, theming, commerce, media, collections, functions, i18n, import), but several could be collapsed — the sb_store action multiplex and the four read-only page inspectors especially — into fewer, better-scoped tools.
Coverage is unusually thorough: page create/open/update/publish/version/repair, element CRUD, styling, bindings, events, templates, media, theme tokens, i18n, collections, backend functions, custom code, and a generic sb_api_call escape hatch to 969 operations. The main native gaps are page/site deletion, site creation and domain/settings management, which an agent can reach through sb_api_call but not through purpose-built tools.