Skip to main content
Glama
sabiertas

Bricks Builder MCP Server

by sabiertas

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BRICKS_SITESYesComma-separated list of site identifiers (e.g., 'main,staging'). At least one site must be configured.
BRICKS_MAIN_URLYesWordPress site URL for the 'main' site (required if 'main' is in BRICKS_SITES).
BRICKS_STAGING_URLNoWordPress site URL for the 'staging' site (if 'staging' is in BRICKS_SITES).
BRICKS_MAIN_PASSWORDYesWordPress application password for the 'main' site.
BRICKS_MAIN_USERNAMEYesWordPress username for the 'main' site.
BRICKS_STAGING_PASSWORDNoWordPress application password for the 'staging' site.
BRICKS_STAGING_USERNAMENoWordPress username for the 'staging' site.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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.

bricks_set_page_elementsB

Set/replace the entire Bricks elements array for a page/post. Takes the full elements JSON array.

bricks_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.

bricks_remove_elementA

Remove an element by its element ID from a page. Also removes all descendant elements.

bricks_update_elementA

Update a specific element's settings on a page (by element ID). Merges new settings with existing ones.

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.

bricks_bulk_update_elementsB

Update settings on multiple elements at once. Accepts an array of {element_id, settings} objects. Includes validation warnings.

bricks_move_elementB

Move an element to a different parent or position within parent's children array.

bricks_duplicate_elementA

Duplicate an element and all its descendants within the same page. New IDs are generated for all duplicated elements.

bricks_get_element_treeA

Get a hierarchical tree representation of page elements (nested, not flat array). Useful for understanding page structure.

bricks_snapshot_pageA

Save a snapshot of all page elements before making changes. Stored in post meta. Use bricks_restore_snapshot to roll back.

bricks_restore_snapshotB

Restore page elements from a previously saved snapshot.

bricks_list_snapshotsB

List all available snapshots for a page, sorted by most recent first.

bricks_delete_snapshotB

Delete a specific snapshot from a page.

bricks_list_templatesA

List Bricks templates (headers, footers, sections, content templates). Supports filtering by template_type and search. Returns pagination totals.

bricks_get_templateC

Get template details including its Bricks elements array.

bricks_create_templateC

Create a new Bricks template with elements.

bricks_update_templateB

Update a Bricks template's elements, title, or status.

bricks_delete_templateB

Delete a Bricks template permanently.

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.

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.

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.

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.

bricks_create_pageB

Create a new WordPress page with Bricks content. The page will use Bricks Builder for rendering.

bricks_clone_pageB

Clone a page's Bricks content to a new page. All element IDs are regenerated to avoid conflicts.

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.

bricks_get_page_cssC

Get custom CSS for a page (stored in _bricks_page_css_2 post meta).

bricks_set_page_cssA

Set custom CSS for a page (stored in _bricks_page_css_2 post meta).

bricks_get_settings

Get Bricks global settings (stored in wp_options as bricks_global_settings). May require a custom REST endpoint if not exposed by default.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 28 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness4/5

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

ActivityInactive
ResponsivenessNo issues