A high-performance MCP (Model Context Protocol) server for WordPress page builders — written in Rust.
5.4MB binary · ~3MB RAM · ~1ms startup · 75 tools
Purpose
This project provides AI assistants with deep, structured access to WordPress page builders through the Model Context Protocol. Rather than treating WordPress pages as opaque HTML blobs, it exposes the underlying page builder data model — allowing AI tools to read, create, and modify content at the element level with full awareness of widget types, settings schemas, and design tokens.
MCP server for WordPress page builders — currently Elementor, with plans to support any page builder with automatic detection
Current State: Elementor
At present, the server is purpose-built for Elementor — the most widely used WordPress page builder. It integrates directly with Elementor's native REST API (elementor/v1/*) rather than the generic WordPress REST API, giving it access to element trees, widget schemas, global design tokens, experiments, and the live editor via Chrome DevTools Protocol.
Key capabilities in the current Elementor implementation:
Element-level CRUD — add, update, move, duplicate, or remove individual widgets without replacing the entire page
Widget schema validation with "did you mean?" suggestions for incorrect setting keys
Global design token management (colors, typography)
Elementor kit settings, feature flags, and CSS cache control
Theme Builder template creation with automatic condition activation
Visual tools — screenshots with inline images, side-by-side stitched comparison, CDP-based DOM inspection
CSS-to-Elementor mapping — convert computed styles to Elementor widget settings
One-shot visual parity — match_styles extracts CSS from a reference, converts, and applies in one call
Live editor control via CDP — open editor, select widgets, change settings, save
Custom widget scaffolding — generate and deploy PHP widget classes via a companion bridge plugin
Local environment detection — auto-detect and boot DDEV/Lando projects
Page interaction before capture — pre_js on all visual tools to click menus, dismiss banners, etc.
Future Direction: Universal Page Builder Support
The long-term vision is to make this server the single MCP integration point for any WordPress page builder. When a request comes in, the server will:
Detect which page builder(s) are active on the WordPress installation (Elementor, Beaver Builder, Bricks, Divi, Gutenberg blocks, etc.)
Automatically route requests to the appropriate handler for that builder
Expose a unified tool interface regardless of which builder is installed — so AI assistants don't need to know or care which builder is in use
This means a single MCP configuration will work across different WordPress sites regardless of their page builder choice, and AI tools will be able to work with any builder's data model through a consistent API.
Quick Start
# Build from source
git clone https://github.com/juslintek/mcp-for-page-builders
cd mcp-for-page-builders
cargo build --release
Add to your MCP client config (e.g. .kiro/settings/mcp.json, claude_desktop_config.json):
Use the `authenticate` tool with wp_url "https://your-site.com"
This opens a browser for WordPress Application Password approval — no credentials in config files. Credentials are stored internally in ~/.config/mcp-for-page-builders/.
Multi-Site Support
Connect multiple sites. Switch between them without restarting:
Use `connect_site` to add a site, or `switch_site` to change the active site.
Legacy: Environment Variables
You can still pass credentials via environment variables if preferred:
WordPress credentials are optional. Without WP_URL, the server starts in CDP-only mode — all visual and schema tools work, WordPress-dependent tools return a helpful error pointing to setup_wizard.
All visual tools accept pre_js (JavaScript to execute after page load) and wait_ms (delay after execution). Use this to click menus, dismiss cookie banners, or expand sections before capture.
If pre_js executes but the page state doesn't change, a warning is included in the result.
Widget Schema & Validation
Tool
Description
list_widgets
List all widgets with bundled schemas
get_widget_schema
Full schema for a widget type — valid settings, aliases
validate_element
Validate element JSON with "did you mean?" suggestions
CSS Mapping
Tool
Description
css_to_elementor
Convert CSS properties to Elementor widget settings JSON
Templates
Tool
Description
create_template
Create template with auto-activated Theme Builder conditions
update_template
Update template data, title, or conditions
get_template
Get template by ID
list_templates
List all templates
delete_template
Delete a template
WordPress Options
Tool
Description
get_wp_option
Read any WordPress option
set_wp_option
Write any WordPress option
Live Editor
Tool
Description
elementor_editor
Control Elementor editor via CDP — open, select widget, set setting, save
Widget Scaffolding
Tool
Description
install_bridge
Install the MCP Bridge companion plugin
create_widget
Scaffold and deploy custom Elementor widget PHP class
Environment & Setup
Tool
Description
ensure_site
Check URL reachability, auto-detect and boot DDEV/Lando environments
setup_wizard
Interactive WordPress connection setup with options and instructions
Multi-Site Management
Tool
Description
authenticate
Browser-based WordPress authentication — no credentials in config
connect_site
Add a site connection (credentials stored internally)
switch_site
Switch active site without restart (hot-reload)
list_sites
List all stored site connections
disconnect_site
Remove a stored site connection
Utilities
Tool
Description
seed_content
Create demo pages with various layouts and widgets
get_session_state
Recover context after crash — shows active site, pending ops
Local Environment Detection
The ensure_site tool auto-detects local development environments from URLs:
Pattern
Environment
Action
*.ddev.site
DDEV
Check ddev list, start if stopped, verify HTTP
*.lndo.site
Lando
Check lando list, report status
localhost:*, 127.0.0.1:*
Local
HTTP reachability check
Everything else
Remote
HTTP reachability check
CDP tools automatically check reachability before navigation. If a local URL is unreachable, the error suggests calling ensure_site first.
MCP Bridge Plugin
Some tools require a small companion WordPress plugin: MCP Bridge for Page Builders (mcp-bridge-for-page-builders on wordpress.org).
The plugin exposes additional REST endpoints that WordPress's built-in API doesn't provide:
mcp-for-page-builders/v1/status — health check and version probe used by install_bridge
mcp-for-page-builders/v1/option — read/write arbitrary WordPress options (used by get_wp_option, set_wp_option, and as a fallback deployment channel for mu-plugin snippets)
Without the bridge, get_wp_option and set_wp_option fall back to the standard wp/v2/settings endpoint, which only exposes a small allowlisted subset of options. The bridge removes that restriction, giving the MCP server full access to any option — including Elementor's internal configuration, Theme Builder conditions, and third-party plugin settings.
The install_bridge tool handles installation automatically using a five-step fallback chain:
Check if the bridge is already active (no-op if so)
Auto-install and activate from wordpress.org via the plugins REST API
Activate if already uploaded but inactive
Bootstrap via Code Snippets — installs the code-snippets plugin, creates a snippet that writes the bridge plugin file, activates the bridge, then removes Code Snippets entirely (no passwords or cookies needed)
Return the PHP snippet for manual installation
The bridge plugin is intentionally minimal — it adds no admin UI, no settings page, and no frontend output. Its sole purpose is to extend the REST API surface available to this MCP server.
Development
Running Tests
# Full cycle: spins up Docker WordPress, runs unit + integration tests, tears down
./tests/run.sh
# Unit tests only (no Docker needed)
./tests/run.sh --unit
# Keep environment running after tests
./tests/run.sh --keep
# Re-run tests against existing environment
./tests/run.sh --retest
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
सवाल
MCP For Page Builders कैसे इंस्टॉल करें?
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
क्या MCP For Page Builders के लिए API key चाहिए?
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
MCP For Page Builders कौन सा ट्रांसपोर्ट इस्तेमाल करता है?
MCP For Page Builders stdio पर लोकल चलता है।
MCP For Page Builders की पिछली जाँच कब हुई थी?
पिछली जाँच 2026-10-28 को हुई। MCP server for WordPress page builders — currently Elementor, with plans to support any page builder with automatic detection