How to Connect Claude to Bricks Builder (Two Ways, Step by Step)

"Connecting Claude to Bricks" means giving Claude, the AI assistant made by Anthropic, a direct line into your site, so it can read pages and build sections instead of just describing how you would. The technology behind both methods is MCP, an open standard that lets AI apps operate other software. If that concept is new to you, our plain-English MCP guide is the five-minute backgrounder; this article is the hands-on part.

Fair warning about bias: way 2 is our own product. We will describe way 1 as concretely and fairly as we can (we set it up ourselves and documented every stumble) so you can judge both with open eyes.

What do you need before you start?

• A Bricks Builder site. Way 1 requires Bricks 2.4, which is in beta as of July 2026. Way 2 requires an active Bricksfusion Pro Lifetime plan.
• The Claude Desktop app, signed in to your Claude account. Free download at claude.com/download. Other MCP clients like Claude Code and Cursor work too; we use Claude Desktop below because it is the friendliest.
• A staging site, strongly recommended. This is a private copy of your site used for testing. Any AI with write access deserves a sandbox, and way 1 is beta software on top.

Way 1: the native Bricks 2.4 MCP (free, beta)

The native route turns your own WordPress site into an MCP server using the WordPress MCP Adapter, the component that translates Bricks' AI "abilities" into a language AI clients understand. It costs nothing beyond your Bricks license; the price you actually pay is the setup. The exact screens are still evolving between beta releases, so treat these steps as the map rather than turn-by-turn navigation:

1. Check that application passwords work on your site. An application password is a WordPress feature that issues a separate, revocable password so an app can act on your site without your main login. It normally lives on your WordPress user profile screen. See the warning below: this is where our own setup stalled.
2. Generate the credential. Create an application password for the WordPress user the AI should act as. The AI inherits exactly that user's permissions, so a dedicated user with only the permissions it needs is smarter than your admin account. WordPress shows the password only once, so copy it somewhere safe.
3. Set up the MCP Adapter and enable abilities. Bricks 2.4 includes an admin screen where you enable AI abilities individually and set up AI clients. (Abilities are the roughly 145 individual actions the AI may perform, explained in our Bricks 2.4 AI overview.)
4. Edit Claude Desktop's config file by hand. Claude Desktop reads this kind of connection from a text file named claude_desktop_config.json. You add a small block telling Claude where your site lives and which credential to use. The adapter's own instructions provide the exact text. If you have never edited a raw config file: go slowly, one misplaced comma breaks it.
5. Restart Claude Desktop. Fully quit and reopen it, and the Bricks tools appear in Claude. Depending on your client and setup you may also need Node.js, a free program that runs JavaScript outside the browser, which some MCP connections run through.

Honest verdict: none of this is difficult for a developer, and nearly all of it is unfamiliar territory for everyone else. Budget a quiet evening for the first attempt and expect at least one snag. What comes out the other end is a real, working connection. We tested it and published exactly what it built, the good and the bad.

Way 2: the Bricksfusion MCP (Pro Lifetime plan)

This is our product, included in the Pro Lifetime plan. The connection is a URL rather than software you install and configure, which is why the setup is short:

1. Log in to your Bricksfusion dashboard and open the MCP section.
2. Copy the URL shown for Claude Desktop.
3. In Claude Desktop, go to Settings → Connectors and paste the URL.

That is the whole setup. There are no API keys to create for the connection and no config files to hand-edit; it runs on the Claude subscription you already have. If you use Claude Desktop or Claude Code, you don't need Node.js at all; Cursor, VS Code, and Windsurf may need it depending on the client version.

Once connected, Claude gets a toolbox built specifically for design work in Bricks:

• Generate complete Bricks sections from a plain-English description.
• Search a library of 390+ wireframes (pre-built section layouts) so it starts from proven structure instead of a blank page.
• Validate the generated JSON with quality checks before it touches your page, including WCAG contrast. (WCAG is the web accessibility standard; the check confirms text is actually readable against its background.)
• Read your site's structure: post types, taxonomies, and custom fields from ACF, Meta Box, JetEngine, or Pods, so sections can be built around your real content.
• List your pages, read a page's content, and add, replace, or remove sections on it.

The full official setup guide covers every supported client, including the Node.js route for Cursor.

Which way should you pick?

Pick the native MCP if the setup doesn't scare you, you want zero extra cost, and you want the widest raw control over Bricks: it reaches templates, theme styles, forms, and more. Pick the Bricksfusion MCP if you want the short setup and care most about what actually gets generated: sections that pass quality checks and respect your content structure. The two are not mutually exclusive. Claude Desktop can hold several connections at once, and they specialize in different jobs. Our side-by-side comparison goes deeper, including the places where the native option wins.

Whichever route you choose: run your first sessions on staging, review everything the AI builds, and keep the credential private. The connection is the easy part to undo. The habits are what keep you safe.