The nerd door 🔧

The CLI

npx drivethrough (alias dt). Log in once with a GitHub-style device flow, then deploy any static folder:

npx drivethrough login
npx drivethrough deploy ./my-site      # private by default
npx drivethrough share my-site         # Google-Docs-style share link
npx drivethrough privacy set my-site public

Every command supports --json and non-interactive mode, and error messages are written for agent self-correction — plan-limit errors include the upgrade URL, so your agent can relay it instead of guessing.

MCP, both transports

One tool layer — deploy_site, edit_site, get_site, query_db, set_privacy, share_site, and friends — exposed two ways:

• stdio: npx -y drivethrough mcp for Claude Code and local agents. drivethrough agent-setup writes SKILL.md / AGENTS.md and prints both configs.
• Hosted remote: Streamable HTTP + OAuth at https://mcp.drivethrough.dev/mcp — how claude.ai chat and the mobile apps reach the platform. No terminal required.

Chat-born sites round-trip without a filesystem: agents read a deployed bundle back (get_site), edit in place (edit_site), and patch-deploy — the platform assembles versioned bundles server-side.

Data without migrations

Each site gets its own database with one universal document schema. Declare types in drivethrough.json — fields, permissions, rate limits, notify: "owner-email" — and the platform serves a validated Data API for RSVPs, comments, and contact forms. Public writes are Turnstile-protected.