Bricks · MCP

Bricks + MCP: Build Native Templates With AI

Connect Bricks to Claude, Cursor or ChatGPT through NibWP. Turn a design, URL or screenshot into a native Bricks element tree — clean structure, your classes, on a plan you approve.

Get started →How it works
Bricks and MCP — let AI work through real abilities

Bricks people care about clean structure — that's exactly what a generic AI can't give you. Drop an exported layout into a code element and it renders, but it isn't Bricks: you can't nest it, theme it, or wire a query loop to it.

NibWP exposes Bricks as MCP tools. Hand it a design, a URL or a screenshot and it builds a native Bricks element tree — sections, containers and real elements on your global classes, ready to keep building.

What you can do over MCP

Native Bricks element tree

A design becomes sections, containers and real content elements — nested the way you would build them.

Global classes

Elements are wired to your Bricks global classes, not one-off inline styles you can't reuse.

Query loops & dynamic data

Structure that's ready for Bricks query loops and dynamic data — not a static, flattened blob.

From HTML, URL or image

Feed it pasted HTML, a live URL, a screenshot or a Figma frame — it maps each to real Bricks elements.

Clean, portable markup

Semantic, standards-based output with unique IDs — the reason you chose Bricks in the first place.

Approve before write

Every build lands as a draft you review. Nothing is saved until you say yes.

How it works

  1. Install NibWP and connect your AI client over MCP — Bricks shows up as tools.
  2. Point it at a source: HTML, a live URL, a screenshot, or a Figma frame.
  3. NibWP builds a native Bricks element tree on your global classes, and shows you the plan.
  4. Approve, and it saves a real Bricks template you can keep editing on the canvas.

Why typed tools beat a generic AI

A generic assistant

  • Drops a code element full of inline styles
  • Can't nest, theme or query the result
  • Breaks the clean structure you chose Bricks for

Bricks + NibWP

  • A real, nestable Bricks element tree
  • Wired to your global classes
  • Ready for query loops and dynamic data

Safe by default

Built for client sites, so control and traceability come first:

  • Nothing is written without your approval — you see the plan first.
  • Every action is recorded in a full audit trail.
  • It runs on WordPress core and your plugins’ own APIs — your content and site data stay on your server.
  • Reads are read-only; writes are gated.
FAQ

Questions, answered

Common questions about Bricks over MCP.

Is the output real Bricks or a code element?
Real Bricks elements you can select and edit on the canvas — not a single code element with pasted markup.
Can I still use global classes and dynamic data?
Yes — the output is native Bricks, so everything Bricks offers works on top of it.
Will it overwrite my templates?
No. Every build lands as a draft for you to review; nothing is replaced without you.
Which AI clients work?
Claude Code, Claude Desktop, Cursor, Windsurf and ChatGPT — anything that speaks MCP.

Put AI to work in Bricks.

Install NibWP, connect your AI client, and work through real Bricks abilities — safely, on your own site.

Get started →How it works