For developers and AI power users

MCP clients that work with Create Web Page today

Any MCP-capable client can consume the Create Web Page remote MCP server with a short config, then create digital cards, contact pages, link-in-bio pages, and mini websites from prompts.

No account is needed to create a first demo page. Claim and management flows use OAuth when you want the page to persist.

One MCP endpoint, many clients

Create Web Page implements the standard remote MCP transport. Any client that supports remote MCP servers can call the same tools. We test against Claude Code, Codex CLI, Cursor, Cline, and Claude Desktop custom connectors.

Choose your client and connect

  1. Pick a client from the list below.
  2. Add https://create-web-page.com/mcp as a remote MCP server in that client's config.
  3. Call account.whoami to confirm the connection.
  4. Call page.create_from_brief or the onboarding tool to make your first page.
Prompt example

From Codex CLI: create a digital card and mini website for a side project, return the preview link, and publish only if I confirm.

What the same tool surface looks like

The same MCP server URL works across CLIs, IDEs, and chat surfaces.

Tool calls return plain-text content plus structured payloads.

No client-specific code paths in the backend.

Where this fits

Compatible MCP clients

All clients below talk to the same remote MCP server. The links below point to each client's MCP documentation.

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 when remote connectors are available in your workspace.

Pick one and connect

  1. Open the client's MCP config

    CLIs use a config file. IDEs and desktop clients use a settings UI. Either way, you add one remote MCP server entry.

  2. Use the Create Web Page MCP URL

    https://create-web-page.com/mcp. No bearer token or API key required for the first demo page.

  3. Run your first tool call

    Ask your client to call account.whoami, then move on to page.create_from_brief or page.onboarding.start.

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

Do I need a Create Web Page account to try it?

No. The first demo page is created in an anonymous flow. OAuth is only required when you want to claim and manage pages permanently.

Are public app-store listings required?

No. Public directories can help discovery, but the remote MCP endpoint works directly from compatible clients.

Does my client need internet access?

Yes. The MCP server is remote. Local-only MCP clients without outbound network access cannot reach it.

MCP clients that work with Create Web Page today

Any MCP-capable client can consume the Create Web Page remote MCP server with a short config, then create digital cards, contact pages, link-in-bio pages, and mini websites from prompts.