Elementor WordPress MCP Server

Created By
Huetardeda year ago
MCP server for interacting with Elementor and WordPress through natural language
Overview

What is Elementor WordPress MCP Server?

Elementor WordPress MCP Server is a Model Context Protocol (MCP) server designed to facilitate interaction with WordPress and Elementor through natural language, enabling AI assistants to manage WordPress content effectively.

How to use Elementor WordPress MCP Server?

To use the MCP server, you can either run it using NPX or set it up locally by cloning the repository, installing dependencies, and building the server. Configuration is done via environment variables or manually.

Key features of Elementor WordPress MCP Server?

  • Full CRUD operations for WordPress posts and pages.
  • True integration with Elementor for managing sections, columns, and widgets.
  • Automatic detection of posts and pages for Elementor functions.
  • Rich content creation capabilities.
  • Media management for the WordPress library.
  • Secure authentication using application passwords.
  • Type-safe development with TypeScript.

Use cases of Elementor WordPress MCP Server?

  1. Automating content management tasks in WordPress.
  2. Creating and updating Elementor templates programmatically.
  3. Managing media files in the WordPress library.
  4. Integrating AI assistants for enhanced content creation.

FAQ from Elementor WordPress MCP Server?

  • What are the prerequisites for using the MCP server?
    You need Node.js 18 or higher, a WordPress site with REST API enabled, and the Elementor plugin installed.

  • Is there a recommended way to configure the server?
    Yes, using environment variables is the recommended method for configuration.

  • Can I run the server locally?
    Yes, you can clone the repository and run the server locally after building it.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Huetarded
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago