Iter0

The Iter0 builder, callable by your agent.

Connect Claude, Cursor, Codex, or any MCP client to create launch-ready sites, edit generated pages, and save artifacts through your own Iter0 account.

Install the Iter0 MCP/mcp ->
Agent workspace

Agent prompt

Create a launch page for a compliance automation startup. Use our existing site for language, upgrade the design, and save the final HTML locally.
sitesorted_create_site01

Create, clone, or upgrade a site through the Iter0 builder API.

sitesorted_edit_site02

Apply bounded edits to generated HTML without asking the agent to redesign the whole page.

MCP invocation

streaming
sitesorted_create_site
{
  "mode": "upgrade",
  "referenceUrl": "https://customer-site.example",
  "prompt": "Use their content. Improve the structure.",
  "saveArtifacts": true
}

research

Industry context and reference fit

build

Generated HTML and preview artifact

proof

Saved output path for agent review

Site saved to ~/.codex/runs/perfectclone/iter0-mcp. Credits charged to the owning Iter0 account.

Install once. Let the agent call the builder.

The MCP is a client of the production API. It uses account-owned API keys, spends existing credits, and writes generated HTML artifacts locally for verification.

Terminal install

Any terminal with Node

node -e "fetch('https://iter0.com/api/mcp/install/node').then(r=>r.text()).then(eval)"

Mac / Linux shell

curl -fsSL https://iter0.com/api/mcp/install | sh

Windows PowerShell

irm https://iter0.com/api/mcp/install/windows | iex

Use the Node command in PowerShell, cmd, bash, or zsh. The shell and PowerShell commands are direct alternatives. The installer saves the server locally, then prints the MCP client config. Create a Iter0 token, paste it in as SITESORTED_API_TOKEN, and your agent can call the builder. The legacy token name remains for compatibility.

Account-owned keys

No browser cookies, no free bypass. Agent calls authenticate through scoped Iter0 API keys.

Production API boundary

The MCP calls /api/v1/sites and /api/v1/sites/edit through your Iter0 account.

Local proof artifacts

Generated HTML and local output paths are written where agents can inspect them.

Founders launch in the builder. Agents launch through MCP.

Same Iter0 system, two entry points: a visual builder for humans and a callable tool surface for agents.

Open builder