About Bricks Builder MCP
Bricks Builder MCP is an MCP server published by webshr in the AI category: a Model Context Protocol (MCP) server that provides AI assistants with full access to https://bricksbuilder.io page content, enabling programmatic page building, template management, and element manipulation through natural language.
The repository has 8 stars and 3 forks, with the last commit 6 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.
Install
git clone https://github.com/webshr/bricks-builder-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Bricks Builder MCP
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 3 days ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- !License declaredNo license file. Legally you have no right to use it in a product.
- !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
1 check has not been run yet.
README
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)
- 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
Available Tools (29)
Element Manipulation (10 tools)
| Tool | Description |
|---|---|
bricks_get_page_elements |
Get the Bricks elements array for a page/post by ID |
bricks_set_page_elements |
Set/replace the entire Bricks elements array |
bricks_add_element |
Add a single element with automatic parent-child linking and validation |
bricks_update_element |
Update a specific element's settings (shallow merge) |
bricks_remove_element |
Remove an element and all its descendants |
bricks_find_element |
Search elements by type, text content, or CSS class |
bricks_bulk_update_elements |
Update multiple elements at once with validation |
bricks_move_element |
Move element to a different parent or position |
bricks_duplicate_element |
Deep-clone element and descendants with new IDs |
bricks_get_element_tree |
Get hierarchical nested tree view of page structure |
Snapshot / Rollback (4 tools)
| Tool | Description |
|---|---|
bricks_snapshot_page |
Save page state before making changes |
bricks_restore_snapshot |
Restore page elements from a saved snapshot |
bricks_list_snapshots |
List available snapshots for a page |
bricks_delete_snapshot |
Delete a specific snapshot |
Template Management (5 tools)
| Tool | Description |
|---|---|
bricks_list_templates |
List templates with type filter (header/footer/section/content/popup) and search |
bricks_get_template |
Get template details including elements array |
bricks_create_template |
Create a new template with type and elements |
bricks_update_template |
Update template elements, title, or status |
bricks_delete_template |
Delete a template permanently |
Page Management (3 tools)
| Tool | Description |
|---|---|
bricks_list_pages |
List pages with Bricks content (or all pages with include_all). Supports search. |
bricks_create_page |
Create a new page with Bricks content |
bricks_clone_page |
Clone a page's Bricks content with regenerated IDs (respects source CPT) |
CSS & Styling (4 tools)
| Tool | Description |
|---|---|
bricks_get_global_classes |
Get Bricks global CSS classes |
bricks_set_global_classes |
Add or update global CSS classes (merge or replace mode) |
bricks_get_page_css |
Get custom CSS for a page |
bricks_set_page_css |
Set custom CSS for a page |
Local Helpers (2 tools — no API calls)
| Tool | Description |
|---|---|
bricks_list_element_types |
List 22 available element types with defaults and examples |
bricks_generate_element |
Generate a single Bricks element JSON |
Site Settings (1 tool)
| Tool | Description |
|---|---|
bricks_get_settings |
Get Bricks global settings |
Requirements
- Node.js 18+
- WordPress site with Bricks Builder theme installed and active
- WordPress Application Password
Quick Setup
1. Install the companion WordPress plugin
Copy bricks-mcp.php to your WordPress mu-plugins directory:
wp-content/mu-plugins/bricks-mcp.php
This mu-plugin is required — it exposes Bricks Builder data to the REST API. It:
- Enables REST API access for the
bricks_templatepost type - Registers
metaREST fields on pages, posts, and templates for reading/writing_bricks_page_content_2(elements) and_bricks_page_css_2(custom CSS) - Adds custom endpoints:
GET /bricks/v1/get-global-classes— read global CSS classesPOST /bricks/v1/set-global-classes— write global CSS classesGET /bricks/v1/get-settings— read Bricks global settings
All endpoints require authentication (edit_posts capability; manage_options for settings).
2. Clone and build
git clone https://github.com/webshr/bricks-builder-mcp.git
cd bricks-builder-mcp
npm install
npm run build
3. Configure in Claude Code
Add to ~/.claude.json:
{
"mcpServers": {
"bricks": {
"command": "node",
"args": ["/path/to/bricks-builder-mcp/dist/index.js"],
"env": {
"BRICKS_SITES": "prod,test",
"BRICKS_PROD_URL": "https://your-domain.com",
"BRICKS_PROD_USERNAME": "wp-username",
"BRICKS_PROD_PASSWORD": "application-password",
"BRICKS_TEST_URL": "https://staging.your-domain.com",
"BRICKS_TEST_USERNAME": "admin",
"BRICKS_TEST_PASSWORD": "application-password"
}
}
}
}
4. 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.,prod,test,etc.)- Per-site variables: For each site ID, set
BRICKS_{ID}_URL,BRICKS_{ID}_USERNAME, andBRICKS_{ID}_PASSWORD - Tool 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
v1.0.0
- 29 tools for full Bricks Builder management
- 10 element tools: get, set, add, update, remove, find, bulk update, move, duplicate, tree view
- 4 snapshot tools: save, restore, list, delete
- 5 template tools with type filtering (header, footer, section, content, popup)
- 3 page tools: list (with search and include_all), create, clone
- 4 CSS tools: get/set global classes, get/set page CSS
- 2 local helpers: element type catalog (22 types), element JSON generator
- Multi-site support with per-site credentials
- CPT support for all element/CSS tools
- Element validation with warnings
- Response trimming and pagination with totals
Contributing
PRs welcome. Please open an issue first to discuss changes.
License
MIT
README fetched from the repository 3 days ago. The original is authoritative.