A
licenseB
qualityA
maintenanceEnables AI assistants to build, validate, and publish storefront pages to WebCake/StoreCake sites based on natural language descriptions.
135
203 npm
4
MIT
WebCake Landing MCP
by vuluu2k
Related Servers
Alternatives to WebCake Landing MCP
No user-submitted related servers found.
Related Servers
Zarla MCP serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to build, edit, preview, and publish websites through natural language, including managing pages, designs, products, and site publishing.MIT
Buildez MCP Serverofficial
AlicenseAqualityDmaintenanceEnables AI assistants to build complete, live websites from natural language descriptions by connecting to Buildez.ai.116 npm1MIT- AlicenseBqualityCmaintenanceEnables AI assistants to scaffold, edit, live-preview, and deploy full-stack apps with built-in database, email, and push notification capabilities through natural language.19MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with web applications through DOM inspection, user interaction simulation, and application state management.MIT
- 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.-
TDQS
A3.9/5.0
Scored across 23 tools
Disambiguation3/5
Most tools are action-specific, but several pairs overlap: find_pages mirrors list_pages with no filters, get_element returns sparse element skeletons much like new_element, and update_page/patch_page/add_section all mutate pages at different granularities. The long descriptions help disambiguate, but an agent could still select the wrong one.
Naming Consistency4/5
Nearly all tools use snake_case verb_noun naming (list_pages, get_eement, create_page, upload_images), and get_/ list_/ create_ / patch_ verbs consistently encode their role. Minor deviations are 'new_element'/'new_page_skeleton' using 'new' instead of 'create', and 'layout' standing alone as a bare noun.
Tool Count3/5
At 23 tools, the surface is in the heavy 16-25 range for a single MCP server. The count is largely justified by the full build pipeline — ingestion, assets, layout, validation, persistence, publishing — but it could be trimmed by consolidating find_pages/list_pages or new_element/get_element.
Completeness3/5
The build/clone workflow is well covered: reference ingestion, asset handling, element construction, validation, layout math, and page persistence/publishing are all present. However, there is no delete_page tool, and no domain-management tool for attaching or listing custom domains needed for permanent public URLs, so the lifecycle has notable gaps.
Maintenance
ActivityMaintained
ResponsivenessNo issues