What is WordPress MCP?

How WordPress MCP works.

A chatbot can explain how to update a page. A connected AI assistant can also request a tool that reads or edits it. MCP defines how the client discovers those tools, checks their input shapes, and receives results. It does not automatically grant access to your site.

WordPress’s Abilities API, introduced in WordPress 6.9, gives developers a standard way to register functionality. The separate WordPress MCP Adapter makes registered abilities available over MCP. EMCP builds on these foundations and supplies tools for supported WordPress tasks.

For endpoint details, transports and the gateway route, use the WordPress MCP server page. For the relationship between the building blocks, read Adapter vs EMCP.

What can your AI do in WordPress?

The protocol does not determine your tool catalog. Your plugin, active integrations, plan, tool switches and WordPress user determine what is available. With the appropriate EMCP tools, you can work on tasks such as:

“Find draft pages that mention our old phone number. Show the matching text and page links. Do not change anything.”

Example first prompt, not a recorded result. Start with a narrow question whose answer you can verify.

Do you need a plugin?

You need an MCP server and the operations your task requires. A self-hosted WordPress plugin can provide them; a hosted service may use a different connection model. These options can share foundations without having the same tool coverage.

WordPress MCP Adapter

A bridge for abilities supplied by core, plugins or themes. Suitable when you need to expose specific registered functionality or build an integration. Understand the Adapter.

Builder-focused MCP

Useful when your main task is in a particular editor. Elementor’s MCP supports native Atomic layouts; its current documentation includes saving drafts and publishing. Check its version and feature requirements. Read Elementor’s documentation.

A WordPress toolkit such as EMCP

Provides a server plus ready-to-use tools across supported content, builder, theme and plugin workflows. General WordPress tools do not require Elementor. See EMCP installation and requirements.

Compare the operation you need, supported versions, permission checks, data recipients and total service costs. Our comparison pages and WordPress MCP evaluation guide cover those tradeoffs in more detail.

Connect AI to WordPress in five steps.

This path uses EMCP. Other servers have their own installation and authentication requirements. Use a staging site for your first write.

1. Install the free EMCP plugin.

   You need WordPress 6.9+ and PHP 8.1+. Elementor is optional; each integration has its own requirements. Activate EMCP and open EMCP Tools → Connection. Follow the installation guide if you are starting from a downloaded ZIP.

2. Choose the user and authentication method.

   For a dedicated user with limited task permissions, use an Application Password belonging to that user with a client that supports it. EMCP OAuth approval requires administrator-level access by default, so its token normally acts as that administrator. Do not assume OAuth automatically creates a restricted user. Compare both methods in the security guide.

3. Select the client and connection route.

   Use the Connection wizard for your client’s server URL and configuration. A direct connection does not require EMCP Cloud. A remote connection should use HTTPS. For a local development site, check the WP-CLI stdio bridge. For several connected sites, the optional hosted gateway provides a separate route.

4. Add the connection in your AI client.

   Follow the guide for Claude, the ChatGPT desktop app, Cursor, or another documented client. Menus, supported transports and account requirements differ. Check your AI client’s own plan and workspace policies.

5. Read first, then try a small draft.

   Ask for the site name, connected identity and a few recent pages without changing anything. Check the returned site and records. Then, on staging, enable the specific write tool you need and request one small draft edit. Read it back and inspect its native editor and frontend preview before publishing.

Permissions, data and review.

EMCP checks calls against the connected user’s capabilities and enabled tools. An Editor account and an administrator account do not have the same access. Check each operation’s actual requirements; a role name alone does not establish what the tool will permit.

• Begin with reads and enable only the write tools the task needs.
• Use staging and drafts where supported, and keep a current backup.
• Check available History and recovery before a write. Not every operation can be undone.
• Review the saved result. A successful tool response is not a visual or publishing check.
• Revoke credentials or connected-app access when the connection is no longer needed.

Find your connection guide.

Choose the application you will actually use. EMCP Free supports direct connections with its free tools; Pro adds tools and integrations. This is separate from your AI application’s subscription or administrator policies.

For supported builders, block packs, themes and plugins, use the integration catalog. Check the individual integration page for its scope before making promises about a page build or site-wide edit.

Before you connect.