Tools overview
EMCP Tools ships 207 MCP tools (162 of them free): the full Elementor page-building workflow, a Gutenberg block toolset, a builder-agnostic theme builder (EMCP Themer), eight domains beyond Elementor for general WordPress management, and integrations for popular plugins. How many actually register on your site depends on which of those plugins you run. See Requirements for the breakdown.
Every tool name in MCP is prefixed with emcp-tools/. The WordPress MCP Adapter converts the slash to a dash when exposing tools to clients, so the internal ability emcp-tools/list-widgets shows up in your AI client as emcp-tools-list-widgets.
Elementor categories
Section titled “Elementor categories”| Category | Free | Pro adds | E4.0 adds |
|---|---|---|---|
| Query & Discovery | 7 | ||
| Page Management | 5 | ||
| Layout & Structure | 10 | ||
| Widgets (catalog-backed) | 4 | 1 | |
| Templates & Theme Builder | 2 | 6 | |
| Global Settings | 2 | ||
| Composite | 1 | ||
| Stock & Media | 4 | ||
| SVG Icons | 1 | ||
| Custom Code | 1 | 3 | |
| Widget Builder (Pro, opt-in) | 8 | ||
| Atomic Elements (E4.0+) | 14 |
Gutenberg & theme building (new in v3.1.0)
Section titled “Gutenberg & theme building (new in v3.1.0)”Config-independent: these register regardless of Elementor.
| Category | Tools | Default |
|---|---|---|
| Gutenberg blocks | 10 | enabled (always-on) |
| EMCP Themer (theme builder) | 8 | enabled (module on by default) |
WordPress categories (beyond Elementor)
Section titled “WordPress categories (beyond Elementor)”New in v3.0.0: general WordPress management over MCP, built on WordPress core (these never touch _elementor_data).
| Category | Tools | Default |
|---|---|---|
| WordPress Content | 8 (+3 core) | enabled |
| WordPress Settings | 2 | enabled |
| Plugins & Themes | 13 | 4 read enabled · 9 writes off |
| Media Library | 3 | get/update on · delete-media off |
| WordPress Users | 4 | reads on · writes off |
| Performance Analyzer | 1 | enabled |
| Security & Malware Scanner | 1 | enabled |
| Filesystem | 6 | 3 read enabled · 3 writes off |
| Database | 6 | 3 read enabled · 3 writes off |
Plugin integrations
Section titled “Plugin integrations”These speak to a specific third-party plugin, and each registers only when that plugin is active, so you only ever see tools for what you actually run. Most follow a two-dispatcher pattern: one Read tool and one Write tool, each taking an operation and an arguments object.
| Integration | Tools | Default |
|---|---|---|
| ACF (Advanced Custom Fields) | 2 | acf-read on · acf-write off |
| WooCommerce | 2 | read on · write off |
| Forms (8 plugins) | 16 | reads on · writes off |
| SEO (7 plugins) | 14 | reads on · writes off |
| Elementor Addons (3 plugins) | 4 | reads on · uae-write off |
Elementor Addons deliberately breaks the two-dispatcher pattern: Essential Addons and Premium Addons get a discovery tool only, because their widgets register into Elementor’s own registry and are placed with the ordinary add-free-widget. Ultimate Addons for Elementor is both a widget pack and a template plugin, so it keeps the full pair.
Finding the right widget: discover → inspect → act
Section titled “Finding the right widget: discover → inspect → act”As of v3.0.0 the 62 per-widget convenience tools and the old universal add-widget were replaced by a catalog-backed model, five tools that reach every widget without bloating the per-turn tool list:
- Discover:
list-widgetsreturns a compact catalog index; filter bytier/category/search. - Inspect:
get-widget-schemareturns curated params for a widget (or atypes[]batch); passfull: truefor the raw control schema. - Act:
add-free-widget/add-pro-widget(Pro only) create the widget with catalog defaults merged in;update-widgetedits an existing one.
No capability is lost. Every widget and every curated parameter is still reachable, and any valid Elementor control passes straight through. See Widgets.
Disabled-by-default tools
Section titled “Disabled-by-default tools”98 of the 207 tools ship off by default, leaving 109 enabled, and they are opt-in from EMCP Tools → Tools. The pattern is consistent: anything that writes, deletes, or renders site-wide starts disabled. That covers SEO & Accessibility (Pro), Widget Builder (Pro), PHP Snippets, the Plugins & Themes write tools, delete-media, the Users write tools, the Filesystem and Database write tools, WP-CLI, the Themer PHP templates, and the write dispatcher of every plugin integration (ACF, WooCommerce, Forms, SEO, Elementor Addons).
So your active surface is always smaller than the installed count until you deliberately turn things on.
Permission model
Section titled “Permission model”Every tool runs a WordPress capability check before executing. Read tools require edit_posts; write tools add an ownership check on the target. Global settings, WordPress settings, and code snippets require manage_options; user tools require list_users / create_users / edit_users; plugin & theme tools each check their matching *_plugins / *_themes cap.
The full permission matrix is documented in the plugin’s CLAUDE.md on GitHub.
Disabling tools
Section titled “Disabling tools”You can toggle individual tools on or off from EMCP Tools → Tools in the WordPress admin. Categories are grouped under an Elementor tab and a WordPress tab. The choices persist in the emcp_tools_disabled_tools option and apply to every MCP request, including the REST endpoint that AI clients use.
For clients with strict tool caps (Antigravity, Gemini API), flip on Compact tool mode at the top of the same page. It collapses the whole surface to 3 dispatcher meta-tools. See Compact tool mode.