A Next.js tool that creates editable Bricks Builder JSON templates. Use built-in sections, an AI provider, local ChatGPT sign-in through Codex, or a ChatGPT MCP connection. Review exports in Bricks before publishing.
Start here: setup, both AI connections and import guide.
- Pre-built template library (Hero, Navbar, Features, Pricing, Testimonials, Footer and more)
- Full page presets
- Design tokens (colors, border-radius, shadows, spacing, typography, dark mode)
- API route for AI-powered generation (
/api/generate) - Export as Bricks Import JSON + copy-to-clipboard
- Local Sign in with ChatGPT, optional MCP tools and JSON paste/file import
- Bricks 2.4.1 native element/control registry, reference repair and responsive defaults
- Export types and preservation of global classes/component metadata
- Node.js 22.12+
- npm 10+
npm ci
npm run devThen open in your browser:
http://localhost:3000
npm run lint
npm test
npm run build
npm run typecheck
npm run startThe API supports OpenAI Responses, Anthropic, Azure OpenAI and OpenRouter. Use Settings to choose a provider/model and test the connection. API usage is billed by your provider; a ChatGPT subscription does not include API credit.
For Sign in with ChatGPT, install the official Codex CLI and use npm run dev:local. In Settings, sign in, check the connection and enable the ChatGPT account option. This loopback-only mode uses your Codex account limits and supports text prompts. It is unavailable on the public Vercel deployment. See setup for the separate MCP option.
Request fields:
prompt(string)apiKey(string)useAI(boolean, defaults to false)provider("openai" | "anthropic" | "azure" | "openrouter")model(optional string); Azure requires endpoint/deployment
src/app/page.tsx– Main UIsrc/app/api/generate/route.ts– Generation APIsrc/lib/bricks-engine.ts– Bricks JSON engine + section generatorssrc/lib/templates.ts– Template catalogsrc/components/*– UI components (form, preview, cards)
- Built with the Next.js App Router.
- Apply deployment rate limits. Keep server-funded keys disabled on public deployments without authentication.
- Validation covers structure/control names, not all nested values or WordPress runtime behavior. See the audit for outstanding integration checks.