Easy MCP AI Review: A WordPress Bridge with Useful Permission Limits

Easy MCP AI suits someone who wants an outside assistant to work with WordPress. The free plugin saved and revised real drafts in our test. Publishing control needs care because its draft setting does not prevent update tools from publishing.

A bridge for an assistant you already use

Easy MCP AI makes WordPress an MCP server. An assistant that supports the connection can request operations such as reading a post or updating its content. The plugin is the connection and tool layer; it does not generate the writing itself.

We tested that layer with a protocol client and prepared sample copy. A create request produced a real WordPress draft, visible in the Posts list and native preview. An update request changed the title and paragraph while leaving that post as a draft. That is useful evidence for a workflow where an assistant prepares content and a person reviews it in WordPress.

It does not establish how well ChatGPT, Claude or another assistant would write the article, choose tools or follow editorial instructions. We did not connect an external assistant, complete an OAuth login or test its response quality. The plugin presents connection options for multiple clients, but those options are not the same as verified connections.

Permissions are the important choice

Each connection operates as a WordPress user with the tools it is allowed to call. Our sample used an Author account with selected post tools. A request to change site settings was refused, and the site title remained unchanged. The Activity screen recorded that refusal alongside successful post changes.

The client also received the plugin’s helper tools, so selecting four post tools did not produce a four-tool-only connection.

Choose the user and tool scope around the work the assistant should perform. An Author account can publish its own posts when the permitted tool supports that operation. Giving a connection an update tool deserves the same care as giving it a create tool.

Force draft on create has a specific boundary

Force draft on create was off by default. After we enabled and saved it, a create request asking for a published post produced a draft instead. That provides a useful review step for new content created through the plugin’s own create tools.

An update request then published that same sample while the setting remained enabled. This matches the explanation in the native settings screen: update tools and plugin abilities can still publish. The switch is a rule for creating new content, rather than a universal publishing lock.

If human approval before publication is essential, enforce it through the WordPress user’s capabilities and the tools available to the connection. Do not assume the draft switch compensates for a user and update tool that can publish.

The change trail is useful for editors

Activity shows which tool ran, the WordPress user and client involved, and whether the request succeeded or was refused. Change history adds before and after snapshots of writes made through the MCP server. The title comparison showed our revision clearly, but the content row displayed a blank after value even though the native preview showed the saved revised paragraph. Check the actual post as well as the comparison.

That helps answer what changed and which connection did it. It does not cover every ordinary edit someone makes directly in WordPress, and it is not a substitute for backups or a complete security audit.

The dashboard also has a pause control. After its native confirmation, the next tool call was refused with a site-paused error. Resuming access allowed the client to read the draft again. Existing clients stay signed in, so this is a temporary stop for tool access rather than credential revocation.

Free software, separate service costs

Easy MCP AI is free on WordPress.org. An outside assistant still uses its own account and plan, and connected analytics or SEO services may have their own API costs. Those services were not connected in our test.

The tool screen includes content operations, plugin integrations and external data, but availability depends on configuration and the software or services connected to the site. A large advertised tool count does not show that every tool is enabled, appropriate for a particular user or tested in this review.

Start with one editorial task, a limited WordPress user and a small set of tools. Inspect the saved post before extending that access to a wider workflow.