A year ago, giving an AI assistant an MCP connection to a WordPress site meant picking one plugin. In September 2026 InstaWP tested twenty-one of them on one live site, and that list left out the official adapter, the hosted services and the builders and themes that ship their own server. Ranking them is not much use, because they are not the same kind of thing. This article groups them by where the server runs and what it writes, so you can tell which group you need before you compare names.
One disclosure first: Delta, the theme this site belongs to, has an MCP server built in. It appears in the last group, and we have tried to describe it with the same measure as the others.
1. The official bridge: WordPress MCP Adapter
The MCP Adapter is the WordPress project’s own plugin, on WordPress.org since October 2026. It connects the Abilities API, which has been part of core since WordPress 6.9, to MCP. It has no AI features of its own and no settings screen. Whatever abilities core and your plugins register and mark public become MCP tools; the client sees three of them (discover, get info, execute), and the ability’s own permission check runs against the signed-in user. Clients authenticate with an Application Password at /wp-json/mcp/mcp-adapter-default-server, or over STDIO through WP-CLI on a local site.
What it exposes depends entirely on what is installed. Themeisle’s write-up found that a site with Secure Custom Fields as its one fields plugin offered fifty-one abilities, five of them permanent deletes and none of them for posts, pages or media. So the adapter is a foundation for developers who register their own abilities, and for products that build on it, such as Bricks, Ollie and The Plus Addons for Elementor. On its own it is not a site-control server, and it is still pre-1.0 software.
2. Server plugins
This is the crowded group: a plugin that runs an MCP server inside your site and exposes WordPress itself (posts, pages, media, users, options) plus whatever plugins it has written integrations for. The agent reads and writes the same data the REST API does, so what it produces is post content in whatever format the active editor or builder stores.
- Easy MCP AI (Themeisle): free, OAuth 2.1 or scoped tokens, 280+ tools by its own count across core, WooCommerce, ACF, SEO plugins and analytics sources. Access levels, a rate limit, an audit log on by default and change-history snapshots the agent can restore from. InstaWP’s test put its everyday guardrails, with Sokket’s, at the top of the field.
- Royal MCP: free with a Pro tier, OAuth 2.0, 250+ tools including Elementor, Divi, ACF, Yoast and WooCommerce. The feature reviewers single out is undo: changes can be reverted for 72 hours.
- AI Engine (Meow Apps): an MCP server inside a broader AI plugin that also does chatbots, content generation and forms. Forty-five tools free, more with Pro. Reviewers found its controls thinner than its tool list.
- Secure MCP Server (miniOrange): built around governance. Nothing is allowed until a role profile exists, tools are assigned per role, and every call is logged. Slower to set up, which is the point.
- Smaller entries worth knowing: Flex MCP (one-click undo and a rate limit), MountDev (dry-run edits and rollback), Enable Abilities for MCP (per-ability switches on top of the adapter), Sokket (revertible Site Editor changes).
Two cautions from the InstaWP test apply to the whole group. Four plugins reported a result that did not match what happened (a call looked successful and had failed, or the reverse). Eight had a security weakness in the version tested. Several have shipped fixes since; check the changelog and test on a staging site.
3. Hosted relays
A relay puts the MCP server on someone else’s infrastructure. The AI client talks to the service, and the service talks to your site. Setup is easier because there is no OAuth server to run on your host, and the service can add approval steps in the middle.
WPVibe is the clearest example: a free plugin plus an account, with a daily action allowance on the free plan. Destructive operations pause for your approval with a dry-run preview, and new posts default to draft. The trade-offs are that every call passes through WPVibe’s servers, and that some deletions (categories, tags, menu items, often media) go straight through the REST API with no approval step and no trash.
WordPress.com’s MCP server is the other one: a single hosted endpoint with OAuth 2.1 for sites on WordPress.com, and for self-hosted sites connected through Jetpack on an eligible plan. Sources disagree about how much of it writes rather than reads, so check the current documentation before you plan around it.
4. Servers inside a builder or a theme
The last group does not expose WordPress in general. It exposes one product’s own model of a page, which means the agent can build layouts rather than only fill in content.
- Elementor exposes its structures through the Abilities system; everything it generates is saved as a draft. Angie, Elementor’s agent, runs its own server at
/wp-json/mcp/angiewith around thirty abilities. - Bricks and Ollie register abilities and connect through the MCP Adapter with Application Passwords.
- Delta puts the server in the theme, at
/wp-json/21press-delta/mcp. The client sees four permanent tools and discovers abilities behind them: pages, templates, design tokens, content types, menus, media, and the plugins Delta integrates (forms, SEO, redirects, WooCommerce, static export). Because the theme renders the page, the agent writes the HTML, CSS and JavaScript the browser receives, against one set of design tokens, rather than a builder’s data structure. Connections are OAuth against your own WordPress login or an Application Password, administrators only, and actions that hand out control wait for approval.
Side by side
| Group | Runs where | Signs in with | Writes | Safety net |
|---|---|---|---|---|
| MCP Adapter | Your site | Application Password | Whatever abilities are public | Ability permission checks; nothing else built in |
| Server plugins | Your site | OAuth 2.1 or 2.0, tokens, Application Passwords | Posts, pages, media and plugin data | Varies: logs, rate limits, undo windows, role profiles |
| Hosted relays | The service’s servers | Account with the service | Posts, pages, media through the REST API | Approval step in the relay; some deletes bypass it |
| Builder or theme | Your site | Application Password or OAuth | The product’s own page model | Drafts (Elementor); approvals and snapshots (Delta) |
What actually differs
What the write produces. This is the question to ask first. A server plugin writes post content, so a page built by the agent is whatever your editor stores: block markup or a builder’s JSON. A builder’s server writes that builder’s structures. A theme’s server writes what the theme renders. If the job is publishing articles, a server plugin is enough. If the job is building or redesigning a site, you want the agent working in the thing that decides layout.
How much the agent has to read. Tool schemas cost context. The adapter’s test site returned fifty-one abilities; AtlasMCP sent 694 tools to the client; Delta sends four tools and the agent asks for one ability’s schema at a time. Fewer, better-described tools mean fewer wrong calls, which matters more than the size of the number on the plugin page.
Who the agent is. With an Application Password the agent is that WordPress user, with every capability the role has. OAuth lets you see and revoke each client. A relay adds a third account, at the service. Whichever you pick, the agent should not be an administrator unless the product requires it, and you should know how to cut it off.
What happens after a mistake. Approval before the action, undo after it, or a snapshot to restore. The products differ most here, and the reviews are worth reading for this column alone.
How to choose
- Content and maintenance on an existing site: a server plugin with an audit log and undo, or the adapter if you can write your own abilities.
- A team that needs role-based access and a record of every call: miniOrange’s model, or a plugin with per-ability switches.
- No server configuration at all, and you accept a third party in the path: a hosted relay.
- Building or redesigning the site itself: the server of the builder or theme that renders your pages. If you are starting fresh, that is where Delta fits; Connect an agent shows the setup for Claude, Cursor and the rest.
- A local site: any client that runs on your machine (Claude Code, Cursor, Claude Desktop with an extension). A cloud connector cannot reach
.test.
Facts in this article come from the vendors’ pages and from Themeisle’s comparison and InstaWP’s test, both updated in late October 2026. Both publishers also sell a product in this list, as we do. Tool counts are the vendors’ own and change monthly.
