Comparison
WPVibe and WPAgently compared
WPVibe routes every tool call through a server operated by Awesome Motive. WPAgently connects your agent directly to your site.
Both products let you run WordPress with the AI subscription you already have. The difference is the route your instructions take, and the permissions the agent gets on your site.
As of 24 August 2026Checked against wpvibe.ai, its security page, the GitHub repository, the pricing page and WordPress.org
When WPAgently is the stronger fit
WPAgently
When the workflow on your live site should have narrow, explicit boundaries
- Your agent connects directly to the MCP endpoint on your customer's site. On that route, WPAgently does not process calls through a vendor relay.
- WPAgently Free provides 34 core abilities with no call limit. Companion 0.4.121 expands the documented surface to 414 abilities, with 317 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, while server-side schema and parameter boundaries define what each supported write path can accept.
- Article and landing-page pipelines are idempotent and document conflict hashes, read-back, and path-specific render checks or recovery. This is not a promise for every possible write.
What each product is good at
WPVibe comes from a large company and covers more ground. WPAgently is narrower and documents path-specific verification contracts. Which one fits you depends on how much control over the route your data takes you need.
WPVibe
Broad coverage and a genuinely free entry point
- WPVibe is built by Awesome Motive, the company behind WPForms, SeedProd, MonsterInsights and OptinMonster. That is reach and development capacity a single-handed product does not have.
- On WordPress.org the plugin sits at more than 10,000 active installations and a 4.9 out of 5 rating from 25 reviews on 24 August 2026. That remains a small sample.
- The current version on that date is 1.15.4. The free tier needs no card, covers unlimited sites, includes the complete tool and skill surface, and allows 100 tool calls per rolling 24-hour window. WPAgently Free includes 34 tightly bounded core abilities without a daily call limit.
- WPVibe passes the WordPress REST API through as generic tools and emulates more than 40 WP-CLI commands against an allowlist. That covers more edge cases than a fixed set of purpose-built actions, and it works on shared hosting without SSH.
- The current documentation also names modifying database operations behind dry runs and approval. It additionally provides an approval log, trash, and theme draft, preview and backup.
WPAgently
The direct route and narrowly bounded standard paths
- There is no WPAgently server between your agent and your site. The connection goes straight to the MCP endpoint of your own installation.
- 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.
- Your credentials stay where you created them, rather than with a provider that keeps them for you.
- The respective contracts for supported article and landing-page pipelines describe read-back, sometimes render checks, conflict hashes and idempotency. That does not apply to every write as a blanket promise.
- The price depends only on your number of sites. Nothing counts requests, so the invoice does not change shape at the end of a busy month.
The difference in the working and safety model
The WPVibe statements come from the wpvibe.ai security page and the plugin's public GitHub repository; the WPAgently statements come from the product documentation in this repository.
The route your instructions take
WPVibe
Every tool call passes through the hosted MCP server at mcp.wpvibe.ai. The repository describes it as a Cloudflare Worker relay and states that it is closed source.
WPAgently
The agent talks straight to your site's MCP endpoint at /wp-json/wp-agent/mcp. There is no WPAgently server on that route.
The permissions the agent gets
WPVibe
WPVibe works with the rights of the WordPress account that connects it, which the vendor describes as anything from contributor to administrator depending on the account. There is no product-level ceiling.
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.
Where credentials and logs live
WPVibe
Credentials are stored on Awesome Motive's infrastructure, encrypted with AES-256-GCM and a per-site salt, because they pass through the relay. Usage and approval logs live there too.
WPAgently
Credentials live in your WordPress installation and in the CLI's local configuration file. The tamper-evident log of the developer and staging mode lives on your own site.
What happens before a critical action
WPVibe
Posts default to draft, deletions go to the trash, and bulk deletion, search and replace and role changes require a dry run with explicit approval.
WPAgently
New content starts as a draft. The current set-post-status path returns HTTP 409 with manual_only, so publishing is a deliberate manual step in WordPress. In the integrated chat every write action gets its own single-use approval.
How database changes are bounded
WPVibe
The current documentation names modifying database operations behind a dry run and approval. WPVibe's current product materials define the exact scope of those operations.
WPAgently
Standard paths write through WordPress and provider APIs rather than raw database access. A direct database write path exists only in the separate developer and staging mode, which is its own plugin and stays off by default.
Pricing compared
The two price lists measure different things. WPVibe scales by the number of tool calls per day and allows unlimited sites on every tier. WPAgently scales by the number of sites and counts no calls at all.
WPVibe
| Plan | Calls per rolling 24 hours | Price per year |
|---|---|---|
| Free | 100 | $0 |
| Pro | 500 | $99 |
| Power | 2,000 | $299 |
| Agency | 5,000 | $599 |
| Scale | 10,000 | $899 |
WPAgently
| Plan | Sites | Price per year |
|---|---|---|
| Free | unlimited | $0 |
| Solo | 1 | $49 |
| Pro | 5 | $99 |
| Agency | 25 | $149 |
The plans measure different things. If you look after many small sites, scaling by calls can fit well. If you work one site intensively, weigh the call allowance against pricing by number of sites.
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 permanent free tier. WPVibe limits Free to 100 calls per day. WPAgently limits the scope to 34 core abilities but does not count their calls.
- Awesome Motive has more development capacity and a considerably larger distribution channel through its existing products.
- A passed-through REST API covers more edge cases than a fixed set of purpose-built actions. If you do a lot of unusual work, you hit a wall sooner with WPAgently.
- WPVibe ships its own dry runs, approval log, trash, and theme draft, preview and backup.
- WPVibe's generic tool surface suits more unusual interventions than WPAgently's standardised content contracts.
Sources and date
Every statement about WPVibe on this page comes from the vendor's own public sources, accessed on 24 August 2026. The plugin is updated very frequently, so we re-check this page regularly.
- https://wpvibe.ai/
- https://wpvibe.ai/security
- https://mcp.wpvibe.ai/pricing
- https://github.com/awesomemotive/wpvibe-ai-mcp
- https://wordpress.org/plugins/vibe-ai/
If the direct route is what counts for you
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.