mcp-page-authoring
Best practices for authoring a Classic Unbounce landing page from HTML/CSS/JS through Unbounce MCP — create_page_from_html, create_variant_from_html, and update_variant_from_html. Use when the user asks for a Classic or custom-HTML page, when a new page needs something the AI Builder catalog cannot express (a bespoke interactive widget, custom page-level JavaScript), when the account does not have AI Builder, or to edit or add a variant to a page already authored through these HTML tools; also to personalize page text by URL parameter (Dynamic Text Replacement). A new page otherwise goes through the mcp-ai-builder-authoring skill. Not for AI Builder pages or pages hand-built in the Unbounce builder.
Install
With your agent
Install OMGSkills skill "unbounce/agent-plugins:plugins/unbounce-mcp/skills/mcp-page-authoring" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/unbounce/agent-plugins /tmp/agent-plugins && ln -s /tmp/agent-plugins/plugins/unbounce-mcp/skills/mcp-page-authoring ~/.claude/skills/mcp-page-authoringFrom README
Authoring an Unbounce MCP page These rules apply when you write the HTML/CSS/JS body for createpagefromhtml, createvariantfromhtml, or updatevariantfromhtml. The page is a full-bleed custom-HTML page — you own the markup end to end. Design the page to be optimized for conversions: by default, every layout, copy, and hierarchy decision should serve the page's single conversion goal. This covers MCP-authored pages only, and the split is exclusive both ways: A page hand-built in the Unbounce builder is not editable this way — updatevariantfromhtml refuses it. Replicating or modernizing a builder-built page is a different, audit-first job. An MCP-authored page cannot be edited in the Unbounce builder. Never tell the user they can open, tweak, swap images, or finish the page "in the Unbounce builder/editor" — they cannot. Every edit goes through these MCP tools: the user asks for the change, or supplies updated HTML.