The SiteSorted 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 SiteSorted account.
Install the SiteSorted MCP/mcp ->Agent prompt
sitesorted_create_site01Create, clone, or upgrade a site through the SiteSorted builder API.
sitesorted_edit_site02Apply bounded edits to generated HTML without asking the agent to redesign the whole page.
MCP invocation
streaming{
"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
~/.codex/runs/perfectclone/sitesorted-mcp. Credits charged to the owning SiteSorted 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.
Mac / Linux
curl -fsSL https://sitesorted.co.nz/api/mcp/install | shWindows PowerShell
irm https://sitesorted.co.nz/api/mcp/install/windows | iexThe installer saves the server locally, then prints the MCP client config. Create a SiteSorted token, paste it in as SITESORTED_API_TOKEN, and your agent can call the builder.
Account-owned keys
No browser cookies, no free bypass. Agent calls authenticate through scoped SiteSorted API keys.
Production API boundary
The MCP calls /api/v1/sites and /api/v1/sites/edit through your SiteSorted 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 SiteSorted system, two entry points: a visual builder for humans and a callable tool surface for agents.
