Zarla MCP serverofficial
A
licenseNot graded
qualityC
maintenanceEnables AI assistants to build, edit, preview, and publish websites through natural language, including managing pages, designs, products, and site publishing.
MIT
sbuilder-mcp
by vuluu2k
Related Servers
Alternatives to sbuilder-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables AI assistants to build, validate, and publish storefront pages to WebCake/StoreCake sites based on natural language descriptions.135165 npm4MIT
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.183 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 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.-
apparelhub-mcpofficial
AlicenseAqualityAmaintenanceRun a custom-merchandise store end to end from an AI agent: generate designs, build products with mockups and margin-safe pricing, list them on Shopify, WooCommerce, Wix and TikTok Shop, and route orders to Printful, Printify or Gelato for fulfillment.123572 npmMIT
TDQS
B3/5.0
Scored across 33 tools
Disambiguation3/5
Many tools target distinct resources and actions (media, page, node, API, templates), but sb_connect and sb_site_list substantially overlap, and sb_store's many named actions overlap with specialized tools like sb_add, sb_bind, sb_event, and sb_template_use. Descriptions help clarify boundaries, but selection is not always crisp.
Naming Consistency3/5
All tools use an sb_ prefix and snake_case, which is readable, but the naming grammar is mixed: pure verbs (add, set, move), noun_verb forms (media_upload, page_list, api_find), and plain nouns (event, theme, store). This is not a predictable verb_noun pattern, though it remains understandable.
Tool Count2/5
33 tools is high for one MCP surface; while the domain is broad, several tools could be consolidated (connect/site_list, import/import_site, and the sb_store mega-tool). This exceeds the 25+ threshold associated with excessive tool count.
Completeness4/5
The surface covers the main lifecycle: login/list sites, create/open/read/edit pages and nodes, media upload/list, templates, binding/events, publish, state, review, look, undo, import, and store flows via sb_store. Gaps like explicit page delete, site create/delete, and media delete are mitigated by sb_api_find/sb_api_call reaching the full API, so the surface is broadly complete with minor workarounds.
Maintenance
ActivityMaintained
ResponsivenessNo issues