A WordPress MCP server that runs on your own site.
EMCP turns your WordPress install into a full MCP server. Any AI agent can manage content, plugins, users, media, and the database (and build Elementor pages) over the Model Context Protocol, capability-checked, with the endpoint on your own domain.
What is a WordPress MCP server?
The Model Context Protocol lets AI clients call typed tools on external systems. A WordPress MCP server exposes your site's capabilities as those tools, so an agent can operate WordPress the way a developer would, reading and writing through safe, permission-checked interfaces rather than scraping the admin.
EMCP builds on the WordPress Abilities API (core in WordPress 6.9+) and the bundled MCP Adapter to register a dedicated server at /wp-json/mcp/emcp-tools-server. It requires PHP 8.1+ and WordPress 6.9+. Direct MCP connections do not require an EMCP Cloud subscription.
One server for the whole site.
Far beyond page building. Each domain is a group of tools your agent can call, with reads on by default and sensitive writes off until you opt in:
- Content: posts, pages, any custom post type, taxonomies, and Gutenberg blocks.
- Plugins & themes: install, update, activate, and switch. EMCP, Elementor, and the active theme stay protected.
- Users & media: safe user management and full media-library control.
- Database & filesystem: read-only SQL, structured writes, and ABSPATH-confined file tools, all audit-logged.
- Performance & security: scored performance and malware/hardening reports.
- Redirect Manager: 301/302 redirects and broken-link scanning, on by default so a deleted or renamed page never leaves a dead URL.
- Integrations: ACF, Meta Box, WooCommerce, Kadence, Astra, forms and SEO plugins. See the integration catalog for current requirements and tier access.
- Sandbox & Cloud: AI-drafted custom blocks, widgets, and PHP snippets, human-reviewed before they run, with cross-site backup and a Marketplace.
Self-hosted, capability-checked, private.
Unlike gateway services, EMCP runs inside your WordPress. With a direct connection, your selected AI client exchanges requests and tool results with your site. The AI provider may process those results. If you choose the hosted EMCP Cloud gateway, requests and results also pass through that service. The AI connects as a real WordPress user (over the WP-CLI stdio bridge locally, or HTTP with an Application Password or OAuth for remote sites), and every tool call is checked against that user's capabilities. Sensitive writes require opt-in, and supported destructive operations require confirmation. Use drafts, previews and available rollback before publishing; not every change can be undone.
Two admin screens make the server itself configurable and debuggable: a Context tab for stable, site-wide instructions every connecting agent receives automatically, and an MCP Log tab recording the last 100 requests (tool, status, duration) so a connector failure can be matched to a server-side outcome without touching a terminal.
Before connecting, review our WordPress MCP permissions and security guide for authentication choices, tool controls, and a read-only first task.
Questions, answered.
Still stuck? Drop a line at [email protected] or open an issue on GitHub. Most replies are under one business day; Pro tiers go to the front of the queue.
Open the full docsRun your own WordPress MCP server today
Install EMCP, connect your AI client, and operate your whole site from a prompt: self-hosted, capability-checked, and private.