Create Web Page
com.create-web-page/create-web-pageVersion 0.1.0Create, edit, preview, publish, and manage web pages from MCP-capable AI clients.
Status
Responds204 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:52 UTC
- Latency
- 204 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://create-web-page.com/mcpResponds204 msNo sign-in
Claude Code
claude mcp add --transport http create-web-page https://create-web-page.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: create-web-page
Remote MCP server URL: https://create-web-page.com/mcpCursor
{
"mcpServers": {
"create-web-page": {
"url": "https://create-web-page.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"create-web-page","type":"http","url":"https://create-web-page.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
24 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
account_whoamiReturn the current Create Web Page account context. Use this to check whether the user is authenticated or using an anonymous expiring demo. | No | Yes | Yes | No |
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. On an already-published page this saves a new draft revision only: the live page does not change until page_publish runs, which should happen only when the user explicitly asks to update the live page. The edit never takes the live page down. The response includes nextSteps: optional hints about what else would make the page more complete. | No | No | No | Yes |
block_deleteDelete one block by stable blockId. Use page_get first if unsure which id to remove. On an already-published page this saves a new draft revision only: the live page does not change until page_publish runs, which should happen only when the user explicitly asks to update the live page. The edit never takes the live page down. | Yes | No | Yes | No |
block_reorderMove a block to a new zero-based index in the page main slot. On an already-published page this saves a new draft revision only: the live page does not change until page_publish runs, which should happen only when the user explicitly asks to update the live page. The edit never takes the live page down. | No | No | Yes | No |
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. On an already-published page this saves a new draft revision only: the live page does not change until page_publish runs, which should happen only when the user explicitly asks to update the live page. The edit never takes the live page down. | No | No | Yes | Yes |
layouts_listList supported page layouts. Currently ships link_in_bio only. | No | Yes | Yes | No |
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). | No | No | No | No |
media_deleteSoft-delete a media asset and remove all references to it from the page content. | Yes | No | Yes | No |
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). | No | No | No | Yes |
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). Returns uploadPageUrl, a page the user opens to pick their photo; it resizes the image for the web and attaches it to the page itself, so no media_attach call is needed. The link expires (see expiresAt). page_get shows the photo once it has been uploaded. | No | No | No | No |
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. | No | No | No | No |
page_create_from_briefCreates a real website hosted on its own public link (create-web-page.com/sites/<name>) that customers or friends can open on any phone: a small-business page with WhatsApp, call, map or booking buttons, an Instagram link-in-bio, a digital business card, or a personal page such as a birthday, invitation or tribute. It returns a private preview first; page_publish makes it public. 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, ma | No | No | No | Yes |
page_getRead a page's latest draft: content with block ids, pageId, editToken, preview and public URLs. Pass pageId (+ editToken for anonymous pages), or only editToken — which may be the whole private keep link the user saved (https://create-web-page.com/claim/<token>) — to reopen a page from an earlier conversation. | No | Yes | Yes | No |
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. On an already-published page this saves a new draft revision only: the live page does not change until page_publish runs, which should happen only when the user explicitly asks to update the live page. The edit never takes the live page down. | No | No | Yes | Yes |
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. | No | Yes | Yes | No |
page_meta_updateUpdate internal page title, URL slug, and SEO title/description. On an already-published page this saves a new draft revision only: the live page does not change until page_publish runs, which should happen only when the user explicitly asks to update the live page. The edit never takes the live page down. | No | No | Yes | No |
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). | No | Yes | Yes | No |
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. | No | Yes | Yes | No |
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. | No | Yes | Yes | No |
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 the public URL and nextSteps (the claim reminder for demo pages and any remaining optional improvements). | Yes | No | Yes | No |
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. On an already-published page this saves a new draft revision only: the live page does not change until page_publish runs, which should happen only when the user explicitly asks to update the live page. The edit never takes the live page down. | No | No | Yes | Yes |
page_unpublishRemove a published landing page from public availability while keeping its draft and revision history. | Yes | No | Yes | No |
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. | No | Yes | Yes | No |
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. | No | Yes | Yes | Yes |
Details
- Registry status
- Active
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Categories (suggested)
- Files and storageSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared