| Price | Free tier at 0 USD, then Pro at 99 USD a year, Power at 299, Agency at 599, and Scale at 899 | Free on WordPress.org. No paid tier, no API key to buy, no usage limits. |
|---|
| Usage limits | Every tier is metered per account. Free is 100 tool calls a day with a bonus allowance for the first 7 days, then 500 on Pro, 2,000 on Power, 5,000 on Agency and 10,000 on Scale | None. No cap on calls, clients, or users, on any tier, because there is only one tier. |
|---|
| Where calls are processed | Through the WPVibe service. Their listing says the plugin “connects to the WPVibe service at wpvibe.ai to relay requests between your AI assistant and your WordPress site”, and that requests may also pass through relay servers WPVibe operates on DigitalOcean, which do not store them | On your own site. Your AI client connects straight to your WordPress endpoint and nothing of ours sits in between. |
|---|
| Where the credential lives | On their servers. Their listing states that on connection "a WordPress application password is created and encrypted with AES-256-GCM on WPVibe servers hosted on Cloudflare" | In your own database, and only ever a credential you created. Nothing is transmitted to us, because we run no service. |
|---|
| Vendor in the chain | Yes, by design. The relay is the product, and they document it plainly as a third-party service | 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. |
|---|
| Public MCP endpoint on your site | No. Your AI client connects to mcp.wpvibe.ai/mcp, which relays to your WordPress REST API. Their listing says “WPVibe does not open your site to the world” | Yes. Your site serves the MCP endpoint itself, protected by OAuth or an Application Password, an optional IP allowlist, and an optional rate limit. |
|---|
| Agent connects as | An Application Password their service creates and holds for you, encrypted at rest on their infrastructure | 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 | Yes. Their listing describes file operations running “through WordPress capability checks, a path sandbox scoped to the draft theme, and PHP syntax validation before save” | Two layers: a connection only sees the tools its user can run, and WordPress itself re-checks that user’s capability before every call. |
|---|
| Approval before destructive work | Yes, and it is a headline feature: destructive operations pause for an in-chat approval panel with a dry-run preview and Approve or Decline buttons | No in-chat approval step. Destructive abilities are instead off by default, capability-gated, with Trash post and Trash page sending content to the Trash (most Delete tools are permanent), and stoppable in bulk with read-only mode. |
|---|
| Audit log | Yes: an append-only Approval Log in wp-admin recording every sensitive action, the preview you saw, and the result | Every call, denials included with the reason, in your own database: who acted, the connection, IP and duration, and the argument keys and identifiers it touched, never free-text content. Searchable, with optional alerts. |
|---|
| Theme and file access | Yes, and deliberately so: theme file browsing and editing against a draft theme with a preview URL, plus WP-CLI style commands that can activate plugins, switch themes, update options and query the database | No. No code execution, no arbitrary file access, and no plugin or theme management. That is a boundary we chose, not a gap. |
|---|
| Tool catalog | Content management, media uploads, theme file work, WP-CLI style commands, REST API access, page builder writes and abilities other plugins register. No total count stated on the pages checked | 186 governed abilities (92 core, 94 integration), plus a bridge for abilities other active plugins register. |
|---|
| AI clients | Claude Desktop, Claude on the web, Claude Code, ChatGPT, Cursor, Windsurf, OpenCode and any MCP-compatible agent, per their listing | 9 today, including ChatGPT, Claude.ai, and Manus through custom connectors. The Gemini app is not supported yet, stated plainly. |
|---|
| Business model | A free tier plus four paid tiers, from SeedProd | Open source. No affiliate links, no agency upsell, no partner directory shown to your users. |
|---|
| Install base | 100,000+ active installs and 206 ratings (checked 6 November 2026), listed April 2026 | Far smaller. WordPress.org shows 900+ active installs and 5 ratings for us (checked 6 November 2026). They are well ahead of us here. |
|---|