A brief becomes a real page.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, connected.
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.
What leaves your site when an AI client connects?
WordPress executes the tools. Your chosen client receives their results. Where those results travel depends on your connection route and the model the client uses.
- Your AI client
- Your WordPress + EMCP
Requests and results travel between the client and your site. No EMCP hosted gateway is required. A local proxy, if configured, is another component in this path.
- Your AI client
- EMCP Cloud gateway
- Your WordPress + EMCP
The gateway receives and forwards requests and results. It selects a connected site and authenticates to it using a delegated site credential.
| Data | Recipient and purpose | When it applies |
|---|---|---|
| Tool arguments and results | WordPress executes the operation; the AI client receives returned content, which may include private records. | Every MCP route; the gateway also handles them when selected. |
| Prompts and model context | The selected model provider processes the context the client sends. | When using a remote model. Retention and training settings depend on that provider and account. |
| Connected-site identity and delegated credentials | EMCP Cloud and its gateway identify and authenticate to connected sites. Cloud stores the gateway refresh credential encrypted at rest; it must be usable by the service to connect. | When gateway access is enabled for the site. Encryption does not remove the service from the data path. |
| Operational activity | WordPress and gateway/Cloud components record diagnostic or activity information such as tool, site, outcome and timing. | Depends on route and enabled services. A log entry is distinct from the tool result itself. |
| Backup and sync bundles | EMCP Cloud stores the artifacts you send for backup, sync or reuse. | Optional Cloud workflows; direct MCP does not require uploading artifacts. |
| Marketplace submissions | EMCP receives submitted assets and listing information; published items are shared through the marketplace. | When you submit or publish an item. Review bundles for private content first. |
| License and purchase information | Licensing/payment services, including Freemius, handle relevant subscriptions, licenses and updates. | When using those paid services. This is separate from the MCP request path. |
Choose the route for the job
- Direct connection: useful when you want client-to-site access and manage each site's connection yourself. Start with Cursor or your preferred client guide.
- Hosted gateway: useful when you want one connection for a Cloud workspace. Confirm the target site on every task and review gateway setup and revocation.
- Either route: start with a narrow read, request only necessary fields, and choose tool access appropriate to the connected user. Follow the security setup guide.
Technical review: 26 September 2026. This explains the implemented data paths, not a retention or compliance guarantee. The current privacy policy describes the website and named services; it does not establish a complete gateway payload-retention schedule. For requirements about deletion, logs, storage location or subprocessors, confirm the applicable service terms with support before sending restricted data. Revoking access does not recall results already returned to a client.
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: with a direct connection or an optional hosted gateway.