Skip to main content
Glama

Elementor MCP

CI License Node

An MCP (Model Context Protocol) server that lets AI agents design complete websites and emit import-ready Elementor v4 JSON. The agent makes design decisions; the server guarantees structurally valid output.

Quick start

npm install @smecha10/elementor-mcp
npx elementor-mcp

Register with an MCP client

Claude Desktop - add to claude_desktop_config.json:

{
  "mcpServers": {
    "elementor": {
      "command": "npx",
      "args": ["-y", "@smecha10/elementor-mcp"],
      "env": { "ELEMENTOR_MCP_OUT": "./output" }
    }
  }
}

HTTP transport:

ELEMENTOR_MCP_TRANSPORT=http ELEMENTOR_MCP_PORT=3001 npx elementor-mcp

Related MCP server: PixelCheck

Features

  • 27 section templates - hero, feature-grid, bento, timeline, portfolio-grid, team-section, countdown, error-404, and more

  • 39 widget types - heading, text, button, image, icon, accordion, form, tabs, pricing, carousel, portfolio, HTML, and more

  • Dual format output - atomic (default, Elementor v4 $$type) or classic (flat settings, maximum import compatibility)

  • Motion effects - entrance/hover animations, scroll effects, mouse effects, 3D transforms, sticky, v4 interactions

  • Dynamic tags - bind WordPress content (post-title, featured-image, author, etc.)

  • @keyframes injection - CSS keyframe animations in page-level custom_css

  • Global widgets - reusable widget definitions shared across pages

  • CSS custom properties - auto-generated from theme tokens, with dark mode support

  • Popup builder - triggers, entrance/exit animations, timing rules

  • Theme Builder - header/footer/single/archive templates with display conditions

  • Brand-driven theme generation - 6 design personalities, WCAG contrast checks

  • SEO sidecar - meta tags, Open Graph, Twitter cards, JSON-LD schema

  • Schema learning - feed real Elementor exports to learn exact widget settings

  • HTTP + stdio transport - use remotely or locally

Tools (15)

Tool

Purpose

get_intake_brief

Client questionnaire - run first

get_design_playbook

Design system and best-practice rules

generate_theme

Brand color + personality to full WCAG-checked theme

generate_seo

Meta + Open Graph + JSON-LD schema sidecar

list_widgets

All blueprint node types (with pagination)

get_widget_schema

Fields, example, and learned schema for one widget

list_motion_options

All animation/effect/interaction options

list_dynamic_tags

Dynamic tag names for WordPress content binding

list_templates

All 27 section templates (with pagination)

get_template

Params + example for one template

validate_blueprint

Compile in memory, report errors

build_page

Compile and write one import-ready .json (supports dryRun)

build_popup

Compile a popup with triggers and timing

build_site

Compile a multi-page site (supports dryRun)

learn_from_export

Ingest Elementor exports, learn widget schemas

Prompt templates (3)

Prompt

Purpose

design-website

Full intake to theme to build to SEO workflow

design-landing-page

Single landing page workflow

design-popup

Popup design workflow

Dual format output

Format

Settings

Widget names

Layout

Use case

atomic (default)

$$type wrapped

e-heading, e-paragraph

e-flexbox

Elementor v4 editor

classic

Flat settings

heading, text-editor

container

Maximum import compatibility

Most real-world Elementor installations use the flat settings format. Use "classic" for maximum compatibility.

Development

git clone https://github.com/Smecha10/elementor-mcp.git
cd elementor-mcp
npm install
npm run build      # tsc
npm run selftest    # compile sample site + verify
npm test           # vitest (16 tests)

License

MIT - see LICENSE file

Changelog

v0.5.0

  • Classic format compiler (flat settings, container elType, classic widget names)

  • 12 new template archetypes (27 total)

  • Schema learning from 7 real Elementor templates (21 types, 275 instances)

  • Vitest test framework (16 tests), GitHub Actions CI

  • 3 MCP prompt templates, pagination, dryRun option

v0.4.0

  • @keyframes injection, global widgets, HTTP transport

v0.3.0

  • Motion effects, interactions, dynamic tags, popup builder, Theme Builder conditions, CSS custom properties

v0.2.0

  • 15 TypeScript source files, 9 new Tier 1 widgets, template type support

v0.1.0

  • Initial release: blueprint compiler, 15 section templates, 6 brand personalities, SEO sidecar, schema learning

Available Tools

15 tools
build_pageBuild Elementor pageA

Compile a blueprint into import-ready Elementor JSON and write it to a file. The file can be imported in Elementor (Site Settings → Import/Export, or paste into the page template import). Set format: "classic" for flat settings output (recommended for maximum import compatibility with all Elementor versions) or format: "atomic" (default, v4 $$type-wrapped widgets). Supports popup type with triggers/timing via the popup field, Theme Builder conditions via conditions, dynamic tags via dynamic on nodes, CSS custom properties via cssVars, native background/box-shadow props in style, @keyframes CSS animations via keyframes, and reusable widget definitions via globals.

Inputs: dryRun, blueprint, outputDir, designIntensity.

build_popupBuild Elementor popupA

Compile a popup blueprint into import-ready Elementor v4 JSON with popup triggers, entrance/exit animations, and timing rules in page_settings. Use type: 'popup' with a popup config. The popup content goes in the tree.

Inputs: title (required), tree, theme, timing, +5 more.

build_siteBuild a multi-page siteA

Compile a whole site to import-ready Elementor JSON: one file per page, all sharing a theme and an optional header/footer (e.g. navbar/footer templates). Supports site-level globals for reusable widget definitions across all pages. Set format: "classic" at site level for flat settings output (recommended for maximum import compatibility), or per-page format to override. Writes a site-manifest.json alongside the pages.

Inputs: site, dryRun, outputDir, designIntensity.

generate_seoGenerate SEO meta + schemaB

Produce an SEO sidecar for a page: trimmed meta title/description, slug, robots, canonical, Open Graph + Twitter tags, JSON-LD business/page schema, and a ready-to-paste block. Returns warnings (missing description, no OG image, etc.). Keep page JSON clean — apply this at the WordPress/SEO-plugin level.

Inputs: seo.

generate_themeGenerate a brand themeA

Turn a brand color (+ optional accent) and a design 'personality' into a complete, WCAG-checked Elementor theme (colors, font pairing, radii, shadow, spacing). Drop the returned theme straight into a blueprint/site. Run after intake so the palette is built around the client's brand, not a generic template.

Inputs: brandColor (required), tone, scheme, industry, +3 more.

get_design_playbookGet design playbookA

Return the design system and best-practice rules to follow when generating a site (theme tokens, spacing scale, type scale, layout, section patterns, accessibility). Read this before building.

Inputs: no named parameters.

get_intake_briefGet client intake questionnaireA

Return the structured intake to run BEFORE designing: company facts, audience/goals, brand & design direction, content/structure, and SEO. Ask the client these, fill the returned brief skeleton, then feed brandColor+personality to generate_theme and the answers into the page copy. This is what makes each site specific instead of generic.

Inputs: format.

get_templateGet template params + exampleA

Get the parameters and a concrete example for one section template.

Inputs: name (required).

get_widget_schemaGet widget schemaA

Get the fields and a concrete blueprint example for one node type. Call before using an unfamiliar widget.

Inputs: type (required).

learn_from_exportLearn from an Elementor exportA

Ingest an Elementor JSON export and extract the settings schema of every widget it contains, merging into a persistent registry. Use this to teach the server the exact shape of widgets/settings not yet known (then get_widget_schema will show them). Provide a file path OR the JSON inline.

Inputs: json, path.

list_dynamic_tagsList dynamic tagsA

List all available dynamic tag names for use in the dynamic field of any blueprint node. Dynamic tags pull content from WordPress (post title, featured image, author, etc.). Use them in template-type documents (single, archive) to create dynamic content.

Inputs: no named parameters.

list_motion_optionsList motion & animation optionsA

List all available entrance animations, hover animations, and interaction triggers/effects/easing options for use in the motion field of any node. Call before adding motion to a blueprint.

Inputs: no named parameters.

list_templatesList section templatesA

List ready-made, theme-aware section templates (hero, feature-grid, cta-band, testimonials, pricing, faq, contact, navbar, footer). Use them in a blueprint via a node: { type: "template", template: "", params: {…} }.

Inputs: limit, offset.

list_widgetsList blueprint widgetsA

List all blueprint node types the compiler supports, grouped by category. Use this to discover what you can place in a blueprint tree. Optionally filter by category.

Inputs: limit, offset, category.

validate_blueprintValidate blueprintA

Compile a blueprint in-memory without writing a file. Returns the element count and any errors so you can fix issues before building. Supports keyframes (CSS @keyframes animations) and globals (named widget definitions for reuse). Set format: "classic" for flat settings output (recommended for maximum import compatibility) or format: "atomic" (default, v4 $$type-wrapped widgets).

Inputs: blueprint.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of the Elementor workflow: building (page/popup/site), generating (SEO/theme), getting design rules/intake/template/widget examples, listing templates/widgets/dynamic tags/motion options, learning from exports, and validating. No two tools have overlapping purposes.

    Naming Consistency5/5

    All 15 tool names follow a consistent snake_case with a verb_noun pattern (e.g., build_page, generate_theme, list_templates). There is no mixing of conventions or ambiguous verbs.

    Tool Count5/5

    15 tools is well-scoped for an Elementor MCP server. It covers intake, design, building, validation, SEO, and discovery without being excessive or insufficient.

    Completeness5/5

    The tool surface covers the full lifecycle: intake (get_intake_brief), design system (get_design_playbook, generate_theme), blueprint creation (build_page, build_popup, build_site), validation (validate_blueprint), SEO (generate_seo), and discovery (list_*, get_*, learn_from_export). No obvious gaps for its stated purpose.

    Related MCP Connectors

    Related MCP Servers

    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that automatically generates static websites from natural language instructions, creating Next.js-based sites with optional automatic deployment to AWS S3.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets AI agents use your real browser as an API, accessing any website with your login state, no keys or scrapers needed.
      1
      MIT