Tools overview

Three interfaces, one engine — CLI, MCP, and builder UI.

Three interfaces write to one headless engine. All paths validate against siteShapes.ts and persist to Firebase RTDB.

Building sites in the UI? See Using nertia — customer guides for publish, export, domains, and billing.

Builder UI ──┐
ner CLI      ├──► applyCommands() ──► Firebase ──► hosted site
MCP          ──┘

Interface	Entry	Best for
Builder UI	`/dashboard/[slug]`	Visual editing, content, publish
ner CLI	`ner @site +hero`	Terminal batch edits, scripting
MCP	`POST /api/mcp`	AI tool integrations (Cursor, Claude, etc.)

Subpages

Install — curl \| bash bootstrap
ner shorthand — token grammar and aliases
nertia CLI — verbose SiteCommand syntax
MCP — JSON-RPC tools table
CLI roadmap — honest today → north star

Engine stack

argv / tool call
      │
      ▼
cliInterpreter.ts
      │
      ▼
commandRouter.ts (SiteCommand validation)
      │
      ▼
conversionLibrary.ts → applyCommands()
      │
      ▼
siteShapes.ts (Zod) → putSite() → RTDB

Zone contract: core-engine.

Quick reference

Local bootstrap: curl -fsSL https://ner.sh/install | bash
Shorthand:       ner @mysite +hero +footer
Verbose:         npx tsx src/bin/nertia.ts --slug mysite add-section marketing-hero
MCP endpoint:    POST https://ner.sh/api/mcp