Releases: yasirshabbirservices/Bricks-Builder-MCP
Release list
v1.14.0 — Onboarding flows + business profile skill
Improve Bricks CSS regen and styling docs
Add clear guidance to prefer global classes over per-element inline styles and document CSS compilation behavior across MCP tools (bricks-builder-mcp.php and class-tool-site.php). Update Tool_Cache: expand tool description text and rework regenerate_css to prefer Bricks\Assets_Files::regenerate_css_files, handle optional post_id via generate_post_css_file, fallback to Bricks\CSS_Files for per-post generation, and finally to Bricks\Breakpoints as a last resort. Return more detailed status info and error messages. Also adjust a comment in cache clearing. These changes improve reliability of programmatic styling workflows and give clearer instructions for when to call bricks_regenerate_css and bricks_clear_cache.
v1.13.0 — SureCart integration, CLAUDE.md, skill references
What's New
SureCart Ecommerce Integration (8 new tools)
surecart_list_products— List SureCart products with price range, stock, collectionssurecart_get_product— Full product details (sc_id, prices, stock, gallery, collections)surecart_list_collections— List product collections (sc_collection taxonomy)surecart_get_collection— Collection details with product listsurecart_list_forms— List checkout forms with shortcodessurecart_get_dynamic_tags— Reference: all 21 SureCart Bricks dynamic data tagssurecart_get_bricks_elements— Reference: all 31+ SureCart Bricks elements with controlssurecart_get_template_guide— Reference: template types, build patterns, shortcodes
CLAUDE.md & Skill References
- CLAUDE.md project development guide
- .claude/skills/ with Bricks Builder, SureCart, and Web Optimization references
- Built-in surecart skill in assets/skills/
System Prompt & Instructions
- SureCart workflow section with tool reference and dynamic tag cheatsheet
- surecart_active field in site info
- Custom instructions updated with SureCart ecommerce rules
Total tool count: ~105
Bricks Builder MCP v1.12.0
Add accessibility, performance, and schema tools
Bump plugin to v1.12.0 and register three new tools in the Tools_Registry: Tool_Performance, Tool_Accessibility and Tool_Schema. Added new MCP endpoints and capability mappings for structured data (get/update/delete), accessibility audit, SEO audit/heading structure, performance audit, and breakpoints writes. Implemented Tool_Accessibility (WCAG-style checks for images, headings, ARIA, semantic HTML, links), Tool_Performance (Core Web Vitals focused checks: images, element counts/nesting, CSS bloat, font preload hints, and performance tips) and Tool_Schema (read/update/delete stored JSON-LD per post, output JSON-LD in wp_head, and peek Yoast/RankMath). Updated registry to include the new tools and corresponding read/write cache targets.
Bricks Builder MCP v1.13.3
Add PHP 8.0 version gate; fix str_starts_with compat (v1.13.3)
Bricks Builder MCP v1.13.2
Pre-merge audit fixes (v1.13.2)
Bug #1 — CRITICAL: currentType JS var read cfg.type (undefined) instead
of cfg.currentType, causing any existing non-PHP snippet to be saved as
PHP type if saved without clicking a type tab. Fix: cfg.currentType.
Bug #2: PHP snippets with a leading <?php tag stored it in the code and
in the signature hash. Strip it on save in save_snippet() since the
editor decorator already shows it visually and eval() doesn't need it.
Bug #3: type/location fields in save_snippet() had no allowlist check.
Now validated against TYPES/LOCATIONS constants with safe fallback.
Bug #4: dead hiddenType variable referencing non-existent DOM element
removed from snippet-edit.js.
Security #5: ajax_snip_save used sanitize_url() (WP 5.9+ only alias)
instead of esc_url_raw() — now consistent with save_snippet().
Robustness #6: added explicit return after wp_send_json_error() calls
Bricks Builder MCP v1.11.0
v1.11.0 — Auto-sign code elements + accurate Bricks 2.3.6 element catalog
- sign_elements() in Bricks_Data: auto-applies wp_hash() signature to code,
svg (inline), and queryEditor elements on every set_elements() call so AI-
written PHP/JS executes on the frontend (Bricks 1.9.7+ requirement) - get_code_execution_status(): new helper to check executeCodeEnabled setting
and BRICKS_LOCK_CODE_SIGNATURES constant - bricks_code_execution_status tool: AI can verify execution is enabled before
writing code elements - Validator: warns on missing signatures and deprecated elements (html)
- get_known_elements(): rewritten with all 82 core + WooCommerce elements from
Bricks 2.3.6 source, correct nestable flags, deprecated elements marked - Correct breakpoints sourced from Bricks::Breakpoints::get_default_breakpoints():
tablet_portrait=991px, mobile_landscape=767px, mobile_portrait=478px;
removed non-existent tablet_landscape breakpoint everywhere
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
Bricks Builder MCP v1.10.0
Fix element catalog & breakpoints based on Bricks 2.3.6 source code
bricks-elements.md:
- Corrected complete element catalog from actual includes/elements/ (82 elements)
- Added nestable flag to all elements (accordion-nested, tabs-nested, slider-nested,
offcanvas, dropdown, back-to-top, div, block, container, section, nav-nested, slot) - Marked deprecated elements: html (undocumented deprecated), carousel → use slider-nested
- Added missing elements: alert, counter, rating, pie-chart, social-icons, back-to-top,
toggle-mode, map-leaflet, map-connector, instagram-feed, facebook-page, dropdown,
post-toc, post-reading-time, post-reading-progress-bar, post-sharing - Added ALL query filter elements: filter-checkbox, filter-radio, filter-select,
filter-datepicker, filter-range, filter-search, filter-submit, filter-active-filters - Added ALL WooCommerce elements (product, cart, checkout, account — 30+ elements)
- Prefer accordion-nested over accordion; tabs-nested over tabs; nav-nested over nav-menu
- toggle-mode correctly described as light/dark mode switcher (not collapsible content)
mobile-first.md:
- Corrected breakpoint widths from source (Breakpoints::get_default_breakpoints()):
tablet_portrait = 991px (was wrong 1023px/1024px)
mobile_portrait = 478px (was wrong 479px/480px)
Bricks Builder MCP v1.9.0
docs: update README and connection UI for v1.9.0 multi-client support
README.md:
- Add compatibility matrix (13 clients — Claude Code/Desktop/Web, Cursor,
VS Code, Continue, Cline/RooCode, Windsurf, Zed, Gemini CLI, Anthropic
API, legacy SSE) - Add config snippets for all clients (Cursor, Windsurf, Zed, Continue,
Cline, Anthropic API Python SDK, legacy SSE endpoints) - Add Endpoints table documenting /mcp, /sse, /messages
- Add v1.9.0 / v1.8.0 / v1.7.1 changelog section
- Update protocol version reference to MCP 2025-11-25
admin/views/settings-page.php:
- Add $sse_endpoint and $messages_endpoint variables
- Add $cfg_cursor and $cfg_windsurf config snippets
- Add Cursor, Windsurf, and Legacy SSE tabs to the client nav
- Add Cursor panel (same HTTP config as Claude Code)
- Add Windsurf panel (serverUrl format)
- Add Legacy SSE panel with copyable SSE and Messages URLs
- Update VS Code hint to mention Cline and RooCode
Bricks Builder MCP v1.8.0
fix: MCP protocol compliance for Claude.ai web (v1.8.0)
Three spec violations prevented Claude.ai (and other strict MCP clients)
from loading tools after a successful initialize handshake:
-
notifications/initialized returned HTTP 204 — spec (§6.1) requires 202.
Claude.ai checks for 202 before proceeding to tools/list; getting 204
caused it to abort the session, leaving tools never registered. -
DELETE /mcp returned 404 — spec (§6.4) requires the endpoint to accept
DELETE for session termination. Added graceful 200 acknowledgement. -
initialize response had no Mcp-Session-Id header — spec says servers
SHOULD include it. Now generated as a random 32-char hex token per
request (plugin remains stateless; the ID is not tracked server-side).
Also added: ping method handler, and a catch-all 202 for any future
unknown notifications so sessions are never broken by unrecognised methods.
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
Bricks Builder MCP v1.7.1
v1.7.1 — Fix memory system: stronger AI save instructions, session bootstrap
- Rewrote AI memory system prompt: AI now required to bootstrap site
memories (branding, CSS prefixes, global classes) on first session
when high_priority_memories is empty, save during work not at end,
and review before every session ends - Updated bricks_get_session_context description to trigger immediate
memory saves when the session context returns no memories - Bump version to 1.7.1
Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com