Onboarding tools collect category, layout, palette, and action fields.
For AI power users and developers
The website builder for MCP-capable agents
Give your AI client a focused page-publishing tool surface: collect a brief, create a public single-page website, preview it, publish it, and claim it for ongoing management.
No account is needed to create a first demo page. Claim and management flows use OAuth when you want the page to persist.
Use Create Web Page to make a launch page for an open-source MCP utility. Keep it concise, add install instructions, GitHub and docs links, and a clear call to star the repo.
Draft created. Preview is ready. Publish only after the user confirms.
The website builder for MCP-capable agents
Give your AI client a focused page-publishing tool surface: collect a brief, create a public single-page website, preview it, publish it, and claim it for ongoing management.
See compatible clients
Portable MCP contract
Every tool result is designed to be useful in plain MCP clients, with ChatGPT Apps widgets treated as optional progressive enhancement rather than the only interface.
- Plain-text content plus structuredContent on every tool result.
- OAuth 2.1 with PKCE, dynamic client registration, and revocation already implemented.
- Authless demo flow keeps first-page friction low across clients.
MCP setup path
- Point a compatible AI client at https://create-web-page.com/mcp.
- Let the client call onboarding or intake tools before creation.
- Use edit tokens for anonymous demo mutations.
- Use OAuth only for claim and account-management flows.
Prompt example
Use Create Web Page to make a launch page for an open-source MCP utility. Keep it concise, add install instructions, GitHub and docs links, and a clear call to star the repo.
Tool surface, not template guessing
Creation and editing tools return plain-text content plus structured payloads.
Publishing tools keep draft/live state explicit so agents do not accidentally change public pages.
Where this fits
- Give an agent a safe public-page creation primitive.
- Publish one-page docs, demos, portfolios, and local-business pages.
- Keep natural-language understanding in the user's AI client while the app stays deterministic.
MCP clients that work with Create Web Page today
Public marketplace approvals from OpenAI and Anthropic are still pending. None of the clients below depend on those approvals; they consume the same remote MCP server directly.
Claude Code
Add the Create Web Page remote MCP endpoint with a single config entry. Claude Code uses your existing Anthropic subscription to call the tools.
Codex CLI
Register the Create Web Page MCP server in your Codex CLI config and the model picks up the tools on the next session.
Cursor
Cursor reads the same MCP server config and exposes the tools to the in-IDE assistant.
Cline
The Cline VS Code extension supports remote MCP servers and surfaces tool calls inside the editor.
Claude Desktop custom connectors
Add Create Web Page as a custom connector inside Claude.ai or Claude Desktop. No directory submission required for personal use.
Setup in one minute
- Copy the MCP endpoint
https://create-web-page.com/mcp serves the JSON-RPC tool surface and authless demo path.
- Add it to your client's MCP config
Each client has its own settings file or UI for remote MCP servers. The MCP docs page lists exact snippets.
- Test with account.whoami
First tool call confirms the connection. Then move on to onboarding or page.create_from_brief.
What the MCP layer owns
AI client
Understands the user, asks questions, normalizes intent, and chooses tool calls.
Create Web Page
Validates schemas, stores content, renders pages, imports explicit public sources, and returns clear missing-field guidance.
User
Approves publish, supplies protected-source details, and claims pages when they should persist.
Public-source boundary
Create Web Page can import normal public HTTP pages as explicit source material. It does not bypass protected platforms such as Instagram, TikTok, Facebook, or Google Maps. For those sources, use your AI client's browsing, official connectors, pasted text, or screenshots.
FAQ
Is the app provider-specific?
No. ChatGPT and Claude are distribution surfaces. The product contract is MCP-first and works with compatible clients.
Does the backend infer business categories with an LLM?
No. Semantic inference belongs to the user's AI client. The app validates explicit structured fields and returns deterministic results.
Are HTML widgets required?
No. Tool results include plain-text content and structuredContent. Widgets are optional for clients that support them.
Related paths
The website builder for MCP-capable agents
Give your AI client a focused page-publishing tool surface: collect a brief, create a public single-page website, preview it, publish it, and claim it for ongoing management.