# Create Web Page Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Create Web Page

Build and publish link-in-bio landing pages for your business or project.

- Record: https://musedirectory.ai/connector/create-web-page
- Category: Shopping & Commerce
- Developer: daniel-lopez-puig (https://create-web-page.com/docs/mcp)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 555ms, checked 2026-09-28T10:01:28Z
- Endpoint: https://create-web-page.com/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T12:26:16Z)
- Source: Found in the official MCP Registry (com.create-web-page/create-web-page) https://registry.modelcontextprotocol.io/v0/servers?search=com.create-web-page%2Fcreate-web-page

Create hosted landing pages and link-in-bio sites with customizable layouts, themes, and content blocks. Import from existing websites, add images and contact forms, and publish to a public URL. No coding required.

Example request: "Create a landing page for my restaurant with a menu, hours, and a button to book a table."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Create Web Page to help me. It is a free service with an MCP server at https://create-web-page.com/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- account_whoami: Return the current Create Web Page account context. Use this to check whether the user is authenticated or using an anonymous expiring demo.
- page_intake_start: RECOMMENDED 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_* offe
- page_onboarding_start: Optional 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 STATE
- page_onboarding_update: Validate 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
- source_import: Fetch 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 pag
- page_create: Create 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 cr
- page_create_from_brief: Create 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 
- block_add: Append 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 gen
- layouts_list: List supported page layouts. Currently ships link_in_bio only.
- presets_list: List 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_get: Read a landing page draft, including its latest content JSON. For anonymous demo pages, include the editToken.
- media_upload: Add 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
- media_upload_link_create: Get 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 click
- media_attach: Attach 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 (th
- media_delete: Soft-delete a media asset and remove all references to it from the page content.
- page_claim: Claim 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
- account_pages_list: List landing pages claimed by the signed-in account. Safe to call without auth: an anonymous demo session gets ok=true with an empty list and authRequired=true (not an error) because it has no saved pages, so go straight to page_intake_start or page_create_from_brief. Sign-in is 
- account_page_manage: Read a claimed account page without requiring an editToken. Use after OAuth when the user wants to manage a durable website.
- page_header_update: Update the link-in-bio page header: displayName, bio, verified checkmark, QR display, 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
- page_theme_update: Apply 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 
- page_meta_update: Update 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
- page_preview: Return 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.
- page_publish: Publish 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 anonym
- page_unpublish: Remove a published landing page from public availability while keeping its draft and revision history.
- block_update: Patch 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_p
- block_delete: Delete 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 upda
- block_reorder: Move 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 se

Screening checks:
- MCP handshake: pass (Answered in 270ms)
- Domain against threat feeds (Cloudflare security DNS): pass (create-web-page.com not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (27 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)