Bricks Builder MCP Server

A Model Context Protocol (MCP) server that provides AI assistants with full access to Bricks Builder page content, enabling programmatic page building, template management, and element manipulation through natural language.

Features

• 29 tools for full Bricks Builder management

• Read, write, search, and manipulate Bricks page elements

• Template management with type filtering (header, footer, section, content, popup)

• 14 section generators for common patterns (hero, features, pricing, FAQ, and more)

• Snapshot system for rollback before destructive changes

• Element tree view, bulk updates, move, and duplication

• Global classes and custom CSS management

• Multi-site support: manage multiple Bricks sites from one server instance

• CPT support: works with any custom post type, not just pages/posts

• Response trimming and pagination with totals

Related MCP server: Bricks MCP

Available Tools (29)

Element Manipulation (10 tools)

Snapshot / Rollback (4 tools)

Template Management (5 tools)

Page Management (3 tools)

CSS & Styling (3 tools)

Local Helpers (3 tools -- no API calls)

Site Settings (1 tool)

Section Generator Patterns (14)

The bricks_generate_section tool creates complete, ready-to-use Bricks element structures:

All patterns accept overrides to customize texts, colors, and structure.

Requirements

• Node.js 18+

• WordPress site with Bricks Builder theme installed and active

• WordPress Application Password

Quick Setup

1. Clone and build

git clone https://github.com/sabiertas/bricks-mcp-server.git
cd bricks-mcp-server
npm install
npm run build

2. Configure in Claude Code

Add to ~/.claude.json:

{
  "mcpServers": {
    "bricks": {
      "command": "node",
      "args": ["/path/to/bricks-mcp-server/dist/bricks-mcp-server.js"],
      "env": {
        "BRICKS_SITES": "main,staging",
        "BRICKS_MAIN_URL": "https://your-domain.com",
        "BRICKS_MAIN_USERNAME": "your-wp-username",
        "BRICKS_MAIN_PASSWORD": "your-application-password",
        "BRICKS_STAGING_URL": "https://staging.your-domain.com",
        "BRICKS_STAGING_USERNAME": "admin",
        "BRICKS_STAGING_PASSWORD": "your-application-password"
      }
    }
  }
}

3. Configure in Cursor / other MCP clients

Same config pattern -- see your client's MCP documentation.

Authentication

Uses WordPress Application Passwords (Basic Auth). Create one at: WordPress Admin > Users > Profile > Application Passwords

Multi-site Support

This server supports managing multiple Bricks Builder sites simultaneously:

1. BRICKS_SITES: Comma-separated list of site identifiers (e.g., main,staging,client)

2. Per-site variables: For each site ID, set BRICKS_{ID}_URL, BRICKS_{ID}_USERNAME, and BRICKS_{ID}_PASSWORD

3. Tool usage: Every tool accepts a site parameter. If omitted, the first configured site is used as default.

CPT Support

All element and CSS tools accept a post_type parameter that defaults to pages but works with any registered custom post type (e.g., posts, product, portfolio).

Response Format

List endpoints return paginated responses:

{
  "data": [...],
  "total": 25,
  "total_pages": 1
}

Changelog

v2.0.0

• 29 tools (was 20): element search, snapshots, bulk update, move, duplicate, tree view, delete snapshot

• 14 section generators (was 6): contact, stats, team, logos, newsletter, comparison, steps, footer

• Enhanced list_pages (include_all, search) and list_templates (template_type filter, popup)

• Snapshot rollback system (save, restore, list, delete)

• Element validation with warnings

• Response trimming and pagination with totals

• CPT support for all element/CSS tools

• clonePage respects source post type

• createTemplate writes template_type to meta

v1.0.0

• Initial release: 20 tools, multi-site support, 6 section generators

Contributing

PRs welcome. Please open an issue first to discuss changes.

License

MIT