
Create Web Page
Create Web Page is an MCP server that lets agents create, edit, preview, publish, and manage web pages end to end.
About
Create Web Page MCP is a hosted Model Context Protocol server that lets AI-assisted developers treat web pages as agent-managed artifacts: create drafts, edit copy and structure, preview renders, publish live, and manage existing pages without juggling a separate site builder UI for every tweak. founders use it heavily in Validate when they need a credible landing page, pricing teaser, or experiment page to test demand, and it remains useful in Build when documentation or lightweight marketing surfaces need fast iteration. The registry exposes a streamable HTTP endpoint at create-web-page.com with official MCP documentation and UTM-tracked discovery metadata, which signals a productized service rather than a one-off script. Complexity stays beginner-friendly because the mental model is pages in/out of your agent thread, not infra provisioning. Connect the remote in your MCP settings, then direct the agent to spin up or update pages as part of validation or launch checklists.
- Full page lifecycle: create, edit, preview, publish, and manage from MCP clients
- Streamable HTTP remote at create-web-page.com/mcp
- Registry docs and distribution plan at create-web-page.com/docs/mcp
- GitHub source daniel-lopez-puig/landings for transparency
- Brand icons for light and dark themes in registry metadata
Create Web Page by the numbers
- Exposes 23 verified tools (MCP introspection)
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http create-web-page https://create-web-page.com/mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | None |
| Tools | 23 |
What it does
Create, preview, and publish marketing or validation pages from Claude Code or Cursor without leaving the agent loop.
Who is it for?
Best when you want agent-native landing pages, smoke-test sites, and light marketing pages with minimal frontend setup.
Skip if: Deep mortgage pricing integrations, specialized legal datasets, or teams needing full custom app backends only.
What you get
Pages move from draft to published inside MCP-driven sessions so you can validate ideas and ship surface area faster.
- Created and edited web page drafts with preview URLs
- Published pages ready for validation traffic or launch distribution
By the numbers
- Registry version 0.1.0
- 1 streamable-http remote at create-web-page.com/mcp
- Repository source github.com/daniel-lopez-puig/landings
Tools 23
Public tool metadata - what this server can do for an agent.
account.whoamiReturn the current Create Web Page account context. Use this to check whether the user is authenticated or using an anonymous expiring demo.
page.intake.start7 paramsRECOMMENDED first step for building a page. Returns the few questions worth asking (business name, primary visitor action, key content, optional source link) so you can then call page.create_from_brief. This is the simplest, most reliable path — prefer it. (page.onboarding.* offers extra category/layout/palette pickers but is a stateless planning helper, not required.) Call once per creation request; skip if the user already gave you a source URL. Does not create a page.
originalRequeststringThe user's original page-creation request, copied verbatim when available.businessNamestringOnly include if the user already provided the business or project name.businessTypestringBusiness category inferred from the user's words, such as hamburger restaurant or dental clinic.sourceUrlstringPublic HTTP/HTTPS source URL provided by the user, such as a business website or link-in-bio page. Protected platforms (social networks, maps, paywalls) require client-side browsing or pasted details instead.sourceHandlestringPublic social handle provided by the user.primaryGoalstringThe main visitor action if known, such as book, call, WhatsApp, buy, or leave a lead.localestringPreferred content locale if obvious from the conversation.
page.onboarding.start3 paramsOptional planning helper that returns category/layout/palette/primary-action choices and a quality checklist (it does NOT create a page). Use it only if you want those pickers; otherwise page.intake.start → page.create_from_brief is the simpler path. IMPORTANT: this flow is STATELESS — page.onboarding.update does not remember earlier calls, so each update must resend the FULL set of selections + knownFields gathered so far. As soon as you have a business name and a primary action, stop and call page.create_from_brief (you do not need to reach a 'ready' step).
originalRequeststringlocalestringPreferred UI locale, such as es or en.suggestedSelectionobject
page.onboarding.update4 paramsValidate onboarding selections and return the remaining checklist. STATELESS: it does not remember previous calls, so every call must include the FULL accumulated selection (mainCategory, subCategory, layout, palette, primaryAction) plus all knownFields (name, description, action destination, etc.) gathered so far — not just the latest answer, or earlier choices will look 'missing'. You do not need to loop to a 'ready' state: once you have a name and a primary action, call page.create_from_brief with those values.
stepIdstringlocalestringselectionobjectknownFieldsobject
source.import2 paramsFetch a public website URL and extract a structured brief with business name, description, contact links, and suggested page blocks. Only works with public HTTP/HTTPS pages. Does not bypass login, CAPTCHA, or paywalls. Returns extracted fields and suggestedBlocks for use with page.create_from_brief.
sourceUrlstringrequiredPublic http/https source URL to import.localestringPreferred output locale if obvious from the conversation, such as es or en.
page.create9 paramsCreate a hosted link-in-bio page draft from a style preset. Provide title, displayName, and a preset (or 'auto' to infer from businessType/style). The page starts with empty placeholder blocks for you to fill in via block.update — do not invent content. This tool intentionally creates a draft only and does not return a publish action. After calling it, stop and show the preview URL. Do not call page.publish in the same turn unless the user's current message explicitly asks to publish, make the page live, or get a public share link. Anonymous demo pages expire unless claimed.
titlestringrequiredInternal page title and default header display_name.displayNamestringVisible header display name. Defaults to title.biostringOptional short bio for the header.businessTypestringUsed by preset:auto inference. Examples: musician, restaurant, designer.slugstringPreferred public URL slug.layoutstringLayout id. Defaults to 'link_in_bio'.presetstringrequiredStyle preset id, or 'auto' to infer deterministically from businessType/style.stylestringFree-form style hint used by preset:auto inference.initialPromptstring
page.create_from_brief29 paramsCreate a hosted landing page draft from a structured brief. Accepts business name, category, layout, palette, primary action, explicit final-audience publicSections, and optional hero image. Planning fields such as audience, offer, primaryGoal, location, businessType, style, and mustInclude are context only and are not rendered as public body copy. Draft previews are customer-facing: do not pass owner instructions, section-planning labels, or placeholder copy as public content. Keep sparse briefs sparse: use only facts supplied by the user or imported public sources, plus light wording polish; do not invent menus, services, hours, facilities, locations, testimonials, guarantees, staff details, prices, or operational claims. Prefer one short section or no extra section when the prompt is minimal. If a requested CTA lacks its real destination, ask for it before creation or provide fallbackLeadForm with public copy. Returns a preview URL, edit token, and next-step hints. This tool intenti
businessNamestringrequiredbiostringOptional short bio for the header.businessTypestringPlanning context only. Not rendered directly as public page copy.preferredSlugstringDesired URL path. Ask the user for it near the end of onboarding. Use normal letters, numbers, and hyphens; the server normalizes and makes it unique.layoutstringDefaults to 'link_in_bio'.presetstringStyle preset id, or 'auto' to infer deterministically. Defaults to 'auto'.sourceUrlstringProvenance reference only.sourceHandlestringprimaryGoalstringPlanning context only. Not rendered directly as public page copy.audiencestringPlanning context only. Not rendered directly as public page copy.offerstringPlanning context only. Not rendered directly as public page copy; use bio and publicSections for final-audience copy.locationstringPublic business address or service area intended for map/address actions, not direct body copy and not the user's private/current location.publicWhatsappstringPublic WhatsApp phone number explicitly supplied by the user or a public source. Do not use the user's account phone or invent placeholder numbers.publicPhonestringPublic business phone number explicitly supplied by the user or a public source. Do not use the user's private/account phone.publicBusinessEmailstringPublic business contact email explicitly supplied by the user or a public source. Do not use the user's ChatGPT/account email.stylestringPlanning context only. Not rendered directly as public page copy.mustIncludearrayPlanning checklist only. Do not put section names, CTA labels, owner instructions, or private notes here; not rendered directly.publicSectionsarrayFinal-audience text sections to render on the public page. Write in the target language with correct spelling/accents. Only include facts the user supplied or that came from an imported public source; for sparse prompts, keep this short and avoid invented service lists, hours, benefits, testimonials, prices, or operational details.initialPromptstringlocalestringonboardingMainCategorystringValidated atom.bio category id from page.onboarding.*, for example physical-business or online-business.onboardingSubCategorystringValidated atom.bio subcategory id, for example health.onboardingLayoutstringLayout style: background_color (minimalist), full (featured photo), or background_image (full image background).onboardingPalettestringPalette id returned by page.onboarding.* paletteChoices, for example atom_dark_plum.primaryActionIdstringprimaryActionLabelstringPublic label for the primary action in the page's target language.fallbackLeadFormobjectPublic fallback contact/interest form to use when the requested primary action lacks a real destination. All copy must be final-audience copy in the page's target language.primaryActionUrlstringReal destination URL for the primary action when explicitly supplied by the user or imported public source, such as a booking link. Do not invent booking/order URLs; if missing, ask for it or use fallbackLeadForm.heroImageUrlstringExplicit user-provided image URL for featured-photo or full-image styles.
block.add3 paramsAppend a new content block to a link-in-bio page. The block must match one of the 13 allowed types (link, social_row, whatsapp, phone_call, email_contact, image, gallery, video_embed, text, map_embed, product_card, lead_form, reviews) with that type's strict props. The server generates the block id and returns it in the response. For already-published pages, this saves an unpublished latest revision only. Do not call page.publish in the same assistant turn after this edit. Stop and tell the user the draft/preview was updated, then wait for a separate user message that explicitly asks to update the live link, publish, or make the changes public before calling page.publish. Do NOT call page.unpublish either — the live page should stay public; only unpublish when the user explicitly asks to take it down. The response includes nextSteps: after adding a block, share these hints with the user so they know what else would make the page more complete.
pageIdstringrequirededitTokenstringblockobjectrequiredThe block to add. Must match one of the 13 allowed types with that type's strict props schema. The server generates the block id.
layouts.listList supported page layouts. v1 ships link_in_bio only.
presets.listList the 8 curated style presets (theme + starter blocks) for link-in-bio. Use to offer the user a choice or to confirm a preset:auto selection.
page.get2 paramsRead a landing page draft, including its latest content JSON. For anonymous demo pages, include the editToken.
pageIdstringrequirededitTokenstring
page.claim2 paramsClaim an anonymous demo page into an AUTHENTICATED account. This requires the signed-in user's OAuth — an anonymous chat/agent session cannot call it and will get an OAuth-required error. So in a normal agent conversation, do NOT call this to 'save' a demo page: instead share the claimUrl from the page.create/page.publish result with the user, who opens it, signs in, and keeps the page. Only call page.claim when the request already runs under the owner's OAuth.
pageIdstringrequiredThe pageId returned by page.create.editTokenstringrequiredThe editToken returned by page.create for the anonymous demo page.
account.pages.list1 paramList landing pages claimed by the authenticated account. This requires OAuth and is for account management, not first-time demo creation.
limitnumberMaximum number of claimed pages to return.
account.page.manage1 paramRead a claimed account page without requiring an editToken. Use after OAuth when the user wants to manage a durable website.
pageIdstringrequiredThe claimed pageId to manage.
page.header.update6 paramsUpdate the link-in-bio page header: displayName, bio, verified checkmark, and QR display. Use only the fields you want to change. For already-published pages, this saves an unpublished latest revision only. Do not call page.publish in the same assistant turn after this edit. Stop and tell the user the draft/preview was updated, then wait for a separate user message that explicitly asks to update the live link, publish, or make the changes public before calling page.publish. Do NOT call page.unpublish either — the live page should stay public; only unpublish when the user explicitly asks to take it down.
pageIdstringrequirededitTokenstringdisplayNamestringVisible display name in the page header.bioShort bio under the display name. Pass null to clear it.verifiedbooleanShow a verified checkmark next to the display name.showQrbooleanShow a QR code for this page.
page.theme.update3 paramsApply a partial theme patch. Theme fields are enum-constrained (button variant/radius/shadow, font family/weight, density, icon_size). Use presets.list first if the user wants a complete restyle. For already-published pages, this saves an unpublished latest revision only. Do not call page.publish in the same assistant turn after this edit. Stop and tell the user the draft/preview was updated, then wait for a separate user message that explicitly asks to update the live link, publish, or make the changes public before calling page.publish. Do NOT call page.unpublish either — the live page should stay public; only unpublish when the user explicitly asks to take it down.
pageIdstringrequirededitTokenstringthemeobjectrequiredPartial theme patch. Provide only fields you want to change.
page.meta.update6 paramsUpdate internal page title, URL slug, and SEO title/description. For already-published pages, this saves an unpublished latest revision only. Do not call page.publish in the same assistant turn after this edit. Stop and tell the user the draft/preview was updated, then wait for a separate user message that explicitly asks to update the live link, publish, or make the changes public before calling page.publish. Do NOT call page.unpublish either — the live page should stay public; only unpublish when the user explicitly asks to take it down.
pageIdstringrequirededitTokenstringtitlestringInternal page title shown in editor results.slugstringPreferred public URL slug.seoTitlestringSEO <title> tag value.seoDescriptionstringSEO meta description value.
page.preview2 paramsReturn the current preview URL for a page.
pageIdstringrequiredThe pageId returned by page.create.editTokenstringRequired for anonymous demo pages. Use the editToken returned by page.create.
page.publish2 paramsPublish the latest page revision. Call this only when the user's latest message explicitly asks to publish, make the page live, or get a public share link. Do not call this immediately after page.create or page.create_from_brief just because the draft is publish-ready. For anonymous demo pages, include the editToken returned by page.create. The response includes nextSteps: always share these with the user after publishing — they include the claim reminder and any remaining improvements.
pageIdstringrequiredThe pageId returned by page.create.editTokenstringRequired for anonymous demo pages. Use the editToken returned by page.create.
page.unpublish2 paramsRemove a published landing page from public availability while keeping its draft and revision history.
pageIdstringrequirededitTokenstring
block.updatePatch one content block by stable blockId. Provide a props patch (merged into existing props) and/or a new type. Block types and props are validated against the strict per-type schema. For already-published pages, this saves an unpublished latest revision only. Do not call page.publish in the same assistant turn after this edit. Stop and tell the user the draft/preview was updated, then wait for a separate user message that explicitly asks to update the live link, publish, or make the changes public before calling page.publish. Do NOT call page.unpublish either — the live page should stay public; only unpublish when the user explicitly asks to take it down.
block.delete3 paramsDelete one block by stable blockId. Use page.get first if unsure which id to remove. For already-published pages, this saves an unpublished latest revision only. Do not call page.publish in the same assistant turn after this edit. Stop and tell the user the draft/preview was updated, then wait for a separate user message that explicitly asks to update the live link, publish, or make the changes public before calling page.publish. Do NOT call page.unpublish either — the live page should stay public; only unpublish when the user explicitly asks to take it down.
pageIdstringrequirededitTokenstringblockIdstringrequired
block.reorder4 paramsMove a block to a new zero-based index in the page main slot. For already-published pages, this saves an unpublished latest revision only. Do not call page.publish in the same assistant turn after this edit. Stop and tell the user the draft/preview was updated, then wait for a separate user message that explicitly asks to update the live link, publish, or make the changes public before calling page.publish. Do NOT call page.unpublish either — the live page should stay public; only unpublish when the user explicitly asks to take it down.
pageIdstringrequirededitTokenstringblockIdstringrequiredtoIndexnumberrequired
Recommended MCP Servers
How it compares
Hosted page lifecycle MCP integration, not a backlink analytics server or local static-site generator skill.
FAQ
Who is Create Web Page MCP for?
Developers and agents who publish and iterate web pages from Claude Code, Cursor, or other MCP clients.
When should I use Create Web Page MCP?
When validating an idea with a landing page, updating launch copy, or managing lightweight sites during build and ship.
How do I add Create Web Page MCP to my agent?
Add https://create-web-page.com/mcp as a streamable-http MCP remote per create-web-page.com/docs/mcp and restart the client.