Webcake Landing

Name: Webcake Landing
Author: vuluu2k

by vuluu2kversion 1.7.0i★ –iComputer or cloud

Registry nameio.github.vuluu2k/webcake-landing-mcp

Install

Overview

Description from the maker (original English)

Build, validate, and persist Webcake landing-page source JSON: element schemas plus AI usage hints.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiEarly↓ 785/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Developer tools
You need to fill in: WEBCAKE_JWT, PEXELS_API_KEY, Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: WEBCAKE_JWT, WEBCAKE_ENV, WEBCAKE_API_BASE, WEBCAKE_ORG_ID, PEXELS_API_KEY, Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "webcake-landing": {
      "command": "npx",
      "args": [
        "-y",
        "webcake-landing-mcp"
      ],
      "env": {
        "WEBCAKE_JWT": "your-value",
        "WEBCAKE_ENV": "your-value",
        "WEBCAKE_API_BASE": "your-value",
        "WEBCAKE_ORG_ID": "your-value",
        "PEXELS_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http webcake-landing https://mcp.toolvn.io.vn/mcp --header 'Authorization: your-value'

Or run it on your computer

claude mcp add webcake-landing --env WEBCAKE_JWT=your-value --env WEBCAKE_ENV=your-value --env WEBCAKE_API_BASE=your-value --env WEBCAKE_ORG_ID=your-value --env PEXELS_API_KEY=your-value -- npx -y webcake-landing-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "webcake-landing": {
      "url": "https://mcp.toolvn.io.vn/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "webcake-landing": {
      "command": "npx",
      "args": [
        "-y",
        "webcake-landing-mcp"
      ],
      "env": {
        "WEBCAKE_JWT": "your-value",
        "WEBCAKE_ENV": "your-value",
        "WEBCAKE_API_BASE": "your-value",
        "WEBCAKE_ORG_ID": "your-value",
        "PEXELS_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "webcake-landing": {
      "type": "http",
      "url": "https://mcp.toolvn.io.vn/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "webcake-landing": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "webcake-landing-mcp"
      ],
      "env": {
        "WEBCAKE_JWT": "your-value",
        "WEBCAKE_ENV": "your-value",
        "WEBCAKE_API_BASE": "your-value",
        "WEBCAKE_ORG_ID": "your-value",
        "PEXELS_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

WEBCAKE_JWT secret env
Webcake backend JWT; required only for the persistence tools (create/update/list pages).
WEBCAKE_ENV env
Webcake environment preset that fills the API/app/builder base URLs.
WEBCAKE_API_BASE env
Override for the Webcake API base URL (takes precedence over WEBCAKE_ENV).
WEBCAKE_ORG_ID env
Default Webcake organization id for the persistence tools.
PEXELS_API_KEY secret env
Optional Pexels API key for search_images; without one a shared hosted proxy is used.
Authorization secret HTTP header
Bearer ; required only for the persistence tools (create/update/list pages).

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account vuluu2k, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 347 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Developer toolsi

More stars than 0% of the other 5578 servers in this category
Published to the registry more recently than 79% of the other 5578 servers in this category
Basic checks equal to or better than 100% of the other 5578 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Webcake Landing safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: WEBCAKE_JWT, PEXELS_API_KEY, Authorization

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.7.0) reached the registry 4 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

by githubWidely used★ 34.2KUpdated 6 days ago

Computer or cloud

Install

Desktop Commander

MCP server for terminal commands, file operations, and process management

by wonderwhy-erWidely used↓ 709.6K/wk★ 10.2KUpdated 18 days ago

Runs on your computer

Install

Cloudflare MCP

Cloudflare MCP servers

by cloudflareWidely used★ 4.4KUpdated 14 months ago

Runs in the cloud✓ mcp.cloudflare.com

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

WebCake Landing MCP

English · Tiếng Việt

Describe a landing page in plain words — your AI builds it, checks it, and ships it straight to WebCake.

⭐ If this saves you an afternoon of dragging boxes, [give it a star](https://github.com/vuluu2k/webcake-landing-mcp) — it's a one-dev project and every star keeps it alive.

*"Build a landing page for my coffee shop — a hero with a sign-up button, a 3-feature section, and a lead form. Save it to my workspace."*

…and a real, editable WebCake page appears in your account. No dragging boxes, no learning the schema, no hand-writing JSON.

🧩 How it works

This server is the bridge between your AI assistant and WebCake. The AI never *guesses* what a WebCake page looks like — it asks this MCP, which knows the entire element model, validates the result, and saves it for you.

   You              AI assistant            webcake-landing MCP            WebCake

┌──────┐ prompt ┌────────────┐ tools ┌──────────────────────┐ API ┌──────────┐ │ idea │ ───────► │ Claude / │ ──────► │ • knows the element │ ────► │ a real │ │ │ │ Cursor / │ │ model + AI hints │ │ editable │ │ │ ◄─────── │ Windsurf │ ◄────── │ • builds + validates │ ◄──── │ page in │ └──────┘ page URL └────────────┘ result │ • saves to your acct │ │ WebCake │ └──────────────────────┘ └──────────┘

You ask in plain language — goal, brand, sections, CTA, form fields.
The AI learns the model from the MCP: the element catalog, the absolute-positioning canvas, the event vocabulary — so it builds a *real* WebCake page, not a guess.
It assembles + validates the full { page, popup, settings, options } JSON. validate_page catches off-canvas boxes, dangling CTAs, and missing form fields before anything is saved.
It persists to your WebCake account — dry-run preview first, then for real.
You get an editor link — open it, tweak, publish. The AI did the heavy lifting.

Why it's reliable


📚 Knows the real model	Serves WebCake's actual element catalog (40+ types — hero, form, countdown, gallery, product list…), each with its exact `specials` and AI hints, drawn straight from the editor's renderers.
✅ Validates before saving	Structural + semantic checks (unique ids, on-canvas layout, working CTAs, unique form fields) so the page isn't broken when it lands.
🛡️ Safe by default	Every write is dry-run first (preview the request, token masked) — nothing touches your account until you confirm.
✏️ Edits surgically	Ask for one change ("make the CTA green") and it edits only that element — every other id, coordinate, and block stays exactly as it was.

💡 Lead-gen, events, invitations, app promos — or selling COD/online? It speaks WebCake's commerce model too (product lists, variations, cart).

✨ What you can build

One sentence to your AI → a finished, editable WebCake page. A taste of what people ship with it:

	Just say…
🧲 Lead-gen landing	"A SaaS waitlist page — hero, 3 benefits, an email-capture form."
🛒 COD / online store	"A one-product page for my skincare serum — gallery, price, variations, an order form with cart."
🎟️ Event / webinar	"A registration page for Saturday's webinar — countdown, agenda, sign-up form."
💌 Invitation	"A wedding invite — names, date, a map, an RSVP form."
📱 App promo	"A page for my fitness app — phone mockups, feature list, App Store + Google Play buttons."
⚡ Flash sale	"A flash-sale page — big countdown, discounted product grid, a sticky Buy button."
🔗 Link-in-bio	"A link-in-bio for my creator profile — avatar, short bio, 5 link buttons, socials."
🎉 Product launch	"A launch page for v2 — hero, what's-new list, an early-access form."

…then "make the CTA green" or "add a 4th feature" and it edits *only* that block — every other id and coordinate stays exactly where it was.

🤖 Works in Claude Desktop, Claude Code, Cursor, Windsurf, Augment, Codex, Antigravity, Gemini CLI, Cline, Kiro, OpenCode, or any MCP-capable client — and the reference + generation tools need zero setup, so you can try it before ever pasting a token.

Under the hood

MCP (Model Context Protocol) server that teaches AI agents how to build a complete WebCake landing-page source JSON from a requirement — and persist it to a WebCake backend.

It exposes the element catalog, per-element usage hints + specials, the full page JSON Schema, valid element/page skeletons, a page validator, and tools to create or edit pages on the backend. The AI agent produces the full { page, popup, settings, options, cartConfigs } JSON; create_page persists it and auto-publishes (build + publish_html) so the preview renders immediately (the edit tools save source-only — re-publish via publish_page after edits).

Method	Best for	Auth
npx (local) — runs on your machine	Personal daily use, full control	browser `login`, a JWT, or none (reference tools)
Hosted URL — use our live server, nothing to install	No Node.js, teams, the claude.ai dialog	your personal `?jwt=` link / `x-webcake-jwt` header

The reference + generation tools (get_generation_guide, list_elements, validate_page, …) and the ingest tools (ingest_html, ingest_url — turn an existing HTML or URL into a layout anchor so the AI can recreate or adapt it) work with zero config; only the persistence tools (create_page, update_page, add_section, patch_page, publish_page, list_pages, find_pages, get_page, list_organizations) need a token. Credentials resolve in order: per-request header → env var → saved `auth.json` (login).

🚀 Get connected — the 2 main ways

Pick one. Both hand your AI tool (Claude, Cursor, …) the full Webcake landing toolkit. No coding.

① `npx` — runs on your machine (recommended for personal use)

Zero install, always the latest version, needs Node.js 18+. One line grabs your token *and* writes the IDE config:

# Opens the browser — click Connect, your installed IDEs are configured (prod)

npx -y webcake-landing-mcp install

Developers only — step by step: environment, login or JWT, org, IDE(s)

npx -y webcake-landing-mcp install --dev

Scripts and CI — every supported IDE, even ones not installed yet

npx -y webcake-landing-mcp install --ide all --jwt

Remove the server from every IDE config

npx -y webcake-landing-mcp uninstall

`install` asks nothing. It connects to production, opens your browser so you can click *Connect*, then adds the server to every AI app it finds on this computer. Your other servers are kept, and any config file it changes is backed up next to the original as .webcake-landing-backup. No AI app found? It says so and exits with an error: install one and run it again, or name it with --ide.

Need staging or local? --dev opens the step-by-step wizard, or skip it with --env staging / --env local.

Installed with an older version? Run install again. Older versions wrote VS Code's config under the wrong key, so the

server never appeared there, and registered Claude Code for the current folder only.

It writes a webcake-landing entry into the right config file for each target: claude-desktop, claude-code, cursor, windsurf, augment (VS Code), codex, antigravity, gemini (Gemini CLI), cline, kiro, opencode, or all. Flags: --dev, --ide, --env, --jwt, --org-id, --api-base/--app-base, --npx/--local, -y — see install --help.

Just want to run the server (configure by hand later)? npx -y webcake-landing-mcp

🛠️ Hand-written per-IDE config, shell-script installers (install.sh/install.ps1), or a cloned

local build → [docs/manual-install.md](docs/manual-install.md).

② Remote URL `…/mcp?jwt=` — hosted, nothing to install

The server is already live at https://mcp.toolvn.io.vn/mcp — no Node.js, no machine to keep awake. Grab your personal link (your token is baked in) and paste it into your client's *Add custom connector* / config:

https://mcp.toolvn.io.vn/mcp?jwt=<YOUR_TOKEN>

Two ways to get the link:

Easiest — open [https://webcake.io/mcp-remote](https://webcake.io/mcp-remote) in your Webcake dashboard → it builds & copies the link for you.
By hand — see the step-by-step guide: [docs/connect-mcp.md](docs/connect-mcp.md).

Optional extras: &env=prod, &org_id=…, &api_base=…. Hand each teammate a link with their own jwt → per-user, no OAuth. Clients that support headers should send the token as `x-webcake-jwt` instead of putting it in the URL — the full header ↔ env mapping is in [docs/configuration.md](docs/configuration.md#per-request-headers-hosted--remote-server).

✅ Best for: no Node.js, team/shared use, the claude.ai connector dialog (URL-only, no headers). ⚠️ The link contains your personal token — treat it like a password, always use HTTPS.

⚙️ Configuration

The quick version — only the persistence tools need any of this:

npx -y webcake-landing-mcp login    # opens the browser once, saves the token to ~/.webcake-landing-mcp/auth.json

…or set WEBCAKE_ENV (local | staging | prod — fills in all base URLs) + WEBCAKE_JWT.

For publish_page to actually put a page live, a build host is needed (it renders the app/app_css that the live publish_html route requires):

prod preset auto-configures https://build.webcake.io — no extra setup (the preset applies when the env resolves to prod: WEBCAKE_ENV=prod, --env prod, or x-webcake-env: prod).
For staging/local, set WEBCAKE_BUILD_BASE= or send the x-webcake-build-base header per request.
Without it, publish_page falls back to a legacy source-only save with rendered:false, live:false + a warning — nothing goes live.
A page is only permanently live with a custom_domain; without one the returned /preview/ link expires ~10 minutes after the publish.

Everything else — the full env-var table, environment presets, per-request headers for the hosted server, the login browser flow (+ backend contract), and how to grab a JWT by hand — lives in [docs/configuration.md](docs/configuration.md).

📚 Docs

Guide	What's inside
[Connect your IDE / claude.ai](docs/connect-mcp.md)	Step-by-step connection for every client (npx & hosted URL), troubleshooting table.
[Configuration](docs/configuration.md)	Env vars, `--env` presets, browser `login`, per-request headers, getting a JWT.
[Tools reference](docs/tools.md)	All 23 tools in detail + the step-by-step workflow + model notes.
[Usage examples](docs/usage-examples.md)	Three end-to-end walkthroughs: build from a brief, surgical edit, inspect a type.
[Manual / advanced install](docs/manual-install.md)	Shell installers, cloned builds, hand-written per-IDE config.

| **[Page-element schema](docs/page-el

Only the beginning is shown; read the rest in the repo

Webcake Landing

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

WebCake Landing MCP

🧩 How it works

Why it's reliable

✨ What you can build

Under the hood

🚀 Get connected — the 2 main ways

① npx — runs on your machine (recommended for personal use)

Developers only — step by step: environment, login or JWT, org, IDE(s)

Scripts and CI — every supported IDE, even ones not installed yet

Remove the server from every IDE config

② Remote URL …/mcp?jwt= — hosted, nothing to install

⚙️ Configuration

📚 Docs

① `npx` — runs on your machine (recommended for personal use)

② Remote URL `…/mcp?jwt=` — hosted, nothing to install