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.
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 no external services.
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:
Unlike gateway services, EMCP runs inside your WordPress. No content is proxied through a third party and nothing is stored off-site. 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. A change ledger records edits with one-click rollback, and destructive tools require explicit opt-in and confirmation.
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 docsInstall EMCP, connect your AI client, and operate your whole site from a prompt: self-hosted, capability-checked, and private.