Log inSubmit server
Webcake Landing logo

Webcake Landing

Build, validate, edit, and publish editable WebCake landing pages from natural-language requirements.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Webcake Landing

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "webcake-landing": {
      "command": "npx",
      "args": [
        "-y",
        "webcake-landing-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 23 tools correctly (Today).

Overview

Webcake Landing connects AI assistants to WebCake, exposing the platform’s landing-page element model, JSON schema, generation guidance, and persistence operations. It can assemble and validate complete page source, check layout and form semantics, then save or publish pages through the WebCake backend. Use it when an agent needs to create editable WebCake pages from descriptions, adapt an existing HTML page or URL, or make targeted page edits without rebuilding unrelated elements.

Use cases

  • Generate a lead-capture landing page from a product brief
  • Create a WebCake product page with variations and an order form
  • Recreate an existing HTML page as a WebCake layout
  • Validate page JSON before saving it to an account
  • Patch one landing-page section without changing other elements

Key features

  • WebCake element catalog with AI usage hints
  • Full landing-page JSON schema and valid skeletons
  • Structural and semantic page validation
  • Dry-run previews for account writes
  • HTML and URL layout ingestion
  • Page creation, editing, search, and publishing tools

Tools23

What Webcake Landing lets your agent do. Expand a tool for its parameters.

Verified live~9.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 48d

What it can do

From the 23 tools this server returned when we ran it; 23 declare their own safety hints.

Can delete or modify data · 3Handles credentials · 12Makes network requests · 15Read-only tools · 20
Network at startup3 connections
Files written at startupNone
Install scriptsprepare
npm provenanceNot published
Package age142 days
Maintainers1

Observed 2026-10-26 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · webcake-landing-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars7Stargazers on the source repository.
npm downloads1.5kPackage downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed23Callable tools this server registers over MCP.

How Webcake Landing works

What Webcake Landing does

Webcake Landing translates natural-language landing-page requirements into WebCake source JSON. The generated document can contain the page, popup, settings, options, and cart configuration structures used by WebCake. Agents can draw from the server’s element catalog, per-element usage guidance, supported specials, and page schema instead of guessing the editor’s data model.

The server covers common landing-page patterns such as lead-generation forms, event registrations, invitations, app promotions, product pages, flash-sale pages, and link-in-bio layouts. Its element model also includes commerce-related structures such as product lists, variations, carts, and order forms.

How it works

An MCP-capable client sends the user’s request to the server’s tools. Reference and generation tools provide the element definitions, valid skeletons, schema, and construction guidance. The agent then assembles a complete WebCake page and can pass it to validate_page before persistence.

Validation checks structural and semantic concerns including duplicate identifiers, elements positioned outside the canvas, unresolved calls to action, and missing or non-unique form fields. Ingest tools can turn existing HTML or a URL into a layout reference that an agent can recreate or adapt.

Writes use a dry-run preview before changing the account, allowing the request to be reviewed with the token masked. create_page saves a new page and publishes it so the preview renders immediately. Page editing tools save source changes; publish_page is used afterward to publish those edits. Targeted edits are intended to preserve unrelated element IDs, coordinates, and blocks.

Setup and configuration

The package can run locally with Node.js 18 or newer:

Terminal
npx -y webcake-landing-mcp install

The installer can configure supported IDEs interactively or accept options such as --ide, --env, --jwt, --org-id, --api-base, --app-base, --npx, and --local. Running npx -y webcake-landing-mcp starts the server without changing client configuration. Manual per-client configuration and local-build instructions are available through the project’s installation documentation.

A hosted streamable HTTP endpoint is also available at https://mcp.toolvn.io.vn/mcp. Connect with a personal link containing ?jwt=<YOUR_TOKEN>, or provide the token through the x-webcake-jwt header when the client supports request headers. The hosted option requires no Node.js installation.

Reference, generation, and ingest operations work without credentials. Persistence operations require a token. Credentials can be supplied per request, through server configuration, or through the saved login produced by the login flow. The installer can also configure a production or alternate environment and an organization ID.

Tools and capabilities

  • Retrieve generation guidance and the WebCake element catalog.
  • Inspect element schemas, usage hints, and supported specials.
  • Obtain valid element and page skeletons.
  • Validate complete page source before saving.
  • Convert HTML or a URL into a layout anchor with ingest_html or ingest_url.
  • Create, update, patch, and add sections to pages.
  • Publish pages and retrieve page URLs or source data.
  • List, search, and fetch pages with list_pages, find_pages, and get_page.
  • List available organizations with list_organizations.

The persistence tools include create_page, update_page, add_section, patch_page, and publish_page. The generation workflow can therefore support both first drafts and focused changes to an existing WebCake page.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Webcake Landing

Webcake Landing is an MCP server that connects AI assistants to WebCake’s landing-page backend. Its main tools expose element schemas and generation guidance, validate page JSON, ingest HTML or URLs, and create, edit, retrieve, or publish editable WebCake pages with optional authenticated persistence.

Install it with `npx -y webcake-landing-mcp install` on Node.js 18 or newer. The installer can configure supported clients interactively or with flags such as `--ide`, `--env`, and `--jwt`. You can also run `npx -y webcake-landing-mcp` and configure a client manually.

Yes. Use the hosted MCP endpoint at `https://mcp.toolvn.io.vn/mcp` with a personal `?jwt=<YOUR_TOKEN>` link. Clients that support custom headers can send the credential as `x-webcake-jwt` instead. This option runs remotely and requires no local machine process.

Yes. Cursor is listed among the supported clients and can be configured by the installer or manually. The server also supports a hosted MCP URL, so Cursor can connect remotely when its MCP configuration supports that connection method.

No. Reference, generation, and ingest tools work without credentials. Operations that persist or manage account pages, including creation, updates, patches, publishing, listing, searching, and retrieval, require a WebCake token.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWebcake Landing AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/webcake-landing?style=directory)](https://allmcps.com/mcp/webcake-landing)
HTML Embed
<a href="https://allmcps.com/mcp/webcake-landing"><img src="https://allmcps.com/api/badge/webcake-landing?style=directory" alt="Webcake Landing on AllMCPs" /></a>