A
licenseB
qualityA
maintenanceEnables AI assistants to build, validate, and publish storefront pages to WebCake/StoreCake sites based on natural language descriptions.
131
534 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.18 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 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
A4/5.0
Scored across 23 tools
Disambiguation4/5
Most tools target a clearly distinct resource+action, and the verbose descriptions explicitly clarify boundaries (e.g. update_page replaces the whole source while patch_page edits by element id, add_section appends). A few adjacent pairs create mild overlap — list_pages vs find_pages, and the validate_page step that is already embedded in create/update/publish — but an agent can still tell them apart.
Naming Consistency4/5
The surface is overwhelmingly consistent snake_case verb_noun (get_page, create_page, update_page, publish_page, ingest_url, search_images). Minor deviations: 'layout' is a bare noun, 'new_element'/'new_page_skeleton' use 'new' instead of 'create', and 'search'/'find' are used for the same lookup concept — readable but not perfectly uniform.
Tool Count4/5
23 tools is on the heavy side and sits in the 16-25 'feels heavy' band, but the domain (ingest, build, validate, layout, media, icon, publish lifecycle) is genuinely broad and each tool maps to a distinct capability with little redundancy. Slightly over-scoped rather than bloated.
Completeness4/5
Strong lifecycle coverage: create, read (get/list/find), update, patch, add_section, validate, publish, plus ingest and asset tooling. The notable gap is deletion — there is no delete_page or unpublish tool, so cleanup/lifecycle teardown is a dead end that agents cannot reach.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive