Elementor Mcp Agent
Manage WordPress Elementor layouts, templates, and safe multi-site edits from your agent when you run client sites or your own marketing stack on Elementor.
Overview
Elementor MCP Agent is a MCP server for the Build phase that performs agency-grade multi-site WordPress Elementor edits, templates, and version-safe changes from your agent.
What is this MCP server?
- Agency-grade Elementor MCP v1.3.0 with multi-site support and version-aware edits
- Safe edit patterns, templates, and site operations via stdio npm elementor-mcp-agent
- Configure ELEMENTOR_MCP_SITES JSON or ELEMENTOR_MCP_CONFIG_PATH for credentials
- Optional ELEMENTOR_MCP_DEFAULT_SITE_ID when tools omit site_id
- WordPress application_password auth per site object in env config
- Server version 1.3.0
- stdio npm identifier elementor-mcp-agent
- Three documented env vars: ELEMENTOR_MCP_SITES, ELEMENTOR_MCP_CONFIG_PATH, ELEMENTOR_MCP_DEFAULT_SITE_ID
What problem does it solve?
Freelance WordPress builders drown in repetitive Elementor clicks across many client sites and fear agents making unsafe live edits without guardrails.
Who is it for?
Solo agencies and indie builders maintaining multiple Elementor WordPress sites who want MCP-driven template and content updates from Claude Code or Cursor.
Skip if: Headless-only SaaS teams with no WordPress, or sites where Elementor is not installed.
What do I get? / Deliverables
After configuring elementor-mcp-agent with site credentials, your agent can apply structured, multi-site Elementor operations with safer edit semantics and template control.
- Agent-driven Elementor template and page updates per configured site
- Multi-site switching with optional default site id
- Safer, version-aware edit workflows compared to raw REST guesswork
Recommended MCP Servers
Journey fit
Shelved under Build/frontend because the MCP drives page builder and template work on live WordPress sites, with agency workflows spanning several client properties. Frontend fits Elementor’s visual site and template editing; integrations subfacet applies via WordPress application passwords and multi-site JSON config.
How it compares
WordPress Elementor site MCP, not a mobile device automation or generic skill linter.
Common Questions / FAQ
Who is elementor-mcp-agent for?
It is for WordPress and Elementor practitioners, especially multi-site freelancers, who want MCP tools for templates and guarded live edits.
When should I use elementor-mcp-agent?
Use it during Build and launch prep when you are updating layouts, templates, or client pages and want the agent to act through Elementor with explicit site config.
How do I add elementor-mcp-agent to my agent?
Install elementor-mcp-agent from npm, set ELEMENTOR_MCP_SITES or ELEMENTOR_MCP_CONFIG_PATH with site url and application_password, optionally ELEMENTOR_MCP_DEFAULT_SITE_ID, then register the stdio MCP server in your host.