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- AlicenseBqualityAmaintenanceEnables AI assistants to build, validate, and publish storefront pages to WebCake/StoreCake sites based on natural language descriptions.131185 npm4MIT
- 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.53 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.-
- FlicenseNot gradedqualityDmaintenanceEnables 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.-
TDQS
Scored across 37 tools
Most tools have clearly distinct purposes (e.g., sb_add vs sb_duplicate vs sb_template_use), and descriptions differentiate overlapping cases like sb_bind vs sb_event and sb_page_state vs sb_page_version. However, some ambiguities remain: sb_connect duplicates sb_site_list's listing, sb_page_open points to sb_api_find for page IDs despite sb_page_list existing, and the multi-action sb_store sprawls across many concerns, risking misselection.
All tools share the sb_ prefix and snake_case, but the naming pattern is mixed: some are verb-only (sb_add, sb_move), some noun_verb (sb_page_create, sb_site_list), and some noun-only (sb_templates). This mixed convention is readable but not fully predictable.
37 tools is heavy for a single MCP server; the platform is complex, but many operations could be consolidated or parameterized (e.g., the multi-action sb_store already does this). Per rubric, 25+ tools score 2.
The surface covers the site-building lifecycle extensively: pages, nodes, styling, publishing, store flows, media, templates, translation, versioning, and a generic API escape hatch. Missing direct page deletion and some store entity CRUD, but agents can use sb_api_call to work around those gaps.