MCP Tools for WordPress & Page Builders
Docs · Integrations · Changelog · Pro
Turn your WordPress site into something an AI agent can actually operate.
EMCP Tools is a WordPress plugin that exposes your site as MCP tools, so Claude, Cursor, and any other MCP client can build Elementor pages, write content, manage plugins and users, audit performance and security, and drive the plugins you already run. It builds on the WordPress MCP Adapter, which ships bundled.
EMCP Pro, 10% off for the GitHub community: use code
EMCPGITat emcptools.com/pricing.
What it does
225 Free tools, 552 total with Pro. These are catalog totals across all supported integrations, including 327 Pro tools. The tools available to your AI client depend on your installed plugins, selected builder, and enabled tools. See the tool catalog for every tool and what it needs.
Build pages. Dedicated integrations cover Elementor, Bricks, Breakdance, Avada, Divi 5, Thrive Architect, Oxygen, Kirki, WPBakery, Beaver Builder, BeBuilder and Visual Composer. Select one standalone builder while Gutenberg stays available. Spectra, Kadence Blocks, GenerateBlocks, Blocksy Blocks and Otter Blocks have independent toggles. Pro adapters expose native features verified for supported vendor versions; see each bundled skill for scope and limitations.
Run the site. Content and taxonomies, media, users, settings, plugins and themes, nav menus, the filesystem, and the database, all over MCP.
Understand and undo. One-call page snapshots, public front-end HTML inspection, content search across your own pages and templates, a change ledger with rollback, and read-only performance and security scans that return a scored report.
Speak your plugins. Integrations that register only when the plugin is active: ACF, Meta Box, WooCommerce, 8 form builders, 7 SEO plugins, and the Elementor addon packs. See the integrations directory.
Animate with GSAP. Pro includes an opt-in local GSAP 3.15.0 integration: core plus all 24 distributed plugins, stable WordPress handles, context and per-plugin switches, and MCP read/write management.
Elementor is optional. Every WordPress domain works without it; installing Elementor unlocks the page-building family.
Install
- Download the latest
emcp-tools-*.zipfrom Releases. - In WordPress: Plugins → Add New → Upload Plugin, then activate.
- Open the EMCP Tools menu in the admin sidebar.
Free installs update in place from Dashboard → Updates.
Requires WordPress 6.9+ and PHP 8.1+. Elementor 3.20+ is optional (4.0+ for atomic elements). The MCP Adapter and Abilities API need no separate install.
→ Installation guide · Requirements
Connect your AI client
The Connection screen in the admin walks you through four steps and generates a ready-to-paste config for your client, including a one-click .mcpb bundle for Claude Desktop. That is the fastest route, and it fills in your site URL and credentials for you.
Step-by-step guides per client:
Claude Code · Claude Desktop · Cursor · VS Code · Antigravity · ChatGPT · WP-CLI · OAuth · Multiple sites
Tools not showing up? Start with no tools appearing or tool cap exceeded.
Safe by default
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.
Anything that writes, deletes, or renders site-wide ships disabled and is opt-in from EMCP Tools → Tools. Destructive operations additionally require an explicit confirm: true. Administrators cannot be edited over MCP, there is no delete-user tool, and filesystem access is confined to the WordPress root with automatic backups and an audit log.
Sample prompts
The prompts/ directory has five complete landing-page blueprints, design system, structure, images, and animations, that build an entire page from a single paste: Local Business, Dental Clinic, Developer Portfolio, Hair Salon, Car Wash.
A library of 100 prompts across 20 categories, 50 landing pages and 50 complete websites, is included with Pro.
Contributing
Bug reports, feature requests, and pull requests are all welcome. See CONTRIBUTING.md.
- Fork the repo
- Create a branch (
git checkout -b feature/amazing-tool) - Make your changes and test locally
- Open a Pull Request
Contributors: @msrbuilds (author and maintainer)