Comparison
AI Engine and WPAgently compared
AI Engine is a broad AI framework with selectable MCP features. WPAgently connects your own agent to 414 Companion abilities and separate Power paths.
The two products solve problems of very different size. AI Engine brings chatbots, content and image generation, AI forms and a knowledge base. This page focuses on the MCP route because it is the shared external agent connection. From WordPress 7.0 onward, WPAgently additionally offers an integrated chat with an AI provider configured under Settings > Connectors.
As of 24 August 2026Checked against meowapps.com, the AI Engine tutorial, the Pro product page and WordPress.org
When WPAgently is the stronger fit
WPAgently
When your own agent should work on live sites under explicit contracts
- Companion 0.4.121 exposes 414 documented abilities through a direct MCP endpoint on your site. 317 of them are in the recommended content profile.
- The article and landing pipelines use an Editor bot. Their client-side preflight aborts when the bot account has administrator rights. Individual MCP tools check the required WordPress capability server-side.
- Ability profiles start closed. Server-side schema and parameter boundaries describe the input allowed for each supported write path.
- Supported article and landing-page pipelines combine conflict hashes and idempotency with read-back, sometimes render checks, and documented recovery paths. This is not a blanket promise for every write.
- Raw access lives in the separate Power plugin, which stays off by default. Backup and restore are dedicated product paths.
What each product is good at
Of the products compared here, AI Engine is by far the oldest and most widely installed. WPAgently leaves out chatbots, embeddings and an AI service of its own to focus on bounded WordPress actions with documented verification contracts. These are two different offers, not two variants of the same one.
AI Engine
An established framework with a large user base
- On WordPress.org, AI Engine sits at more than 100,000 active installations and a 4.9 out of 5 rating from 860 reviews on 24 August 2026. That is a basis for trust a new product cannot show.
- Development continues actively. Version 3.7.2, current on that date, was released on 21 August 2026.
- One plugin covers chatbots, content and image generation, AI forms, embeddings and a playground. WPAgently does not attempt that range at all.
- AI Engine connects many providers and local-server options. WPAgently is built around Claude Code, Claude Desktop and Codex.
- The MCP server is already included in the free version. WPAgently Free includes 34 bounded WordPress abilities without a call limit.
WPAgently
One job, with documented boundaries
- The article and landing workflows apply server-side checks after a write. Markdown or section data is turned into valid Gutenberg blocks before saving.
- For the article and landing pipelines, the bot runs as an Editor. Their client-side preflight aborts when the bot account has administrator rights. Individual MCP tools check the required WordPress capability server-side.
- Standard content pipelines create drafts. The published status change remains a deliberate manual step in WordPress.
- Supported article and landing-page pipelines document conflict hashes, read-back, sometimes render checks and idempotency. Rollback or recovery apply only to the paths whose contracts document them.
- Raw access to PHP and the database lives in the separate Power plugin, which is off by default and additionally requires a constant in
wp-config.phpbefore arbitrary PHP can run.
The difference in the write path
What is compared here is only AI Engine's MCP server, not the plugin's other features. The statements come from Meow Apps' public materials; the WPAgently statements come from the product documentation in this repository.
What the product fundamentally is
AI Engine
An AI framework for WordPress with chatbots, content and image generation, forms and embeddings. The MCP server is one feature inside it.
WPAgently
A WordPress toolkit for the agent you already run, with server-bounded actions and path-specific verification. It brings no chatbots, embeddings or AI service of its own.
How the agent authenticates
AI Engine
Through OAuth or a bearer token. The available MCP features can be selected.
WPAgently
Through an OAuth grant you approve in the browser, or an application password. Both belong to an account with Editor rights.
What permissions the agent gets
AI Engine
The public documentation does not describe a combined role, profile and server-side parameter boundary like the WPAgently contract documented here. That is not a claim about the source code.
WPAgently
For the article and landing pipelines, the bot runs as an Editor. Their client-side preflight aborts when the bot account has administrator rights. Individual MCP tools check the required WordPress capability server-side.
Draft and publication
AI Engine
The public documentation describes a selectable feature scope for MCP execution. It does not describe a corresponding combined draft, approval and Editor-bot contract there. That is not a claim about what the product code may contain.
WPAgently
Standard content pipelines create drafts. The current set-post-status path returns HTTP 409 with manual_only, so publishing remains a deliberate manual step in WordPress.
Verification after the write
AI Engine
The public documentation does not describe combined read-back, render checks and recovery for MCP writes like the documented WPAgently paths. That is not a claim about what the product code may contain.
WPAgently
Supported paths read the result back and sometimes run a render check. Rollback or recovery apply only where the relevant contract documents them. This promise explicitly does not apply to arbitrary PHP code.
One thing matters for reading this table: what was checked is the public documentation, not the source code. If a mechanism is not described there, that means we cannot evidence it, not that it is missing. If you use AI Engine and want these questions answered precisely, ask Meow Apps directly.
Cost model
AI Engine Free already includes an MCP server. According to the vendor, Pro extends the MCP scope for WooCommerce, the database, themes and plugins, among other areas. The primary-source text available on 24 August 2026 does not state plan prices we can reproduce with confidence. That is why this page carries no table with older figures.
WPAgently Free costs $0, includes 34 core abilities and does not count calls. The three annual subscriptions start at $49 for one website and unlock Companion 0.4.121 and Power 0.6.38. You pay for your own AI access with the respective provider.
Where WPAgently does not keep up today
A comparison that points in one direction only is not a comparison. These are the places where WPAgently is the narrower product.
- Both offer a free entry point. AI Engine Free provides a broad AI framework with MCP, while WPAgently Free provides a narrower verified WordPress workflow.
- More than 100,000 installations and 860 reviews are a track record WPAgently does not have as a new product.
- Many provider and local-server options are broader than WPAgently's focus on Claude Code, Claude Desktop and Codex.
- Chatbots, image generation, AI forms and a knowledge base are things WPAgently does not offer at all.
- The sibling products SEO Engine and Social Engine extend the same MCP server with further tools. WPAgently has no comparable product family.
Sources and date
Every statement about AI Engine on this page comes from Meow Apps' public sources and from WordPress.org, accessed on 24 August 2026. When something changes there, we change this page.
- https://meowapps.com/ai-engine/
- https://meowapps.com/ai-engine/tutorial/
- https://meowapps.com/products/ai-engine-pro/
- https://wordpress.org/plugins/ai-engine/
If you need a bounded WordPress workflow
WPAgently Free costs $0, includes 34 core abilities, and does not count calls. The three annual subscriptions start at $49 for one website and unlock the full feature set.
Not sure whether your setup fits? Email hallo@wpagently.com. You get an answer from the developer, not a sales pitch.