Scale and track record
AI Engine has more than 100,000 active installs and a 4.9 rating on WordPress.org. That is a large, proven user base and a plugin many teams already trust.
Governance vs an all-in-one AI suite
Agent Abilities vs AI Engine
AI Engine is a large, popular AI suite for WordPress: chatbots, content generation, AI forms, image generation, and, as one feature among many, an MCP server. Agent Abilities does one thing, a governed MCP server, and nothing else. So this is breadth against focus, and the honest question is how much surface you want an agent to have.
Summary and contents
The short version
Both are real WordPress MCP plugins. AI Engine and Agent Abilities weigh differently, so this is a priorities decision, not a better-or-worse one.
- In common
- Both turn WordPress into an MCP server for AI clients, and both refuse arbitrary code execution in the shipped plugin.
- AI Engine wins on
- Scale, a full AI suite far beyond MCP, and fast, active development.
- Agent Abilities wins on
- Off by default, a WordPress account instead of a secret token, a bounded surface, and every ability free.
- AI Engine today
- 100,000+ active installs (WordPress.org)
What each one optimizes for
The two plugins pull in different directions on purpose. Here is the honest shape of each.
AI Engine sells breadth and momentum. It is a whole AI platform with more than 100,000 installs and a 4.9 rating, and MCP is one part of it. Turn the MCP module on and it exposes a wide core tool set to admin-level access, then its Pro tier adds plugin, theme, database, and WooCommerce management on top. It deliberately refuses arbitrary PHP execution in the official plugin, which is a fair safety line to draw. If you want AI features across your whole site and MCP as a bonus, that reach is the draw.
Agent Abilities sells governance. Nothing is exposed until you switch it on, the agent connects as a real WordPress user with only that user's permissions, every call is re-checked and written to an audit log in your own database, and the plugin makes no outbound calls of its own. If a tight, auditable boundary around the agent is what you want, that is the trade this plugin makes.
Neither approach is wrong. The rest of this page lays out the specifics, including where AI Engine genuinely reaches further than we do.
Side by side
Their claims are quoted from the WordPress.org listing and the Meow Apps documentation, verified July 2026, and stated as their claims. Ours trace to the plugin readme.
| Dimension | AI Engine | Agent Abilities |
|---|---|---|
| Price | Free core on WordPress.org. The full MCP tool set needs AI Engine Pro, from 99 USD per year | Free on WordPress.org. No paid tier, no API key to buy, no usage limits. |
| What it is | An all-in-one AI suite (chatbots, content generation, forms, image and video), with an MCP server as one feature | One thing: a governed MCP server for AI agents, nothing else |
| Default posture | MCP is a module you switch on; once on, a wide core tool set is exposed by default | Off by default. You enable one ability at a time; an update never widens access on its own. |
| Agent connects as | OAuth sign-in, or a secret bearer token in the endpoint URL. Admin-only access by default | A real WordPress user, never a key this plugin mints with a scope of its own. With an Application Password you point it at the dedicated low-privilege user the plugin creates for you. Over OAuth it takes the capabilities of whichever account approves in the browser, so approve as the account you want it limited to. |
| Capability check | Admin-level by default; narrowing which tools a role can call needs a code-level filter (mwai_allow_mcp) | Two layers: a connection only sees the tools its user can run, and WordPress itself re-checks that user’s capability before every call. |
| MCP surface | 36 core tools (posts, comments, users, media, taxonomies, settings). Pro adds plugin install and file editing, theme file editing, database and SQL query tools, and WooCommerce management | Core reads and guarded writes plus capability-gated integrations. No plugin or theme file editing, no SQL query tool |
| Arbitrary code execution | Refused in the official plugin; an optional GitHub-only companion (YOLO) adds it for staging | None. No code execution, no remote URL fetch, ever |
| Audit log | MCP calls are logged; an mwai_mcp_mutate hook fires after content-changing tools | Every call, denials included, with the principal and argument keys but never the values, in your own database. |
| Outbound calls | As an AI suite it calls OpenAI, Anthropic, Google, and others with your keys; the MCP server itself is inbound | Zero outbound calls of any kind. No connectors, no telemetry. Nothing leaves your site on the plugin’s initiative. |
| Built on | Its own MCP implementation, not the official MCP Adapter, which it argues is a thin REST wrapper | A full governed MCP server with its own catalog and bridge, built on the WordPress 6.9 Abilities API and the official MCP Adapter. |
| AI clients | Documents connecting from clients like ChatGPT, Claude, and Claude Code | 9 today, including ChatGPT, Claude.ai, and Manus through custom connectors. The Gemini app is not supported yet, stated plainly. |
| Business model | Freemium: free core plus a paid Pro subscription and a Neko Pass bundle across Meow Apps plugins | Open source. No affiliate links, no agency upsell, no partner directory shown to your users. |
| Vendor in the chain | The MCP server itself is inbound only, but the surrounding suite is a subscription and the wider MCP tool set stops working without it | Nothing between the agent and WordPress belongs to a vendor. No token of ours carrying its own scope, no service of ours in the path, and no licence that can lapse and stop your automation. |
Where AI Engine leads
Said plainly, because pretending otherwise would not help you decide.
A whole AI suite, not just MCP
Chatbots, content generation, AI forms, image and video generation, embeddings, function calling. MCP is one feature among many. If you want AI across your site and not only an MCP endpoint, AI Engine does far more than we do.
Active development and a real safety line
It ships updates often, and it openly refuses arbitrary PHP execution in the official plugin, keeping that in a separate staging-only companion. Both the pace and that stance are genuine strengths.
The trade-offs in AI Engine
Real, evidenced trade-offs a security-minded owner would weigh. Not a knock, just the other side of their design.
Trade-off
MCP is a secondary feature
The product is a broad AI suite, so its MCP server is one module inside it rather than the whole point. The governance around that server is lighter than a plugin built only to govern MCP.
Trade-off
A broad surface, admin by default
Turn MCP on and a wide core tool set is exposed to admin-level access. Narrowing which tools a role can call is done with a code-level filter rather than per-ability admin toggles. Our default is the opposite: everything off, enabled one ability at a time.
Trade-off
The powerful MCP tools are paid
Plugin install and file editing, theme file editing, database and SQL query tools, and WooCommerce management sit behind AI Engine Pro, from 99 USD per year. The free MCP tier is real, but the full surface is not free, and file editing plus SQL access is a lot of blast radius.
Trade-off
Identity is a token, not a bound user
An agent connects with a secret bearer token or admin OAuth, not as a dedicated least-privilege user whose capability is re-checked before every call. That means more reach and less containment by default.
Where Agent Abilities leads
The governance thesis, which is the reason to pick this plugin over a broader one.
Off by default
Every ability starts disabled. You open access one toggle at a time, and an update never widens it on its own.
Least-privilege identity
The agent connects as a real WordPress user through OAuth or an Application Password, never an admin-equivalent key. It takes that account’s capabilities, so you decide its reach by choosing which account approves the connection.
Two-layer capability gating
A connection only sees the tools its user can run, and the capability is re-checked before every call.
Zero outbound, single-sourced facts
No connectors, no telemetry, and every number on this site comes from one source so it never contradicts itself.
Where Agent Abilities falls short
The honest other side. If one of these matters most to you, AI Engine may be the better fit.
Where we fall short
MCP only, no AI suite
We do not ship a chatbot, content generation, AI forms, or image generation. If you want those, AI Engine is a platform and we are a single governed server.
Where we fall short
Far fewer installs
AI Engine has more than 100,000 active installs. We are newer and smaller. If install base is your main trust signal, that gap is real.
Where we fall short
A narrower plugin
One governed MCP server means fewer features and fewer edge-case tools than a full AI suite. That is deliberate, but it is less.
Which should you choose
A short, honest rule of thumb.
Reach for AI Engine if what it leads on maps to your priorities: scale, a full AI suite far beyond MCP, and fast, active development.
Reach for Agent Abilities if you want an agent that starts with zero access, connects as a real WordPress account you choose rather than an admin key, is audited on every call including refusals, and makes no outbound requests. Governance and a tight boundary are the point.
Both are free, so the lowest-risk move is to install the one whose default matches how you want to start. See what a governed WordPress MCP server is, or read the governance model.
Comparing others too? See all MCP plugin comparisons.
Frequently asked questions
Direct answers about how the two compare.
Is Agent Abilities for MCP a free alternative to AI Engine?
For the MCP part, yes. AI Engine’s core MCP tools are free, but its plugin, theme, database, and WooCommerce MCP tools need AI Engine Pro. Agent Abilities is fully free with no paid tier. The trade is breadth against governance.
Does AI Engine run arbitrary code on my WordPress site?
No, not in the official plugin. Its own docs say the MCP tools do not run arbitrary code, and arbitrary PHP execution lives in a separate GitHub-only companion (YOLO) meant for staging. Agent Abilities also runs no code, and adds a least-privilege identity and a capability re-check on every call.
What is the main difference?
Scope and posture. AI Engine is an all-in-one AI suite where MCP is one feature, exposed broadly to admin-level access once you enable it. Agent Abilities is an MCP-only server, off by default, bound to a least-privilege user, and audited on every call.
Which should I choose?
Choose AI Engine if you want a full AI suite (chatbots, content generation, forms) with MCP as one piece, and a large, proven user base. Choose Agent Abilities if you want a focused, governed MCP server that starts off, uses least-privilege identity, keeps a bounded surface, and stays free.
Comparison based on each product's public documentation. AI Engine claims were verified against the WordPress.org listing and the Meow Apps documentation in July 2026 and are stated as their claims; their product may have changed since. Agent Abilities for MCP facts come from its own readme. Agent Abilities for MCP is not affiliated with, or endorsed by, AI Engine.
Start with everything off.
Install Agent Abilities for MCP, keep every ability disabled, and turn on one at a time. Requires WordPress 6.9+ and PHP 7.4+. Free on WordPress.org.
Off by default, least privilege, and nothing leaves your site without you.