WordPress MCP Options: Compare Setup and Capabilities

Start with the job and the site

“WordPress MCP” describes a way to connect AI clients to WordPress operations. It does not identify one product or guarantee the same tools everywhere. Use these four routes to make a shortlist before comparing individual tool names.

Build your own integration

You have custom WordPress operations and a developer to implement and maintain them.

Evaluate the WordPress MCP Adapter

Use a packaged tool catalog

You want existing WordPress and supported integration tools on a site you administer.

Evaluate EMCP Tools

Use Elementor's own workflow

Your project fits its currently supported editor structures and installation requirements.

Evaluate official Elementor MCP

Connect through a hosted account

Your sites qualify for WordPress.com MCP, including eligible Jetpack-connected sites.

Evaluate WordPress.com MCP

Published by EMCP's team. This is a dated, documentation-based comparison of selected options, not an exhaustive directory or independent performance ranking. We did not run the same task through every product.

Compare the setup you would maintain

Documented product roles, reviewed 26 September 2026
Option	Connection and responsibility	What to verify first
WordPress MCP Adapter	A bridge on WordPress exposing registered abilities. Integration authors supply operation logic and permissions.	Chosen release, installation model and the abilities your site actually registers.
EMCP Tools	A site plugin supplying tools and settings. Connect directly or use the optional EMCP Cloud gateway.	WordPress/PHP requirements, integration dependencies, tier and enabled operations.
Official Elementor MCP	Elementor's connection for external clients to use its WordPress AI Abilities.	Editor structure, installed versions and any Angie-dependent capabilities.
WordPress.com MCP	A hosted endpoint serving eligible sites through a WordPress.com account.	Plan eligibility, account access, site controls and available tools.

Installing multiple options does not prove they work together. Test the selected route in a suitable staging environment. A tool-count comparison alone also misses permissions, schema quality, model handling and the exact operations needed for your project.

WordPress MCP Adapter: supply your own operations

The Adapter connects WordPress abilities to MCP. It fits custom integration work when you can implement operation logic, input schemas, permission checks and tests. It is not itself a promise of a complete Elementor or commerce workflow.

Current upstream development documentation describes plugin installation and a default endpoint at /wp-json/mcp/mcp-adapter-default-server. It discourages Composer bundling and notes that WordPress.org plugin-dependency distribution is not yet supported. Match the instructions to the release you select; development documentation can lead a released package.

Read the official repository and installation guidance. The narrower Adapter vs EMCP explanation covers how a product can build on this bridge. EMCP's bundled dependency and upstream's newer installation guidance should not be treated as interchangeable instructions.

EMCP Tools: start with implemented workflows

EMCP provides WordPress operations and integrations, plus Connection and Tools settings on your site. Its shared catalog currently lists up to 225 Free and 552 total tools. The actual surface depends on dependencies, tier and settings. Elementor is required for Elementor operations, not for general WordPress work.

This route fits a site operator who wants an existing tool for the task. It still requires matching that tool's input, permissions and supported editor structure to the site. Use installation requirements, the integration catalog and tier matrix to check the specific workflow.

A direct connection does not require EMCP Cloud. The optional gateway changes routing and data recipients; see direct versus hosted data flow. AI client/model usage is separate from plugin and Cloud licensing.

Official Elementor MCP: check the editor fit

Elementor's MCP connects external AI clients to its editor abilities. Its current product page describes Atomic workflows and lists Widget (V3) support as forthcoming. Some broader WordPress capability groups require Angie.

The setup guide lists WordPress 6.8+ and Elementor Core and Pro 4.3.0+, while the product FAQ describes basic features as free. Confirm that discrepancy against your installed versions before assuming a free-only setup. We have not validated those installations side by side.

Use Elementor's product page and connection guide as primary sources. Our detailed Elementor comparison covers the editor and dependency differences; its AI/Angie section distinguishes built-in assistants from an external MCP client.

WordPress.com MCP: a hosted account connection

WordPress.com's documentation describes a shared hosted MCP endpoint with OAuth 2.1. A connection can reach eligible sites on the account. It also serves eligible self-hosted sites connected through Jetpack; those sites use the same endpoint, not a separate Jetpack server.

Current requirements list WordPress.com paid plans, a first-30-days access window for newly created free sites, or a qualifying Jetpack AI/Complete plan for connected self-hosted sites. MCP must be enabled for the account. Recheck eligibility before choosing it for a client.

Read the official overview and requirements and its linked tool reference. This route may fit account-wide content work, but eligibility alone does not establish support for your particular Elementor layout or custom-plugin operation. Verify the operation in the catalog and with a small test.

Evaluate the same small task

Choose one representative task before installing anything. For example: read the title, status and content of a named staging page; propose one text change; save it to an approved draft; read it back; verify the preview. Use the same acceptance criteria for every option you shortlist.

Record the environment: site URL, editor structure, versions, plan and connected identity.
Verify discovery: inspect the operation and input schema; distinguish missing tools from denied execution.
Start with a read: confirm the correct site and page. A connection badge is not saved-state evidence.
Test one permitted write: use a draft and a recovery plan. Check the saved status and output.
Compare the whole workflow: setup effort, review steps, failure handling, maintenance ownership, service costs and data recipients.

Record failures and unknowns alongside successes. Do not infer a speed, reliability or security ranking from one demo. For a concrete review pattern, use the agency delivery playbook.

Method and review notes

The selections above cover four distinct setup models, not every WordPress MCP project. Vendor documentation supports product scope and requirements; EMCP descriptions also follow the local implementation and published tool references. The Northline example provides EMCP controller evidence, not a comparative MCP-client benchmark.

Sources checked on 26 September 2026: WordPress MCP Adapter and its development installation guide; Elementor MCP and connection requirements; WordPress.com MCP documentation. Product requirements, access plans and catalogs can change. Use the linked setup sources at installation time.

Choose the smallest setup that supports the required operation, permissions and review process. If two options remain plausible, run the bounded evaluation above and keep the result with the project handoff.