Grok Build
Image CDN for Grok Build
Grok Build takes TOML like Codex, but scoped to the project — and it expands ${AURA_SECRET_KEY} for you.
$0 forever 20 GB bandwidth 3 GB storage hard stop at quota — never a surprise bill. Compare plans
Add AuraImage to Grok Build
Like Codex this file is TOML, but the env vars get their own [mcp_servers.auraimage.env] table and Grok expands ${VAR} (and ${VAR:-default}) in url, command, args, env, and headers. grok mcp add --scope project writes this file in the current directory; when Grok loads, a project server replaces a user-level one of the same name entirely.
[mcp_servers.auraimage]
command = "npx"
args = ["-y", "@auraimage/mcp-server@latest"]
enabled = true
startup_timeout_sec = 30
[mcp_servers.auraimage.env]
AURA_SECRET_KEY = "${AURA_SECRET_KEY}"Or from the terminal
grok mcp add --scope project auraimage -- npx -y @auraimage/mcp-server@latestVerified against the vendor docs on 2026-08-09.
Optimize images with Grok Build
Each prompt is paired with the MCP tool it fires.
- Audit the images in this repo only — I keep the server scoped to this project.
audit_lcp - Move every image in src/assets to AuraImage and keep the original filenames. If it stalls halfway, stop and I will run grok mcp doctor.
migrate_assets - Write alt text for the pricing and checkout pages, and flag any I should redo by hand.
generate_alt - Build the hero a responsive <picture> at 480, 960, and 1920 — if the server is still cold, raise startup_timeout_sec rather than dropping a size.
generate_responsive_tag - Preview logo-wide.png as a square avatar and as a wide OG card, using the server from this checkout rather than the user-level one it replaced.
smart_crop_preview
Discovery — acme-storefront Framework Next.js 15 (App Router, TypeScript, pnpm) Images 14 <img> tags · 23 files in /public · 6 Cloudinary URLs Secrets no AURA_* keys · .env.local gitignored Backend route handlers — can sign upload tokens Hosting Vercel Plan 1. Credentials & env → auraimage-api-key 2. Register MCP server → .mcp.json 3. Install SDK → pnpm add @auraimage/sdk 4. Components → <AuraImage /> + <AuraUploader /> 5. Token route → app/api/aura/sign/route.ts4:39 PM
AuraImage installed — 6 writes, 0 failures Wrote .env.local +2 keys (masked) .mcp.json auraimage MCP server package.json @auraimage/sdk 1.4.2 components/aura/ image.tsx · uploader.tsx app/api/aura/sign/ route.ts (+11 lines) Next 1. Restart your agent to load the MCP server 2. audit_lcp — scan for unoptimized images 3. migrate_assets — 23 local + 6 Cloudinary images detected 4. auraimage-react — <AuraImage /> patterns Docs: https://auraimage.ai/docs4:41 PM
Turn completed in 142.7s.
A Cloudinary alternative your agent can wire up itself
| Capability | Cloudinary / Imgix | AuraImage with Grok Build |
|---|---|---|
| Pricing model | Metered per GB and per transform | Flat monthly price |
| Egress | Billed | $0 |
| AVIF | Opt-in configuration | Served by default |
| BlurHash placeholders | Build it yourself | Bundled |
| Component | SDK import | Lands in your repo, yours to edit |
| Install | Manual wiring | One MCP config, then a prompt |
Teach Grok Build your image conventions
AGENTS.md at the repo root is the primary convention and Grok Build reads it, alongside every *.md in a .grok/rules/ directory. Use .grok/rules/ when you want Grok-specific guidance that other agents will not pick up. Rules load from the root down to the working directory, with deeper files winning on conflicts.
.grok/rules/Verified against the vendor docs on 2026-08-09.
Questions, answered
The things developers ask before they ship. If something is missing, just email us.
Install it in your side project. Pay when you ship.
$0 forever 20 GB bandwidth 3 GB storage hard stop at quota — never a surprise bill. Compare plans