Skip to main content
Glama
developer2013

bricks-mcp

by developer2013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to bricks-mcp

No user-submitted related servers found.

    Related Servers

    • Bricks MCP

      cristianuibar
      A
      license
      Not graded
      quality
      C
      maintenance
      A 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.
      122
      GPL 2.0

    • Respira for WordPress

      respira-press
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for AI-assisted WordPress editing across 12 page builders. 172 tools for content management, page builder editing, WooCommerce, SEO analysis, accessibility scanning, and site intelligence. Edits native builder formats (Elementor, Bricks, Divi, Gutenberg, Beaver Builder, and 7 more) with duplicate-before-edit safety, optimistic locking, and surgical element-level operations
      8
      MIT

    • TanukiMCP

      AppleJax2
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server for WordPress automation that enables users to manage content, themes, and site configurations using AI-driven workflows and the WordPress REST API. It provides a wide array of tools for site planning, management, and optimization compatible with tools like Cursor and Claude.
      35 npm
      1
      ISC

    • mcp-server-woocommerce

      AmitGurbani
      A
      license
      B
      quality
      C
      maintenance
      MCP server for managing WooCommerce stores through AI assistants like Claude. Provides 101 tools covering products, orders, customers, coupons, shipping, taxes, webhooks, settings, reports, and more.
      100
      83 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 115 tools

    Disambiguation3/5

    With 115 tools, several clusters overlap—page-write tools (create/update/patch/append/build), multiple backup systems (page backups, snapshots, full-state), and scripts vs. page assets. Descriptions generally differentiate them, but the sheer scale and overlapping mutation/backup boundaries make misselection likely.

    Naming Consistency4/5

    All names use snake_case with a consistent bricks_ prefix, and most follow a predictable action-oriented pattern (get_page, update_page, list_templates). Minor deviations include noun-first tools and a wp_ sub-prefix (bricks_wp_update_post, bricks_call_log, bricks_readability), but the convention remains readable.

    Tool Count1/5

    115 tools is an extreme surface for one MCP server, far past the 50+ threshold. Even a complex Bricks Builder domain would benefit from splitting into specialised servers to reduce discovery and selection overhead.

    Completeness4/5

    Coverage is unusually broad—pages, templates, globals, media, SEO, backups, security, multi-site, and WP content—so few dead ends remain. Missing delete operations for pages/posts/media/fonts are workable via WordPress admin, but they are lifecycle gaps.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources