Why Easy MCP AI fits better
I tested Easy MCP AI next to the official WordPress MCP Adapter for managing posts and pages from Claude Code and Codex. For my use case, Easy MCP AI is clearly the better fit:
OAuth instead of application passwords. The Adapter relies on application passwords, which are site-wide credentials stored in plain text in the client config. Here I approve a connection in the browser and pick its scopes, and I can narrow or revoke it at any time.
Posts and pages work out of the box. With the Adapter I would have had to write my own abilities just to create or update content. Easy MCP AI has ready-made tools for posts, pages, media and taxonomies, and changes can be rolled back through revisions and the change history.
Fine-grained control. I can disable risky tools site-wide (users, plugins, WP-CLI, settings) and keep each connection limited to content.
On “MCP is insecure”
A lot of people worry about giving AI access to their site, and with a careless setup that worry is justified. But Easy MCP AI makes a least-privilege setup possible. I use three layers: risky tools disabled site-wide, narrow scopes per connection, and a dedicated Editor user, so the AI can never do more than an Editor.
I tested it: creating and trashing a draft worked, while changing settings, listing plugins, creating users and editing widgets were all blocked. Configured like this, the risk is limited to content, and even content changes can be rolled back.
One wish
Approving a connection currently requires admin access, so connecting a non-admin user takes an extra step. I’ve posted a feature request about that. Otherwise this is an excellent, well-designed plugin.
