Elementor Mcp Agent MCP Server

elementor-mcp-agent npm v1.3.0

Published by mogacode-ma — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Agentic MCP server for WordPress Elementor — multi-site management, safe Elementor data editing, template import/export, CSS flush, version tracking. Built for agencies running many client sites.

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 99 − adoption risk = 92/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 1.2 = 99. What the published surface and source actually contain:

PointsWhat was foundCategory
−1.2 Package runs install-time scripts MTC-SUP-010 supply-chain

2. Client adoption risk — 99 − 7 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

high Shell/command execution in server code (dist/server.js)MTC-SRC-002

In the server's implementation (`dist/server.js:271`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: import { spawn } from "child_process"; async function detectWpCliPath(site, sshOpts) { if (site.ssh?.wp_cli_path) ret

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/server.js

medium Hardcoded egress to an external endpoint (dist/server.js)MTC-SRC-003

In the server's implementation (`dist/server.js:2068`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const free = await fetch("https://api.wordpress.org/plugins/info/1.0/elementor.json", { headers: { "User-Agen

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/server.js

low Package runs install-time scripts (postinstall)MTC-SUP-010

"elementor-mcp-agent" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.

Evidence: node scripts/postinstall.cjs || true

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package elementor-mcp-agent

Tools 34

Each tool and what it can reach — statically extracted from the published source.

  • apply_template_to_pageingests untrusted input
  • read_page_elementoringests untrusted input
  • read_widgetingests untrusted input
  • add_widgetno sensitive capability
  • bulk_find_replace_siteno sensitive capability
  • check_elementor_versionsno sensitive capability
  • compare_screenshotsno sensitive capability
  • delete_widgetno sensitive capability
  • duplicate_elementor_pageno sensitive capability
  • duplicate_widgetno sensitive capability
Show 24 more tools ↓
  • elementor_find_replaceno sensitive capability
  • export_elementor_templateno sensitive capability
  • fleet_find_replaceno sensitive capability
  • import_elementor_templateno sensitive capability
  • list_elementor_backupsno sensitive capability
  • list_elementor_pagesno sensitive capability
  • list_elementor_templatesno sensitive capability
  • list_global_widgetsno sensitive capability
  • list_sitesno sensitive capability
  • list_widgets_in_pageno sensitive capability
  • move_widgetno sensitive capability
  • ping_siteno sensitive capability
  • preflight_checkno sensitive capability
  • restore_elementor_backupno sensitive capability
  • restore_from_fileno sensitive capability
  • screenshot_pageno sensitive capability
  • site_healthno sensitive capability
  • swap_widget_typeno sensitive capability
  • update_widget_settingsno sensitive capability
  • wp_cli_runno sensitive capability
  • wp_elementor_flush_cssno sensitive capability
  • wp_plugin_listno sensitive capability
  • wp_plugin_updateno sensitive capability
  • wp_search_replaceno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.3.0 latest A 92/100 3 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/elementor-mcp-agent/badge.svg)](https://mcptrustchecker.com/registry/elementor-mcp-agent)
HTML
<a href="https://mcptrustchecker.com/registry/elementor-mcp-agent"><img src="https://mcptrustchecker.com/registry/elementor-mcp-agent/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/elementor-mcp-agent/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan elementor-mcp-agent --online

Use the free API → How scoring works

More in AI & Agents