Capabilities
A full toolkit for AI-native WordPress.
Up to 207 MCP tools spanning Elementor page-building, Gutenberg blocks, a builder-agnostic theme builder, and full WordPress management: widgets, layout, templates, atomic elements, plus content, plugins & themes, users, media, performance, security, filesystem, and the database. If an agent can reach it in WordPress, it can do it through EMCP.
01 / Catalog-backed widgets
Every widget, one workflow
Discover → inspect → act: list-widgets indexes 62 curated widgets, get-widget-schema returns their params, and add-free-widget / add-pro-widget drop them in. Any valid Elementor control passes straight through.
list-widgetsadd-free-widgetadd-pro-widget
02 / Layout primitives
Flexbox containers, fully nested
Build the page the way a designer would: add flexbox containers, move elements between parents, duplicate with fresh IDs, and remove subtrees. Row-layout rules that trip up agents are handled for you.
add-containermove-elementduplicate-element
03 / Performance & Security
Audit and scan, read-only
analyze-performance scores server config, the database, and a page; scan-security sweeps malware heuristics, core-file integrity, hardening, and outdated software. Both return a 0–100 + A–F report. Self-contained, on by default.
analyze-performancescan-security
04 / Composite build
One call. A whole page.
The build-page tool accepts a declarative JSON tree (containers, widgets, settings, global styles, the lot) and returns a finished Elementor document. It also enforces the row-layout rules that trip up agents otherwise: column widths auto-calculated, flex_wrap and _flex_size stripped, alignment defaults applied.
05 / Beyond Elementor
Run the whole WordPress site
As of v3.0.0 EMCP reaches past the page builder: create posts, pages, and any custom post type; read and batch-update core settings; install, update, and activate plugins and themes from wordpress.org; and manage users safely, all over MCP. Built on WordPress core, these never touch _elementor_data, and the tools that can change your site (plugin/theme writes, user writes) ship disabled-by-default behind a real capability.
06 / Media & stock images
Library, alt text, Openverse
Search Creative-Commons images on Openverse and sideload them, or manage what's already there: full attachment detail, one-call alt/caption/SEO edits, and (opt-in) delete.
search-imagesget-mediaupdate-media
07 / Filesystem & database
Files and SQL, guard-railed
Read and scan any file in the install and run read-only SQL (SELECT/SHOW only). Writes (files and structured row edits) are disabled-by-default, ABSPATH-confined, auto-backed-up, and audit-logged.
read-filequerylist-tables
08 / Capability-aware
WordPress permissions, end-to-end
Every tool maps to a real WordPress capability: edit_posts, manage_options, install_plugins, edit_users. Ownership checks on every mutation, administrators are untouchable via MCP, and destructive tools are confirm-gated. Your agent only does what your user can do.
09 / OAuth sign-in
Connect without copying a password
Claude and other MCP clients sign in through a standard OAuth 2.1 flow: approve once from your WordPress login, no Application Password to paste. The token acts as the authorizing admin, so every capability check still applies. Free, HTTPS-gated, on by default; revoke any app under Connected apps.
OAuth 2.1PKCEApp password too