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, 25% off for the GitHub community: use code
MSRGITat emcptools.com/pricing.
Build pages. The full Elementor workflow, containers, widgets, templates, global styles, and atomic elements for Elementor 4.0+. Also Gutenberg blocks, and a builder-agnostic theme builder for headers, footers, and archives.
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.
WooCommerce's native Brands API is covered by list-brands, get-brand, create-brand, and update-brand inside the Woo read/write dispatchers. Brand writes support no-write validation with dry_run:true, use existing image attachment IDs for logos, and reuse the active SEO integration's term tools for SEO metadata.
If generated Elementor styling is stale, enable regenerate-css under Tools → Page Management, then call it with { "post_id": 123 } to invalidate one editable page's CSS/render/asset data. Site-wide invalidation uses { "scope": "site", "confirm": true } and requires administrator permission; Elementor rebuilds on the next frontend request. This does not purge CDN or other plugins' caches.
For classic container grids, Elementor defaults to two rows. Set settings.grid_rows_grid to { "unit": "fr", "size": 1 } for a single row. Supply all four sides of margin/padding/border dimensions; mixed blank sides produce a warning because Elementor can omit the whole CSS rule. Blanks are not automatically converted to zero.
Elementor is optional. Every WordPress domain works without it; installing Elementor unlocks the page-building family.
- 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
The Connection tab in the admin 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.
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.
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 50+ industry-specific prompts is included with Pro.
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)