Developers and MCP

Site production should work from the product and the API.

The MCP and API surface exists; the launch site needs to show it clearly without forcing founders into developer docs.

API keys.

Signed-in users should be able to create scoped keys for SiteSorted production workflows.

Use account API keys for programmatic site creation and bounded edit runs. Keys are visible once, revocable, and tied to account credit boundaries.

Create MCP token

Core endpoints.

The public developer page should mirror the real API shape.

POST/api/v1/sites

Create a site production run.

POST/api/v1/sites/edit

Apply a bounded edit to an existing site.

MCP install.

The MCP is the bridge for agent-led site production.

Any terminal with Node

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

Mac / Linux shell

curl -fsSL https://sitesorted.co.nz/api/mcp/install | sh

Windows PowerShell

irm https://sitesorted.co.nz/api/mcp/install/windows | iex

Install, token, config

The Node command works in PowerShell, cmd, bash, and zsh. The installer places the MCP server locally and prints the config for Claude, Cursor, Codex, or any MCP client. Create a token, paste it into that config, and generated sites will expose artifact paths for verification.

Direct download

Founders use the product. Agents use the API.

Create token