Agents & MCP

The connector

Sitelas is a remote MCP server, so an AI agent can build and run your sites in natural conversation. In Claude or ChatGPT it is one click; every other client takes a few lines of config:

1. Open Sitelas in Claude’s connector directory and choose Add — or open the Sitelas app in ChatGPT.
2. Sign in to Sitelas (Google) and approve. Claude and ChatGPT both register themselves automatically — there’s no client ID to enter.

Everything else reads a config file rather than a directory. Point it at https://sitelas.com/api/mcp and sign in the same way — the exact shape differs by client:

claude mcp add --transport http sitelas https://sitelas.com/api/mcp

{
  "mcpServers": {
    "sitelas": { "url": "https://sitelas.com/api/mcp" }
  }
}

{
  "servers": {
    "sitelas": { "type": "http", "url": "https://sitelas.com/api/mcp" }
  }
}

{
  "mcpServers": {
    "sitelas": { "serverUrl": "https://sitelas.com/api/mcp" }
  }
}

{
  "mcpServers": {
    "sitelas": { "httpUrl": "https://sitelas.com/api/mcp" }
  }
}

Two ways to authenticate, same account, same tools:

What your agent can do

The connector exposes tools across the full lifecycle: discover templates; create, edit, and publish sites (surgical patches, brand & palette changes, image search, URL cloning); manage content collections; read submissions, contacts, and analytics; schedule jobs; and configure custom domains. Destructive actions (like deleting a site) are annotated and require explicit confirmation.

Tool reference

The connector’s tools are the same in Claude, in ChatGPT and for an agent with an API key, and every earlier tool name keeps working everywhere. Here they are by category:

Destructive tools (like delete_site or delete_page) are annotated destructive and require an explicit confirmation before they run.

API keys (headless access)

The connect flow above uses interactive OAuth — a human signs in. For an agent, script, or automation that runs without a browser, create an API key in Dashboard → Account → API keys (shown once) and send it as a bearer header to /api/mcp. No OAuth round-trip.

Claude Code

claude mcp add --transport http sitelas https://sitelas.com/api/mcp \
  --header "Authorization: Bearer $SITELAS_API_KEY"

Anthropic API (build your own agent)

client.beta.messages.create(
    model="claude-opus-5",
    max_tokens=16000,
    betas=["mcp-client-2025-11-20"],
    mcp_servers=[{
        "type": "url",
        "url": "https://sitelas.com/api/mcp",
        "name": "sitelas",
        "authorization_token": os.environ["SITELAS_API_KEY"],
    }],
    tools=[{"type": "mcp_toolset", "mcp_server_name": "sitelas"}],
    messages=[{"role": "user",
               "content": "Build a portfolio site and publish it."}],
)

Any MCP client / raw HTTP

curl -X POST https://sitelas.com/api/mcp \
  -H "Authorization: Bearer stl_pat_…" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

The key acts on your account with the same ownership scoping as the connector — the same tool catalog, no human in the loop. Set an optional expiry, watch its last-used date, and revoke it any time from the same screen.