WebCake Storefront MCP
Related Servers
Alternatives to WebCake Storefront MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceBridges AI assistants to WebCake, enabling users to build, validate, and save editable landing pages from natural language descriptions.23715MIT
- AlicenseBqualityBmaintenanceEnables AI agents to operate a Store Builder site end-to-end — designing pages, filling them with data, reviewing screenshots, and publishing — without human intervention.315,023MIT

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
Buildez MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceEnables AI assistants to build complete, live websites from natural language descriptions by connecting to Buildez.ai.121MIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage git-backed website content through natural language, with tools to create, update, delete, and draft pages that are schema-validated and committed to a repository.01MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to generate 3D product viewers, AR try-on experiences, Shopify integrations, and SEO metadata for e-commerce stores.30MIT
TDQS
Scored across 135 tools
The tools are organized into recognizable families (pages, global sources/sections, products, CMS files, images) and most descriptions clarify scope well. However, the volume of near-parallel names such as get_source_cart vs get_global_source_detail, search_global_section_elements vs search_global_source_elements, and update_page_element(s) vs update_page_source means an agent has to read carefully to avoid picking the wrong variant.
Most tools follow a readable snake_case verb_noun pattern (list_*, get_*, create_*, update_*, delete_*). There are notable deviations like new_section/new_element/new_row instead of create_*, build_page vs create_page, edit_http_function vs update_http_function, and set_image_alts, but the overall style is still recognizable and not chaotic.
135 tools is far beyond a well-scoped surface and clearly falls in the extreme mismatch range. Even though WebCake covers many domains, the sheer number creates a heavy selection burden and overlaps with the on-demand search_tools/invoke_tool catalog.
The tool set covers an unusually broad set of workflows: pages, drafts, global sources/sections, products, categories, collections, CMS files, themes, apps, images, orders/customers/promotions reads, and publishing. There are some gaps such as native promotion mutation, global section editing, and CMS file deletion, but search_tools/invoke_tool and documented workarounds mitigate most dead ends.