Elementor MCP Server

Created By
aguaitecha year ago
A simple MCP server for Wordpress Elementor
Overview

What is Elementor MCP?

Elementor MCP is a simple MCP (Management Control Protocol) server designed for managing Elementor data on WordPress pages. It allows users to perform CRUD (Create, Read, Update, Delete) operations on Elementor content.

How to use Elementor MCP?

To use Elementor MCP, you can install it via Smithery or configure it in your mcp.json file. You need to provide the target website's URL, username, and application password as environment variables.

Key features of Elementor MCP?

  • Perform CRUD operations on Elementor data.
  • Easy installation via Smithery CLI.
  • Supports configuration through JSON files for different operating systems.

Use cases of Elementor MCP?

  1. Managing Elementor content for WordPress websites.
  2. Automating updates to Elementor pages.
  3. Integrating Elementor with other applications through API calls.

FAQ from Elementor MCP?

  • What is the purpose of Elementor MCP?

Elementor MCP is designed to facilitate the management of Elementor data on WordPress, making it easier to handle content updates.

  • Is Elementor MCP free to use?

Yes! Elementor MCP is open-source and free to use.

  • What are the system requirements for Elementor MCP?

Elementor MCP requires Node.js and a compatible WordPress installation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aguaitech
Star
0
Language
JavaScript
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