This is a simple MCP server for Elementor. It is used to perform CRUD operations on the Elementor data for a given page.
This is a simple MCP server for Elementor. It is used to perform CRUD operations on the Elementor data for a given page. Exposed over MCP by the elementor mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Everything the assistant can do here goes through one of these:
WP_URL — The URL of the target websiteWP_APP_USER — The username of the target website. Note: it's the username to log in to the target website, not the application nameWP_APP_PASSWORD — The application password of the target website, keep the space. You can create one in the target website's WordPress dashboard, see [GeneratingWindows — The Windows tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 3 environment variables: WP_URL, WP_APP_USER, WP_APP_PASSWORD. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Elementor MCP's toolset — WP_URL, WP_APP_USER, WP_APP_PASSWORD and 1 more — is a fair guide to whether it matches your workflow. It is maintained by aguaitech; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Elementor MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| WP_URL | The URL of the target website. |
| WP_APP_USER | The username of the target website. Note: it's the username to log in to the target website, not the application name. |
| WP_APP_PASSWORD | The application password of the target website, keep the space. You can create one in the target website's WordPress dashboard, see [Generating Manually Section in this page](https://make.wordpress.org/core/2020/11/05/ap |
| Windows | The Windows tool exposed by this server. |
### Windows
```json
{
"mcpServers": {
"Elementor MCP": {
"command": "cmd",
"args": ["/c", "npx", "-y", "elementor-mcp"],
"env": {
"WP_URL": "https://url.of.target.website",
"WP_APP_USER": "wordpress_username",
"WP_APP_PASSWORD": "Appl icat ion_ Pass word"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| WP_URL | Endpoint or connection string the server talks to. | Yes |
| WP_APP_USER | Configuration value read at startup. | Optional |
| WP_APP_PASSWORD | Configuration value read at startup. | Optional |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.