sitebox

Self-hosted static site host — upload pages via REST API or MCP, serve them immediately.

• Upload files or ZIP archives to named destinations

• Serve from /dest/path instantly

• Auth — shared API key for uploads, optional password-protected pages

• TTL — auto-expire pages after a set time

• MCP — AI agents can manage pages via the built-in Model Context Protocol server

Quick start

docker run -e API_KEY=my-secret-key -v /path/to/pages:/app/data -p 8000:8000 ghcr.io/zarguell/sitebox

Upload a page:

curl -X POST http://localhost:8000/api/upload \
  -H "X-API-Key: my-secret-key" \
  -F "file=@index.html" \
  -F "dest=myapp"

Open http://localhost:8000/myapp/index.html in your browser.

Related MCP server: webserver-mcp

Features

REST API

All require X-API-Key header matching the API_KEY environment variable.

Upload parameters (multipart form):

MCP Server

Connect an MCP-compatible AI agent (Cursor, Claude Desktop) to http://host:8000/mcp with header X-API-Key.

Available tools:

• upload_page — upload base64 content or ZIP

• list_pages — browse page tree

• read_file — read file content

• delete_page — remove a page

Browser Auth

When auth_required=true on upload, visitors are redirected to a login form. The password is the shared API_KEY. Sessions last 24 hours (in-memory).

Configuration

Development

git clone https://github.com/zarguell/sitebox
cd sitebox
uv sync
API_KEY=dev-key uv run uvicorn sitebox.app:app --reload

Design

• config.py — shared env vars and in-memory state (AUTH_PREFIXES, DATA_DIR)

• storage.py — file operations (stdlib only)

• auth.py — login form, session tokens, browser auth helper

• rest_api.py — REST endpoints with API key check

• mcp_api.py — MCP server with Streamable HTTP transport

• app.py — FastAPI wiring, middleware, mounts

ponytail: session tokens and auth prefixes are in-memory (lost on restart). Add Redis or SQLite when multi-process persistence is needed.