Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Related Servers

Alternatives to elementor-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      11
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Agency-grade MCP server for WordPress Elementor — multi-site management for 120+ WordPress sites with safe edits (backup + auto-rollback + post-write verification), template export/import, global widget detection, CSS flush, WP-CLI escape hatch, and headless Chrome screenshots. 34 tools across pages, widgets, templates, bulk find/replace, and fleet operations.
      34
      101 npm
      3
      MIT

    TDQS

    A3.6/5.0

    Scored across 50 tools

    Disambiguation4/5

    The read tools are explicitly layered — get_outline for structure, get_element for one subtree, get_page_tree for everything, get_page for metadata — and the descriptions state when to use which, which is unusually good for a set this size. A few clusters still require careful reading (batch_edit vs replace_page_tree vs duplicate_page, and snapshot vs revision restore), but no two tools are truly interchangeable.

    Naming Consistency4/5

    Everything is snake_case with a uniform elementor_ prefix, and the vast majority is verb_noun (list_sites, create_page, update_element, restore_snapshot). Minor deviations are noun-only names like elementor_custom_css and elementor_widget_usage, plus the opaque elementor_native_mcp_call, but the pattern stays predictable.

    Tool Count2/5

    Fifty tools is a heavy surface even for a broad site-building domain, and several groups are redundant in scope: four ways to read page content, five snapshot/revision tools, and both duplicate_page and duplicate_element. A capable agent can navigate it, but the sheer count raises selection cost and invites over-fetching of large trees.

    Completeness4/5

    Coverage is strong end to end: page and element CRUD, structural wrapping/reordering, atomic batch editing, templates, snapshots and revisions, globals, media, and site-wide search/replace. The notable gaps are lifecycle gaps on templates (no update or delete, only save/export/import) and no media deletion or update, which agents will hit when managing the template library.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues