Novamira vs WPVibe vs MCP Adapter vs Easy MCP AI (2026)

Novamira vs WPVibe looks like one head-to-head, and the short answer is that they solve different problems: Novamira lets an AI run PHP, WP-CLI commands and file operations inside your site, while WPVibe gives the AI a curated toolbox through a hosted relay. Two more routes belong in the same decision.

The MCP Adapter is WordPress’s bridge between plugins and AI clients, newly on WordPress.org, and Easy MCP AI is a free plugin answering through named tools with access levels. This guide compares the four on architecture, reach, live-site fit and cost. For running a live site from chat, Easy MCP AI is the recommendation, and the pick list near the end says when each of the other three fits better. Easy MCP AI is made by Themeisle, the company behind this blog. If MCP is still fuzzy, read what MCP means for WordPress first.

The short version

In a rush ⏱️? This table sums up the main differences.

Option	Runs where	The AI can touch	Price	Best for
Novamira	Your site, direct	PHP, WP-CLI, files, database	Free; Pro from €49/year (€69 regular)	Developers on staging
WPVibe	Hosted relay plus a free plugin on your site	Curated tools, 125+ WP-CLI style commands	Free tier; Pro at $99/year	Hosted setup, live sites with approvals
MCP Adapter	Your site, direct	Only abilities marked public	Free	Developers building abilities
Easy MCP AI	Your site, direct	280+ tools, limited by each token’s access level	Free, no vendor quota	Managing a live site from chat

Method 📋: this comparison covers architecture, reach, live-site safeguards, price and accounts, using vendor documentation, pricing pages, WordPress.org data and, for Novamira, public source code, checked on October 5 to 7, 2026. Novamira and WPVibe are compared from these published sources rather than a hands-on test.

How the four fit together

The MCP Adapter is the base layer. It’s part of WordPress’s AI Building Blocks initiative, and version 0.7.0 was the first release published to the WordPress.org plugin directory, on October 2, 2026. Its own readme states the scope plainly: “MCP Adapter is the server and transport layer. It does not provide any AI features itself.” What it serves are abilities, capabilities that WordPress core and plugins register through the Abilities API, and an ability only becomes reachable over MCP when it is marked public. Clients connect over HTTP or through WP-CLI.

Novamira sits on top of that base layer. Its getting started guide calls the MCP Adapter the “official WordPress plugin, bundled with Novamira”, and the copy it bundles is version 0.6.1, older than the 0.7.0 release on WordPress.org. Novamira adds nine abilities of its own (Execute PHP, seven file abilities and an upload link), plus WP-CLI commands, which together turn the bridge into a development agent.

WPVibe is a different architecture entirely. Its service is a hosted relay at mcp.wpvibe.ai, running on Cloudflare’s servers; the AI client calls it, the relay checks your WPVibe account and the plan’s limits, and only then sends an HTTPS request to your site. There, WordPress’s own REST API handles standard requests such as posts and pages, the free WPVibe plugin handles the rest, and both act as the WordPress user you authorized. The relay is what lets WPVibe work with browser-based clients like Claude.ai and ChatGPT without a local install. It also means every request passes through WPVibe’s servers, and the relay keeps an encrypted application password for your site.

Easy MCP AI is the fourth shape: a self-contained MCP server inside WordPress with no hosted relay and no vendor account, answering through 280+ tools instead of raw PHP. It can also offer WordPress abilities as tools of its own, without the MCP Adapter. On a fresh install on WordPress 6.9 or later, most non-destructive abilities start switched on, and abilities added later stay off until an admin enables them.

Same question, two servers 🔍

Take a small bookshop site running WordPress 7.1.2, with 3 published posts, 1 published page, a draft post and one comment waiting for approval. Here is how each server handled the same site owner question, asked in Claude Code: “Give me a quick status report for this WordPress site: how many posts and pages are published, which plugins are active, and whether any comment is waiting for approval. Don’t change anything.”

With MCP Adapter 0.7.0 from WordPress.org as the only active plugin and the administrator’s application password, the AI can reach three abilities, for site information, user information and environment information. Claude Code’s reply opened with “I couldn’t get any of the three things you asked for.” and explained that the connection “has no way to list posts, pages, plugins or comments.”

That’s the Adapter working as designed. It ships almost nothing until plugins register public abilities, which makes it infrastructure for developers: precisely the layer Novamira builds on.

With Easy MCP AI 2.0.1 from WordPress.org as the only active plugin and an API token on the Read-only access level, which lets the AI view content but not create, change or delete anything, the AI made four read calls (two counts, a plugin list and a comment list). It answered: “Here’s the site status. I only read data and changed nothing.” It reported 3 published posts, 1 published page, 1 active plugin and 1 comment waiting for approval, and even quoted it: “Is The Lantern Keeper available in hardcover?”

💡 PRO TIP: whatever you connect first, start with a question you already know the answer to, like the status report above. It shows what the AI can really reach before you let it change anything.

What the AI can touch, and the live site question

Novamira

Novamira’s free plugin leads with Execute PHP: code that runs with the full WordPress environment, including direct access to the database, every function and every loaded plugin, under a 30 second time limit. Around it sit file read, write, edit and delete, directory listing, WP-CLI commands in the foreground or background, and a temporary link so the agent can upload files to the site. It needs WordPress 6.9 or later, PHP 8.0 or later and an administrator account.

The vendor is blunt about where that belongs: “For development and staging environments only. Always keep backups.” The docs add that this “is a professional recommendation, not a limitation enforced by the plugin”, though a site that looks like production gets a warning before the abilities switch on. New PHP files land in a sandbox, which the docs call “a convenience guardrail, not a security boundary”, and code run through Execute PHP bypasses it entirely. Its crash recovery “Does not roll back changes.” On a staging copy with backups, that trade can make sense.

Two practical notes: the AI abilities start switched off and need a confirmation to switch on, and Novamira is not listed in the WordPress.org plugin directory. You install it from a release ZIP on its site.

WPVibe

WPVibe hands the AI a curated toolbox instead of raw PHP: REST API calls for posts, pages, media, users and settings, media uploads from a URL, draft theme editing with a private preview link, file tools that work with draft theme files, a tool that runs the abilities other plugins register, and commands that work like WP-CLI, 125+ of them by WPVibe’s count. Setup starts with the free WPVibe plugin: install it, authorize the site from the plugin’s admin screen, then add the MCP server URL to your AI client. That plugin is also what brings the draft themes, file operations and WP-CLI style commands listed above.

For live sites the safety model is approvals. Hard-to-undo operations (permanently deleting posts, users or plugins, raw SQL writes, site-wide search and replace, admin access changes) wait on an approval page before anything runs. Theme work happens in an isolated draft only you can preview while logged in. Two gaps deserve attention. Some deletes do not ask: categories, tags, menu items and, on most sites, media are deleted for good when the AI removes them through the REST API, with no approval page. And an administrator can switch on “Dangerously bypass approvals”, which removes the approval prompts: deletes, raw SQL, WP-CLI commands that change things, REST API writes and plugin abilities run as soon as the AI asks. Even then, turning on white label mode, the setting that gives clients a clean wp-admin without WPVibe, waits on an approval page. New code snippets are saved switched off until you turn one on in wp-admin, but an edit to an HTML, CSS or JavaScript snippet that is already on skips that click and goes live right away. Plugin and theme installs keep their confirm step inside the chat, so the AI may still check with you.

MCP Adapter

On its own, the Adapter is the careful minimum: an ability is reachable only when marked public. By default, any signed-in user of the site can connect unless a developer adds a stricter rule. Permission checks run against the connected user, so connect with a limited account, not your admin one. It needs WordPress 6.9 or later.

Easy MCP AI

The current release is Easy MCP AI 2.1.0; the bookshop example above and the token screen below come from 2.0.1. Easy MCP AI answers through named tools covering posts, pages, media, comments, users and menus. WooCommerce and several SEO plugins join once those plugins are active and their tool groups are switched on. GA4, Search Console and other data providers join after you connect your own accounts. The access model is the point: each connection, whether an API token or an AI app you approve through an OAuth sign-in, gets an access level (Full access, Read-only or Custom), and every tool call runs as a specific WordPress user with that user’s permissions.

Three controls matter on a live site. The Audit log, on by default, records every MCP tool call. Change history, on by default on new installs, keeps before/after snapshots of changes made through MCP, and since version 2.1.0 the AI can restore changes from it, though wp-admin has no restore button. An approval switch, off by default, makes Easy MCP AI ask for your approval before destructive actions such as deletes.

The limits are just as concrete: there are no page builder tools, none of the built-in tools runs PHP code, shell commands or WP-CLI, and the Semrush, SE Ranking and DataForSEO integrations need paid accounts with those vendors. If you need PHP or WP-CLI from chat, Novamira runs both, and WPVibe offers WP-CLI style commands.

Price, daily caps and accounts

Novamira is free and open source under the AGPL license for unlimited sites; Pro adds specializations for page builders, themes and plugins plus persistent memory between sessions. Personal is €49 a year for 3 sites (regular price €69), Agency is €149 a year for 1000 sites, and Agency Lifetime is €299 once. All three Pro plans state “No credits, no action quotas.” Pro checkouts run on the maker’s store, dynamic.ooo.

Novamira pricing: free for unlimited sites, Personal €49/year for 3 sites, Agency €149/year, Agency Lifetime €299 once.

WPVibe’s free plan allows 100 tool calls per rolling 24 hours, where a tool call is a successful action on your site, such as reading or editing content or uploading media; failed calls do not count. New accounts get a first-week bonus of 300 calls per rolling 24 hours, which WPVibe gives once per site. Paid plans raise the ceiling: Pro is $99 per year for 500 calls a day, Power is $299 per year for 2,000 and Agency is $599 per year for 5,000, with a Scale tier above that. The daily allowance belongs to the WPVibe account, not to a site, so every connected site draws from the same daily count, and there is one Free account per person.

WPVibe pricing: Free at 100 tool calls a day, Pro $99 a year for 500 a day, Power $299 for 2,000, Agency $599 for 5,000.

The MCP Adapter is a free plugin in the WordPress.org directory, and Easy MCP AI is free with no paid tier, no vendor quota and no Easy MCP account. Easy MCP AI’s extra costs are the optional data APIs, billed by Semrush, SE Ranking or DataForSEO themselves, plus whatever the AI client itself costs.

Sign-in differs as much as price. WPVibe asks for a WPVibe account: when you connect your AI client, it opens a sign-in page where you type your email and the 6-digit code WPVibe emails you. Novamira lets only administrators connect, by OAuth or an application password, over HTTPS except in a local environment.

AI clients reach the Adapter over the web with a WordPress application password, or through WP-CLI, WordPress’s command-line tool. Easy MCP AI connects either through an OAuth 2.1 sign-in, where you approve the AI app on your site, or with per-user API tokens created in wp-admin. For the full click path, follow the step-by-step guide to connecting Claude or ChatGPT to WordPress.

WordPress.org tells its own story 📊: WPVibe’s plugin, listed as vibe-ai by SeedProd, shows 60,000+ active installs and 100 five-star ratings, plus one four-star and one three-star; the MCP Adapter shows 40,000+ installs and no ratings yet; Easy MCP AI shows 10,000+ installs and 11 ratings, all five stars.

Which one should you pick?

💬 For day-to-day work on a live site, start with Easy MCP AI. It runs inside your own WordPress, with no hosted relay and no vendor account, and each connection gets an access level such as Read-only. The Audit log, on by default, records every MCP tool call, and Change history, on by default on new installs, keeps before/after snapshots of changes made through MCP; since version 2.1.0, the AI can restore changes from it. Its 280+ tools reach content, comments and media, plus WooCommerce and SEO plugin fields once those plugins are active and their tool groups are switched on, and GA4 and Search Console data once you connect your own accounts. The plugin is free, with no paid tier.
🔧 If you are a developer, or have one, and want an AI that builds and debugs real code on a staging or dev copy, pick Novamira instead. Its Execute PHP runs AI-written code with the full WordPress environment, and its docs say to keep it off production.
🌐 If you want a hosted relay, with a free plugin on your site and an approval page in front of hard-to-undo changes, pick WPVibe and accept the relay in the middle and a daily cap shared across your sites.
🧱 If you are building your own abilities or a plugin that should speak MCP, pick the MCP Adapter, the layer Novamira builds on.
🧭 If you want to survey the wider field before choosing, read the roundup of the best WordPress MCP server plugins.

ℹ️ Note: prompt injection applies to all four. OWASP ranks it first on its LLM risk list: text the AI reads, such as a comment or a product review, can carry hidden instructions that steer an AI with write access. Defend yourself with read-only access for reading tasks, a limited WordPress user, approval for risky changes, and a review before publishing. With Novamira, neither read-only access nor a limited WordPress user is available: only administrators can connect, and the plugin does not limit what an authenticated admin can do.

Final thoughts 🏁

Easy MCP AI is the site manager: named tools, access levels, an Audit log, free.
Novamira is the power tool: full PHP and WP-CLI, meant for staging and development work.
WPVibe is the hosted convenience: a free plugin plus a relay in the middle, approvals, daily caps.
The MCP Adapter is the foundation: careful, official, and nearly empty until plugins add abilities.

If you run a live site and want to manage it from chat, start with Easy MCP AI, which works inside your WordPress with access levels and an Audit log that is on by default; pick Novamira for code work on a staging copy, WPVibe for a hosted relay with approvals, and the MCP Adapter if you build your own abilities. Which route fits your site, and has another MCP plugin won you over? Let us know in the comments section below!