Bricks Builder MCP Server
Provides programmatic access to Bricks Builder page content, including element manipulation, template management, snapshot/rollback, and 14 section generators for common patterns.
Connects to WordPress sites via Application Passwords, enabling management of pages, custom post types, and templates with Bricks Builder content.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Bricks Builder MCP Server list all header templates"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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)
Tool | Description |
| Get the Bricks elements array for a page/post by ID |
| Set/replace the entire Bricks elements array |
| Add a single element with automatic parent-child linking and validation |
| Update a specific element's settings (shallow merge) |
| Remove an element and all its descendants |
| Search elements by type, text content, or CSS class |
| Update multiple elements at once with validation |
| Move element to a different parent or position |
| Deep-clone element and descendants with new IDs |
| Get hierarchical nested tree view of page structure |
Snapshot / Rollback (4 tools)
Tool | Description |
| Save page state before making changes |
| Restore page elements from a saved snapshot |
| List available snapshots for a page |
| Delete a specific snapshot |
Template Management (5 tools)
Tool | Description |
| List templates with type filter (header/footer/section/content/popup) and search |
| Get template details including elements array |
| Create a new template with type and elements |
| Update template elements, title, or status |
| Delete a template permanently |
Page Management (3 tools)
Tool | Description |
| List pages with Bricks content (or all pages with |
| Create a new page with Bricks content |
| Clone a page's Bricks content with regenerated IDs (respects source CPT) |
CSS & Styling (3 tools)
Tool | Description |
| Get Bricks global CSS classes |
| Get custom CSS for a page |
| Set custom CSS for a page |
Local Helpers (3 tools -- no API calls)
Tool | Description |
| List 24 available element types with defaults and examples |
| Generate a complete section from 14 predefined patterns |
| Generate a single Bricks element JSON |
Site Settings (1 tool)
Tool | Description |
| Get Bricks global settings |
Section Generator Patterns (14)
The bricks_generate_section tool creates complete, ready-to-use Bricks element structures:
Type | What it generates |
| Heading + subtext + CTA button, centered layout |
| Section heading + grid of feature cards (configurable columns) |
| Pricing table with highlighted plan, features list, CTA buttons |
| Dark background call-to-action with heading + text + button |
| Grid of quote cards with author and role |
| Heading + accordion with Q&A items |
| Contact form with name, email, message fields |
| Stats/numbers section (e.g., "10K+ Users", "99.9% Uptime") |
| Team grid with member cards (image + name + role) |
| Logo cloud / client logos row |
| Email signup with heading + input + button |
| Feature comparison table (2-3 columns with checkmarks) |
| Process/how-it-works steps (numbered, with descriptions) |
| Multi-column footer (about, links, contact, social) |
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 build2. 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:
BRICKS_SITES: Comma-separated list of site identifiers (e.g.,main,staging,client)Per-site variables: For each site ID, set
BRICKS_{ID}_URL,BRICKS_{ID}_USERNAME, andBRICKS_{ID}_PASSWORDTool usage: Every tool accepts a
siteparameter. 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
Available Tools
28 toolsbricks_add_elementA
Add a single element to a page. Appends to existing elements. If the element has a parent, it will be added to the parent's children array automatically. Includes validation warnings.
Inputs: post_id (required), element (required), site, post_type.
bricks_bulk_update_elementsB
Update settings on multiple elements at once. Accepts an array of {element_id, settings} objects. Includes validation warnings.
Inputs: post_id (required), updates (required), site, post_type.
bricks_clone_pageB
Clone a page's Bricks content to a new page. All element IDs are regenerated to avoid conflicts.
Inputs: source_post_id (required), new_title (required), site, post_type.
bricks_create_pageB
Create a new WordPress page with Bricks content. The page will use Bricks Builder for rendering.
Inputs: title (required), site, elements, status, +2 more.
bricks_create_templateC
Create a new Bricks template with elements.
Inputs: title (required), site, elements, status, +1 more.
bricks_delete_snapshotB
Delete a specific snapshot from a page.
Inputs: post_id (required), snapshot_key (required), site, post_type.
bricks_delete_templateB
Delete a Bricks template permanently.
Inputs: template_id (required), site.
bricks_duplicate_elementA
Duplicate an element and all its descendants within the same page. New IDs are generated for all duplicated elements.
Inputs: post_id (required), element_id (required), site, post_type, +1 more.
bricks_find_elementA
Search elements within a page by type, text content, or CSS class. Returns matching elements with their IDs, settings summary, and parent chain.
Inputs: post_id (required), site, post_type, element_type, +2 more.
bricks_generate_elementA
Generate a single Bricks element JSON from parameters. LOCAL helper — no API call. Returns a ready-to-use element object with auto-generated ID.
Inputs: name (required), parent, children, settings.
bricks_generate_sectionA
Generate a complete section structure from a type. Returns a ready-to-use Bricks elements array. LOCAL helper — no API call. Types: hero, features, pricing, cta, testimonials, faq, contact, stats, team, logos, newsletter, comparison, steps, footer.
Inputs: section_type (required), heading, text, buttonText, +22 more.
bricks_get_element_treeA
Get a hierarchical tree representation of page elements (nested, not flat array). Useful for understanding page structure.
Inputs: post_id (required), site, post_type.
bricks_get_global_classesA
Get Bricks global CSS classes (stored in wp_options as bricks_global_classes). May require a custom REST endpoint if not exposed by default.
Inputs: site.
bricks_get_page_cssC
Get custom CSS for a page (stored in _bricks_page_css_2 post meta).
Inputs: post_id (required), site, post_type.
bricks_get_page_elementsB
Get the Bricks elements array for a page/post by ID. Returns the structured JSON of all elements on that page.
Inputs: post_id (required), site, post_type.
bricks_get_templateC
Get template details including its Bricks elements array.
Inputs: template_id (required), site.
bricks_list_element_typesA
List available Bricks element types with their default settings structure and examples. LOCAL tool — no API call. Use this to learn which elements and properties are available.
Inputs: filter.
bricks_list_pagesA
List pages. By default only shows pages with Bricks content. Set include_all=true to include all pages. Supports search. Returns pagination totals.
Inputs: site, per_page, page, include_all, +1 more.
bricks_list_snapshotsB
List all available snapshots for a page, sorted by most recent first.
Inputs: post_id (required), site, post_type.
bricks_list_templatesA
List Bricks templates (headers, footers, sections, content templates). Supports filtering by template_type and search. Returns pagination totals.
Inputs: site, per_page, page, template_type, +1 more.
bricks_move_elementB
Move an element to a different parent or position within parent's children array.
Inputs: post_id (required), element_id (required), new_parent_id (required), site, +2 more.
bricks_remove_elementA
Remove an element by its element ID from a page. Also removes all descendant elements.
Inputs: post_id (required), element_id (required), site, post_type.
bricks_restore_snapshotB
Restore page elements from a previously saved snapshot.
Inputs: post_id (required), snapshot_key (required), site, post_type.
bricks_set_page_cssA
Set custom CSS for a page (stored in _bricks_page_css_2 post meta).
Inputs: post_id (required), css (required), site, post_type.
bricks_set_page_elementsB
Set/replace the entire Bricks elements array for a page/post. Takes the full elements JSON array.
Inputs: post_id (required), elements (required), site, post_type.
bricks_snapshot_pageA
Save a snapshot of all page elements before making changes. Stored in post meta. Use bricks_restore_snapshot to roll back.
Inputs: post_id (required), site, post_type, label.
bricks_update_elementA
Update a specific element's settings on a page (by element ID). Merges new settings with existing ones.
Inputs: post_id (required), element_id (required), settings (required), site, +1 more.
bricks_update_templateB
Update a Bricks template's elements, title, or status.
Inputs: template_id (required), site, title, elements, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 28 tools
Each tool targets a distinct operation on a specific resource (elements, pages, templates, snapshots, CSS, global classes). There is no overlap; for instance, add_element vs create_page vs create_template are clearly different.
All tools follow the consistent pattern of bricks_<verb>_<noun> (e.g., bricks_add_element, bricks_create_page, bricks_list_templates). No mixing of conventions or inconsistent verb tenses.
28 tools is slightly above the ideal range but still reasonable for a comprehensive page builder MCP. Each tool serves a distinct purpose, and the count reflects the necessary operations for managing pages, templates, elements, snapshots, and CSS.
The tool surface covers core CRUD for pages, templates, elements, and snapshots. Advanced features like managing global classes (only get, no set/update), breakpoints, or conditions are missing, but the set is complete for basic builder workflows.
Maintenance
Related MCP Connectors
Manage WordPress blogs and WooCommerce shops from Claude, ChatGPT, Cursor and other MCP apps.
Manage your WordPress site from your AI assistant: posts, pages, media, comments and WooCommerce.
Manage your WordPress site from ChatGPT or Claude: posts, WooCommerce, SEO, images and upkeep.
Run all of WordPress from Claude, ChatGPT or Cursor: SEO, security, your WooCommerce shop and Elementor pages, on up to 10 websites in one connector. Start free. SEO: titles, descriptions and focus keywords for every page, post and product. Security & updates: core, plugin and theme updates with a live test, site health and HTTPS checks, users and roles. WooCommerce shop: products, prices, orders, coupons and customers. Elementor and many more page builders: texts, links and images. Blog posts, pages, media, comments and menus. 10 websites in one connector: all your sites in the same chat. Deploy (Agency): build a site locally and push it to your own server. Just say it: "Write SEO titles for every product." "Install all updates and check that the site still works." "Show today's orders and create a weekend coupon." You choose what your AI may change, with one switch. Install the free AlphaBridge MCP plugin from WordPress.org, connect and approve on your own site. No account, no key to copy.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to manage WordPress sites through natural conversation, supporting post creation, content updates, site queries, and draft-to-publish workflows via the WordPress REST API.9MIT
- AlicenseNot gradedqualityBmaintenanceA WordPress plugin that enables AI assistants to manage Bricks Builder sites through natural language. It provides over 20 tools for reading and writing pages, templates, global styles, and WooCommerce layouts directly from MCP-compatible clients.125GPL 2.0
- AlicenseCqualityDmaintenanceEnables AI assistants to manage WordPress content, design, SEO, WooCommerce, and more through natural language commands.1003MIT
- AlicenseBqualityBmaintenanceComprehensive MCP server for Bricks Builder with 100+ tools to manage pages, templates, styles, SEO, and content directly from AI assistants like Claude Code.11594MIT