Build Bricks templates from code — beyond what the UI allows.

The Bricks UI can only take you so far when you want to build templates at speed or have an AI pair do it for you. The cc-bricks-helper closes that: admin REST endpoints (`cc-bricks/v1`) for every element type, so an AI or a script can build and edit Bricks templates programmatically, beyond what the visual builder allows. Merge-settings semantics mean an edit updates settings instead of replacing them, so changes never silently wipe what's already there.

What you get

• REST API for every element (`cc-bricks/v1`): drive Bricks from code.
• Merge-settings semantics: edits update, they don't wipe your config.
• Production-tested and supported: built on a live shop, maintained, not a DIY recipe.
• Desktop-first breakpoint pattern: sensible, predictable responsive behaviour.
• Safe for AI-pair workflows: the merge-safety is exactly what an AI pair needs to build fast without breaking things.

FAQ

What's the £9/mo for?
Optional ongoing updates as Bricks changes underneath. The £49 is the plugin; the monthly keeps it current.

Isn't there an open Bricks MCP / DIY REST route?
There are other ways to drive Bricks from code now. The difference here is merge-safety: edits update your config instead of wiping it, plus it's a supported, production-tested plugin rather than a raw script you maintain yourself.

Do I need an AI co-pilot to use it?
No. It's a REST API any developer can call. The merge-safety just happens to be exactly what an AI-pair workflow needs.

Will it overwrite my existing templates?
No. Merge semantics mean it updates settings rather than replacing them.