Quickstart

From zero to a served site

You need Docker (for Postgres and Redis), Python 3.15 and uv. Nothing else — no Node, no bundler, no template directory.

1 · Raise the city

On first start, migrations run for the public schema and every tenant schema; the default tenant is created, seeded with this site, and published. The website answers on port 8000, the remote MCP endpoint on 8001.

sh
$ git clone https://github.com/Galaktis/uruk && cd uruk
$ docker compose up -d
# http://localhost:8000 — any hostname serves the default tenant
# http://localhost:8001/mcp — the remote MCP endpoint

2 · Claim the throne

No credentials live in the startup path. The tenant's first superuser is claimed over the API with a claim code that only the server's operator can read (it is printed in the app's logs while the tenant is unclaimed). URUK_ADMIN_EMAIL restricts the claim to one address; once claimed, the endpoint refuses forever. Then sign in at /uruk/. Details on the configuration page.

sh
$ docker compose exec app uv run python manage.py claim_code
3f9c…  # the default tenant's claim code
$ curl -X POST http://localhost:8000/api/bootstrap -H "Content-Type: application/json" -d "{\"email\": \"[email protected]\", \"code\": \"<claim code>\"}"
{"set_password_url": "/api/set-password?uid=…&token=…"}  # one-shot; a second claim is refused

3 · Hand a scribe the stylus

Issue an API token for a tenant user (the claimed superuser's username is its email), then point an MCP client at the remote endpoint. The agent can do exactly what that user's permissions allow — create pages, move elements, upload assets, publish.

sh
$ docker compose exec app uv run python manage.py create_api_token default [email protected]
uruk_…  # shown once — store it
// in an MCP client config (Claude Code, etc.)
{
  "mcpServers": {
    "uruk": {
      "type": "http",
      "url": "http://localhost:8001/mcp",
      "headers": { "Authorization": "Bearer uruk_…" }
    }
  }
}

4 · Review, then publish

Every edit is an ordinary write to the site's draft. Visitors keep the published revision while editors watch the draft at /_preview/ — or sign in at /admin/ and open the Studio to review the agent's work, fix it, and publish. Every publish is kept: roll back to any revision, or discard the draft.

This page — the one explaining the system — is itself rows in the default tenant. Ask your agent to reword this paragraph and publish, refresh, and it's done. No commit, no build, no deploy.