From install to first certified asset

Quick start

Three commands stand between you and a connected editor.

1. Install the plugin. Grab the BlueprintForge plugin for your engine version and enable it in your project.
2. Run the bridge. The bridge connects the editor to your AI client and exposes 1,884 in-editor commands.
3. Health check. Confirm the editor is reachable and the command surface matches your engine version.

# 1 — install the plugin (UE 5.7 or 5.8)
bf install --engine 5.8

# 2 — start the bridge
bf bridge start

# 3 — health check
bf doctor
✓ editor connected · 1,884 commands · UE 5.8

Connect your AI client (MCP)

BlueprintForge is an MCP server. Any MCP-capable client can drive the editor — these are the three most common setups.

Claude Code

claude mcp add blueprintforge -- bf mcp serve

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "blueprintforge": {
      "command": "bf",
      "args": ["mcp", "serve"]
    }
  }
}

VS Code

Add to .vscode/mcp.json:

{
  "servers": {
    "blueprintforge": {
      "type": "stdio",
      "command": "bf",
      "args": ["mcp", "serve"]
    }
  }
}

Claude Desktop uses the same server via its MCP settings. Note: the MCP surface exposes a compact tool set that routes to all 1,884 in-editor commands — the tool count you see in your client is not the command count.

First generation

Ask in natural language, or hand the planner an explicit ops file. Either way, the result is verified and certified.

{
  "op":       "niagara.create_system",
  "name":     "NS_Storm_Embers",
  "template": "fountain",
  "params":   { "spawn_rate": 450, "color": "#ff6b35" },
  "verify":   true
}

✓ forged /Game/VFX/NS_Storm_Embers
✓ verified structural 100% · values 99.7%
✓ cert 8f3a21c — rollback available

The Trust Stack

Three artifacts are produced for every change:

1. Mutation Cert — what changed, what was verified, how to roll back.
2. Context Capsule — the exact editor state and inputs, for reproducibility.
3. Side-Effect Trace — everything touched beyond the target. Empty means empty.

Verification is an independent read-back from the engine — the checker never trusts the writer. That's how Niagara reaches 99.7% value fidelity (100% structural) across 87/87 systems.

Auto-fix layers (L1–L7)

Failures escalate through seven layers — normalization, schema validation, adaptive retry, alternative strategy, partial rollback, state reconciliation, and finally an honest failure report. 3,000+ fixes ship today. You'll mostly never notice: that's the point.

Full layer-by-layer breakdown on the Features page →

CLI reference

Troubleshooting