Skip to content
Official MCP RegistryListed

Create Web Page

Part ofCreate Web Pagelisted on 2 directories

Create, edit, preview, publish, and manage web pages from MCP-capable AI clients.

First seen 2 Oct 2026. Evidence as of 7 Oct 2026.

27
Tools
From an anonymous probe
1
Source listings
Each with its own history
50
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
account_page_manageRead a claimed account page without requiring an editToken. Use after OAuth when the user wants to manage a durable website.Read-only
account_pages_listList landing pages saved to the signed-in account. Safe to call without sign-in: an anonymous chat gets ok=true, authenticated=false and an empty list (not an error) because it has no saved pages — then create the page directly with page_create_from_brief. Sign-in is only needed later to keep or manage a page.Read-only
account_whoamiReturn the current Create Web Page account context. Use this to check whether the user is authenticated or using an anonymous expiring demo.Read-only
block_addAppend a new content block to a link-in-bio page. The block must match one of the 14 allowed types (link, social_row, whatsapp, phone_call, email_contact, image, gallery, video_embed, text, map_embed, product_card, lead_form, reviews, save_contact) 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.Changes data
block_deleteDelete 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.Destructive
block_reorderMove 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.Changes data
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.Changes data
layouts_listList supported page layouts. Currently ships link_in_bio only.Read-only
media_attachAttach a ready media asset to the page. placement determines where: avatar (header), block_image (image inside a specific block — requires blockId), gallery_item (appended to a gallery — optional blockId targets a specific gallery; otherwise the first one is used), background (theme background).Changes data
media_deleteSoft-delete a media asset and remove all references to it from the page content.Destructive
media_uploadAdd an image to a page. PREFERRED for any image already on the web: pass its imageUrl and the server fetches it directly (no size limit, no attachment needed in chat). imageBase64 is ONLY for very small inline images — large base64 payloads are rejected by request-size limits and waste context, so never paste a photo's bytes; for a file on the user's device use media_upload_link_create instead. After a successful upload, call media_attach to place it (unless this returned content already showing it).Changes data
media_upload_link_createGet an upload link for a photo on the user's own device (phone/computer) — the right tool whenever the image is not already at a public URL. Pass pageId (+ editToken for demo pages) and the placement (e.g. header_photo). Then show the returned uploadPageUrl to the user as a clickable link and ask them to open it and pick their photo: the page resizes the image for the web automatically and attaches it to the page, so you do NOT call media_attach afterward. The link expires (see expiresAt). After the user says they've uploaded, call page_get to confirm the photo is on the page.Changes data
page_claimClaim 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.Changes data
page_createLow-level/legacy: create a blank link-in-bio scaffold from a style preset (title, displayName, preset or 'auto'). Not for normal page requests — use page_create_from_brief, which builds the page from the user's details. The scaffold starts with empty placeholder blocks to fill 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.Changes data
page_create_from_briefThe main tool for creating a page. Call it directly when the request already has the business/page name and the main visitor action with its real destination (WhatsApp number with country code, booking/order link, phone, address or email); if the request is vague, ask at most one round of questions first (page_intake_start lists them). Creates a private draft and returns previewUrl, pageId, editToken (anonymous pages), claimUrl and expiresAt. Planning fields (audience, offer, primaryGoal, location, businessType, style, 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; never invent menus, services, hours, facilities, locations, testimonials, guarantees, staff details, prices, or operational claims. If a requested action lacks its real destination, ask for it, or use fallbackLeadForm with destinationEmail (ask the user which email should receive enquiries — without it the form cannot deliver anything and cannot be the page's only action at publish). Personal, gift or event pages (birthday, invitation, tribute, a poem) need no contact form and no action at all: a page with real text (bio + publicSections) can be published as is; add a link (primaryActionUrl, e.g. RSVP, gift list or playlist) only if the user has one, never primaryActionId 'lead'. After calling it, show the preview URL and stop; call page_publish only when the user explicitly asks to publish, make it live, or get a public link. Anonymous pages are deleted after expiresAt unless the user claims them via claimUrl. Passing onboardingMainCategory picks the matching template. The draft also seeds the preset's starter blocks (empty placeholder links, social row, save-contact) — they never block publishing and are pruned if left empty. Use the returned previewUrl directly (no need for page_preview). nextSteps marked recommended/optional (bio, photo, social links) are improvements to offer after the user has seen the preview; only 'required' ones block publishing.Changes data
page_getRead a landing page draft, including its latest content JSON. For anonymous demo pages, include the editToken.Read-only
page_header_updateUpdate the link-in-bio page header: displayName, bio, verified checkmark, business-card display style ("photo_hero" large top photo or "avatar"), a short role label (e.g. "Barber · Madrid"), labelPosition, and the header photo (photoUrl; null removes it). 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.Changes data
page_intake_startOptional first step for a vague page request (e.g. 'make me a website for my barbershop'). Returns at most one round of questions to ask together: the name, the main visitor action AND where it goes (WhatsApp number with country code, booking/order link, phone or address), and must-have facts. Skip it when the request already has a name and the main action's destination — call page_create_from_brief directly. Call at most once per request; if the user gave a public link, read it yourself or use source_import instead. Does not create a page.Read-only
page_meta_updateUpdate 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.Changes data
page_onboarding_startGuided visual setup (category, layout, palette, primary action) that does NOT create a page. Use it ONLY when the user explicitly wants to choose the style/layout step by step; for normal requests call page_create_from_brief (asking at most one round of questions first). 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).Read-only
page_onboarding_updateValidate 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.Read-only
page_previewReturn the current preview URL for a page. You usually do not need this: page_create and page_create_from_brief already return a ready-to-open previewUrl. For an anonymous demo page you must pass the editToken from the create result; calling this with pageId alone fails.Read-only
page_publishPublish 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.Changes data
page_theme_updateApply 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.Changes data
page_unpublishRemove a published landing page from public availability while keeping its draft and revision history.Destructive
presets_listList the 12 curated style presets (theme + starter blocks) for link-in-bio. Use to offer the user a choice or to confirm a preset:auto selection.Read-only
source_importFetch 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.Read-only

Change history

  1. presets_list: description changed (+"12" -"8")
  2. page_unpublish: input schema changed
  3. page_theme_update: input schema changed
  4. page_publish: input schema changed
  5. page_preview: input schema changed
  6. page_onboarding_start: description changed (+"Guided visual setup (category, layout, palette, primary action)" +"page." +"ONLY when the user explicitly wants to choose the style/layout step by step; for normal requests call")
  7. page_meta_update: input schema changed
  8. page_intake_start: description changed (+"Optional" +"a vague page request (e.g. 'make me" +"website for my barbershop').")
  9. page_header_update: input schema changed
  10. page_header_update: description changed (-"QR display,")
  11. page_get: input schema changed
  12. page_create_from_brief: input schema changed
  13. page_create_from_brief: description changed (+"The main tool for creating a page. Call it directly when the request already has the business/page name and the main visitor action with its real destination (WhatsApp number with country code, booking/order link, phone, address or email); if the request is vague, ask at most one round of questions first (page_intake_start lists them). Creates" +"private" +"and returns previewUrl, pageId, editToken (anonymous pages), claimUrl")
  14. page_create: input schema changed
  15. page_create: description changed (+"Low-level/legacy: create" +"blank" +"scaffold")
  16. page_claim: input schema changed
  17. block_update: input schema changed
  18. block_reorder: input schema changed
  19. block_delete: input schema changed
  20. block_add: input schema changed
  21. block_add: description changed (+"14" +"reviews, save_contact)" -"13")
  22. account_pages_list: input schema changed
  23. account_pages_list: description changed (+"saved to" +"sign-in:" +"chat")
  24. account_page_manage: input schema changed
  25. server instructions changed (+"Create Web Page builds and hosts simple one-page websites (local business pages, link-in-bio, digital business cards). Flow: 1) No account is needed: call page_create_from_brief once you know the name and the main visitor action with its real destination (ask at most one round of questions; page_intake_start lists them). 2) Show the private preview link and stop. 3) Publish only when the user explicitly asks. 4) After publishing, share the live URL and, for pages made without an account, the private keep link (claimUrl) and its expiry: unclaimed pages are deleted after expiresAt. 5) Never unpublish unless the user asks. Reply in the user's language and write page copy in it. Use only facts the user or a public source provided: never invent prices, hours, reviews, services or contact details. Keep the pageId and editToken from results for later edits.")
  26. source_import: annotations changed
  27. presets_list: annotations changed
  28. page_unpublish: annotations changed
  29. page_theme_update: annotations changed
  30. page_publish: annotations changed
  31. page_preview: annotations changed
  32. page_onboarding_update: input schema changed
  33. page_onboarding_update: annotations changed
  34. page_onboarding_start: input schema changed
  35. page_onboarding_start: annotations changed
  36. page_meta_update: annotations changed
  37. page_intake_start: annotations changed
  38. page_header_update: annotations changed
  39. page_get: annotations changed
  40. page_create_from_brief: annotations changed
  41. page_create: annotations changed
  42. page_claim: annotations changed
  43. media_upload_link_create: annotations changed
  44. media_upload: annotations changed
  45. media_delete: annotations changed
  46. media_attach: annotations changed
  47. layouts_list: annotations changed
  48. block_update: annotations changed
  49. block_reorder: annotations changed
  50. block_delete: annotations changed
Source listings
SourceListingFirst seenLast seenVersions
Official MCP Registrycom.create-web-page/create-web-page2 Oct 20267 Oct 20261