A brief becomes a real page.Expose your own operations.
You have application logic or a plugin API that needs an MCP interface, and a developer to own the implementation.
Explore the developer route ↗Separate the connection from the operation.
A WordPress ability describes an operation an application can invoke. The integration defines its inputs, behavior and permissions. The Adapter makes eligible abilities available through MCP; your client requests the work and receives the result.
For example, “inspect this Elementor page” needs implementation that knows how to read Elementor data. EMCP supplies that implementation. The Adapter handles the connection between the MCP request and the exposed operation. This distinction explains why two sites using the same bridge can offer different tools.
The upstream architecture documentation describes the protocol and WordPress integration layers. The ability-authoring guide covers the operations you expose. Neither the model nor the connection protocol invents missing plugin functionality.
Permissions belong in the implementation too.
The Adapter supports both transport access checks and ability-level checks. EMCP's tool implementations check the connected user's capabilities. For either route, validate access to the specific operation and object; an instruction in a prompt is not a permission boundary. See the Adapter permission guide and our EMCP security walkthrough.
Compare responsibilities, not tool totals.
A protocol bridge and a catalog of implemented operations answer different questions. Use this table to identify which work your setup still needs.
| Responsibility | MCP Adapter | EMCP Tools |
|---|---|---|
| Main responsibility | Connect WordPress abilities to MCP clients. | Provide implemented WordPress workflows and a dashboard around its MCP server. |
| Task implementation | Comes from the abilities or integrations you expose. | A catalog of tools for supported WordPress features, plugins and builders. |
| Custom development | You own your operation logic, schemas, permission callbacks and tests. | Start with existing tools; assess a custom integration when the required operation is missing. |
| Access controls | Transport permissions and per-ability permission checks. | Connected-user checks, site-wide tool selection and gates on relevant operations. |
| Setup surface | Developer documentation and the installation model for your chosen version. | Plugin installation, Connection settings and client configuration guides. |
| Maintenance | Follow upstream changes and maintain the integrations you write. | Update EMCP and its supported dependencies; review changes to your enabled tools. |
| Where to get help | Upstream documentation and issue tracker for Adapter behavior. | EMCP documentation and support for its tools and product workflows. |
On small screens, scroll the table horizontally. Adapter behavior is described by the official documentation linked below; EMCP behavior is checked against its source and product guides.
What EMCP adds to the foundation.
EMCP packages task implementations with a WordPress admin interface. Its Connection screen provides client setup information; the Tools screen lets you review what is exposed on that site. Its catalog includes page-building, content and site-management workflows, with availability determined by your installed integrations and enabled modules.
Elementor workflows
Discover widget types, inspect saved layouts, create drafts and target existing elements for changes.
Build your first page ↗WordPress operations
Work with supported content, media and plugin integrations using tools designed for those systems.
Explore integrations ↗Connection and tool controls
Configure a client, choose relevant tools, inspect requests and use Compact mode where helpful.
Read the documentation ↗The current shared catalog lists up to 225 Free tools and 552 across Free and Pro. These are catalog totals, not a promise that every site exposes every tool. Compare Free and Pro for tier boundaries. Optional Cloud services are a separate choice; a direct MCP connection does not require a Cloud subscription.
Follow the guide for the package you use.
For EMCP: the reviewed dependency lock pins wordpress/mcp-adapter to v0.6.1, and EMCP bundles that dependency. Follow the EMCP installation guide, then copy your connection details from the dashboard. Its dedicated HTTP endpoint is /wp-json/mcp/emcp-tools-server.
For direct Adapter development: upstream trunk documentation now describes a standalone plugin and discourages bundling another Composer copy. That is development-branch guidance, not a statement that EMCP has already migrated. Read the documentation and migration notes matching the version you intend to install. Check upstream installation guidance ↗
Avoid mixing installation recipes.
Do not add a second Adapter installation merely because a different tutorial uses one. Check the dependency model of your installed product first. If you maintain a custom integration, test version compatibility on staging before changing that foundation.
Use the endpoint supplied by the server you actually configured. A tutorial for the Adapter's default server and EMCP's Connection screen can show different URLs because they identify different servers.
When direct Adapter development makes sense.
Suppose an internal plugin stores project handoff records, and your agent needs to read a limited summary. That business operation may not exist in EMCP's catalog. A custom integration can expose exactly that operation, backed by your plugin's API.
- Define the input, output and allowed behavior for the task.
- Implement the ability and check access to the relevant records.
- Expose it through a server using the Adapter API for your version.
- Test allowed and denied users, invalid inputs and error results.
- Maintain the integration as WordPress, your plugin and the Adapter evolve.
Start with the official ability-authoring guide. EMCP may still be useful for other tasks on the site; owning a custom operation does not require rebuilding every general WordPress workflow.
Find the gap before adding another server.
List the available tools and inspect the schema of the closest match. A missing tool may reflect an inactive plugin, a disabled module or a tier requirement. If the operation truly is absent, write down the data it needs, the action it performs and the permissions it requires.
Registering a WordPress ability does not by itself guarantee that it appears in EMCP's dedicated tool catalog. Check how the target server selects its abilities. A custom server needs its own access review and client configuration. Keep each connection clearly named so an agent can identify the intended site and tool set.
If your actual question is about Elementor's own integration, see EMCP vs Elementor's official MCP. That comparison concerns a different product relationship.
Before you choose your setup.
Does EMCP replace the WordPress MCP Adapter?
No. EMCP uses the Adapter to expose its WordPress abilities through an MCP server. EMCP supplies the task implementations and product interface around that foundation.
Do I need to install the Adapter separately for EMCP?
The EMCP package reviewed here bundles the Adapter. Follow the installation guide for your EMCP version rather than adding another copy automatically. Upstream development documentation describes a different, standalone-plugin installation approach.
Can the Adapter support Elementor tools?
Yes, when an integration supplies the corresponding operations. The bridge is not limited to a particular editor. EMCP provides implemented Elementor workflows, including widget discovery, page building and targeted edits.
Does the Adapter have permission checks?
Yes. Its documentation describes server transport permissions and individual ability permission callbacks. A custom integration must define appropriate checks for its operations. EMCP also checks the connected user and provides product-level tool controls.
Is EMCP the same as Elementor’s official MCP?
No. EMCP Tools is an independent product. WordPress’s MCP Adapter, EMCP Tools and Elementor’s official MCP integration are distinct projects. Use the separate Elementor comparison for that decision.
Start with an operation you can verify.
For an existing EMCP workflow, connect your client and inspect the site first. For a custom integration, define one narrow ability and test its permissions before expanding it.
Sources and review scope
Reviewed 23 September 2026. This explanation is published by EMCP Tools, the product discussed here. It is based on official Adapter documentation and EMCP source review, not a comparative performance benchmark. Upstream links target a moving development branch; follow versioned documentation for implementation.
- WordPress MCP Adapter overview and architecture
- Adapter installation and dependency guidance
- Creating abilities and transport permissions
- EMCP source repository: dependency lock and dedicated server registration