# EMCP Tools and the WordPress plugin that lets an agent run the site > EMCP Tools is a WordPress plugin that exposes a site over the Model Context Protocol, so Claude, Cursor and other clients can build pages, manage content, drive the plugins you already run and audit the site. The free tier counts 225 tools, most write operations ship disabled, and the tool totals differ between the README and the repository description. **msrbuilds/elementor-mcp** — WordPress MCP server with 234 Free tools and 547 total with Pro for building pages, managing content, and operating your site. Availability depends on installed integrations and enabled tools. - Repository: https://github.com/msrbuilds/elementor-mcp - Website: https://emcptools.com - Stars: 751 · Forks: 158 - Language: PHP - License: GPL-2.0 - Published: 2026-10-21 · Updated: 2026-10-21 · Language: en - Canonical page: https://hysenlabs.com/projects/msrbuilds-elementor-mcp ## A plugin that turns a site into an MCP server EMCP Tools is a WordPress plugin that exposes your site as Model Context Protocol tools. The stated goal is to turn a WordPress site into something an AI agent can actually operate, and the README names the clients it expects to work with, Claude, Cursor and any other MCP client. From there, the agent can build Elementor pages, write content, manage plugins and users, audit performance and security, and drive the plugins you already have installed. The technical basis is the WordPress MCP Adapter, which the plugin bundles rather than asking you to install separately. The Abilities API is bundled in the same way, and the README says both need no separate install. That matters for adoption: the usual first hour of an MCP project, spent wiring a transport and a server, is handled by the plugin. The audience is a WordPress site owner or agency that already runs a page builder and wants an agent to work inside that stack rather than beside it. It is not a general agent platform: everything here is scoped to the WordPress installation it is installed into, its plugins, its users and its content. The admin screens are a React application built with WordPress's own tooling. The build configuration for it lists a build script that runs wp-scripts build and then two extra Node steps, unit tests through jest, lint scripts for JavaScript and CSS, and Playwright for end-to-end tests: ```json "scripts": { "build": "wp-scripts build && node admin-build/build-pro.mjs && node admin-build/generate-php-icons.mjs", "start": "wp-scripts start", "test": "wp-scripts test-unit-jest --config jest.config.js", "size": "node admin-build/check-size.mjs", "lint:js": "wp-scripts lint-js admin-src admin-build", "lint:js:pro": "wp-scripts lint-js pro/admin-src", "lint:style": "wp-scripts lint-style \"admin-src/**/*.css\"", "test:e2e": "playwright test" }, ``` A size check in the build scripts and a separate lint target for the Pro admin source show that the paid tier is a distinct code path inside the same plugin. ## 225 free tools, 552 with Pro, and three different numbers The tool count is the headline number and the most slippery one. The README body says 225 free tools and 552 in total with Pro, of which 327 are Pro tools, and the badges in the README agree with the body on 225 free and 552 total. The repository description on GitHub says something different: 234 free tools and 547 in total with Pro. The two sources do not match, and a reader has no way to tell which set is current. The reason the count moves is also stated. These are catalogue totals across all supported integrations, and the tools that actually appear in your client depend on your installed plugins, your selected builder and the tools you have enabled. A site with only Elementor and WooCommerce installed will not see the ACF, Meta Box, form builder or SEO plugin tools, because those integrations register only when the plugin is active. That design decision is what keeps the tool list manageable for a client. A model with 500 tools loaded at once spends context on tool descriptions it will never use, and the README links troubleshooting pages for exactly the two failure modes you would expect: no tools appearing, and the tool cap being exceeded. So the practical reading is that the catalogue totals describe the ceiling, not your installation. The tool reference on the project's documentation site is the place to check which tool needs what. ## Installation is a zip upload, and the requirements are narrow The install path is ordinary WordPress plugin installation. You download the latest emcp-tools-*.zip file from the GitHub releases, then in WordPress go to Plugins, Add New, Upload Plugin, and activate it. After that you open the EMCP Tools menu in the admin sidebar. Free installations update in place from the Dashboard and Updates screen, which is worth knowing if you plan to keep the plugin on for a long time. The requirements are WordPress 6.9 or newer and PHP 8.1 or newer. Elementor is optional, and the plugin makes that point twice: every WordPress domain works without it, and installing Elementor simply unlocks the page-building family of tools. If you do use it, Elementor 3.20 or newer is the baseline, and 4.0 or newer is needed for atomic elements. That optionality cuts both ways. It means the plugin is not a page builder plugin with a transport bolted on, and it also means a site without a builder gets a smaller set of page tools. The README also points out that the Pro adapters expose native features verified for supported vendor versions, and that each bundled skill documents its own scope and limitations, which is the difference between a feature you can rely on and one that depends on the builder version you happen to run. The releases move quickly. The tagged versions are v3.20.0 on 2026-10-15, v3.19.3 on 2026-10-11 and v3.19.2 on 2026-10-10, and the last push was on 2026-10-16. The project is not archived. ## Connecting a client: four steps and a generated config The Connection screen in the WordPress admin is the entry point for wiring a client. It walks you through four steps and generates a ready-to-paste configuration for your client, filling in the site URL and credentials for you, and it also offers a one-click .mcpb bundle for Claude Desktop. The README calls that the fastest route. Behind it, the project publishes per-client guides for Claude Code, Claude Desktop, Cursor, VS Code, Antigravity, the ChatGPT app, WP-CLI and OAuth, plus a page for connecting multiple sites. The presence of a WP-CLI guide is a signal about the intended audience, since command-line access to the same tools is what a site operator rather than a clicker tends to want, and the OAuth guide suggests the plugin is expected to run behind an authenticated boundary rather than only on a laptop. The website hosting the guides, emcptools.com, carries the documentation, the integrations directory, a changelog and the pricing page for the Pro tier, and the README links a tool reference with a permission model section. The repository itself also ships an mcp-config-examples.json file, which is a useful reference if you would rather write the client configuration by hand than paste the generated one. ## Writes ship disabled and destructive calls need confirm: true The permission model is the part to read before pointing an agent at a live site. The README states that every tool runs a real WordPress capability check before it does anything, so an agent can only do what the authenticating user could do by hand. That framing is the important one: the plugin is not inventing a separate privilege system, it is reusing the one WordPress already has. On top of that baseline, anything that writes, deletes or renders site-wide ships disabled and has to be switched on from the EMCP Tools and Tools screen. Destructive operations require an explicit confirm: true argument in addition to being enabled. Administrators cannot be edited over MCP, there is no delete-user tool at all, and filesystem access is confined to the WordPress root, with automatic backups and an audit log behind it. Those four carve-outs are the shape of the risk. An agent that can create and publish content is already a publishing workflow with an AI in the loop, and the site-wide render tools change appearance for every visitor at once, which is why they are opt-in rather than merely guarded. The rollback story in the README, a change ledger with rollback, is the counterpart to that: if a tool does change something, there is a recorded way to undo it. The read-only side is less contentious and still useful. One-call page snapshots, public front-end HTML inspection, content search across your own pages and templates, and read-only performance and security scans that return a scored report are the tools that can be enabled without much deliberation. ## Builders, plugin integrations and an opt-in GSAP pack The page-building side is broad, with dedicated integrations for Elementor, Bricks, Breakdance, Avada, Divi 5, Thrive Architect, Oxygen, Kirki, WPBakery, Beaver Builder, BeBuilder and Visual Composer. You select one standalone builder while Gutenberg stays available, and the block editors Spectra, Kadence Blocks, GenerateBlocks, Blocksy Blocks and Otter Blocks have independent toggles rather than a single master switch. The plugin integrations follow a similar conditional model. ACF, Meta Box, WooCommerce, eight form builders, seven SEO plugins and the Elementor addon packs register only when the underlying plugin is active. In practice this means the tool list mirrors the site, and a site built on custom fields and a form plugin exposes a different surface than a WooCommerce store. Animation support sits in the Pro tier and is opt-in: a local GSAP 3.15.0 integration with core plus all 24 distributed plugins, stable WordPress handles, context and per-plugin switches, and MCP read and write management for the animation configuration. That the integration is local matters for a plugin like this, since a site that cannot reach a CDN for its animation library is a site whose pages break. Content and site operations are the third group, and they are broad: content and taxonomies, media, users, settings, plugins and themes, nav menus, the filesystem and the database, all over MCP. The prompts/ directory in the repository makes that scope concrete, with five complete landing page blueprints for a local business, a dental clinic, a developer portfolio, a hair salon and a car wash, plus a design system, structure, images and animations, and a larger library of 100 prompts across 20 categories covering 50 landing pages and 50 complete websites. ## GPL-2.0, a fast release line and a paid tier in the same plugin The plugin is licensed GPL-2.0-or-later, recorded in the LICENSE file and in the package metadata, and the README carries a matching badge. For a plugin that can modify content and render site-wide output, the licence and the Pro split are two things to look at side by side: the open source build is GPL, the paid tier is a commercial offering for the extra tools, and the README carries a promotional code for the GitHub community. The release line is fast and the versioning is conventional. Three of the last tags landed in the first half of October 2026, v3.19.2 on the 10th, v3.19.3 on the 11th and v3.20.0 on the 15th, and the last push to the repository was on 2026-10-16. A minor version bump every few days is normal for a plugin of this kind, and it means you should read the changelog on the project site before updating, since a new tag can bring new enabled tools and new defaults. The repository layout matches the split: a pro/ directory and a pro-manifest.txt at the root, separate admin sources for the paid tier, a docs/ folder, a CHANGELOG.md, a SECURITY.md, a CONTRIBUTING.md and a tests-e2e/ directory running Playwright. The presence of a dedicated security policy is worth reading if you are deploying an agent against a production site, and the AGENTS.md and CLAUDE.md files at the root suggest the project expects coding agents to work on it as well. ## Conclusion Adopt EMCP Tools if you want an AI client to work on a WordPress site you already control and you are prepared to switch on write tools deliberately, since the plugin ships them disabled and gates destructive calls behind an explicit confirm flag. Skip it if you need the whole catalogue in the free tier, because the Pro tools are where the builder depth and the GSAP integration sit, and treat the tool counts with care since the README says 225 free and 552 total while the repository description says 234 and 547. Verify first on a staging copy that the plugin activates on WordPress 6.9 with PHP 8.1, that the Connection screen produces a config your client accepts, and that the change ledger rollback behaves as expected before you let an agent write to production content. ## FAQ ### What does the EMCP Tools WordPress plugin require? It requires WordPress 6.9 or newer and PHP 8.1 or newer. Elementor is optional, and when used the baseline is Elementor 3.20 or newer, with 4.0 or newer needed for atomic elements. ### How do I install EMCP Tools in WordPress? Download the latest emcp-tools-*.zip from the GitHub releases, then in WordPress use Plugins, Add New, Upload Plugin and activate it, then open the EMCP Tools menu in the admin sidebar. Free installs update in place from Dashboard and Updates. ### How do I connect Claude or Cursor to a WordPress site with EMCP Tools? The Connection screen in the admin walks through four steps and generates a ready-to-paste config, including a one-click .mcpb bundle for Claude Desktop. Per-client guides exist for Claude Code, Cursor, VS Code, the ChatGPT app, WP-CLI, OAuth and multiple sites. ### Can an AI agent delete content or edit admin users with EMCP Tools? No. Administrators cannot be edited over MCP and there is no delete-user tool, filesystem access is confined to the WordPress root with automatic backups and an audit log, and anything that writes or deletes ships disabled and needs confirm: true for destructive calls. ## Sources - [License: GPL-2.0](https://github.com/msrbuilds/elementor-mcp/blob/main/LICENSE) - [msrbuilds/elementor-mcp on GitHub](https://github.com/msrbuilds/elementor-mcp) - [Project website](https://emcptools.com) - [README](https://github.com/msrbuilds/elementor-mcp/blob/main/README.md) - [Releases](https://github.com/msrbuilds/elementor-mcp/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/msrbuilds-elementor-mcp