Four different tools promise to connect your WordPress blog to the AI assistant you already use through a WordPress MCP server. Choose the wrong shape and you could end up with a daily call limit you didn’t expect, a login stored where you didn’t intend, or a setup that needs a developer after all.
The four split into two camps. Two are hosted: your AI talks to the vendor’s server, and that server talks to your blog. The other two run on your blog itself, so the AI connects to your site directly, with no relay in between.
In the on-site camp sits Easy MCP AI, a free plugin that turns the blog itself into the server. Easy MCP AI is built by Themeisle, a sister brand of BloggingPro. Competitor facts below come from each vendor’s own docs and WordPress.org listings, with hands-on checks where a run was possible.
In short: Jetpack suits a blog already running it, Easy MCP AI suits bloggers who want no vendor account or meter, WPVibe suits anyone after a guided hosted service, and the MCP Adapter suits a plugin-driven or technical setup. This guide compares all four on where your requests go, what they cost, where the limits sit, what happens before a risky change, and which one fits which blog.
Let’s dive in! 🥽
📚 Table of contents:
- Four ways to connect an AI to your blog
- WordPress MCP servers compared at a glance
- The four options, one by one
- Approvals, logs, and prompt injection
- Which one should you pick?
- Final thoughts on choosing a WordPress MCP server
Four ways to connect an AI to your blog 🔌
🧙 Beginner’s note: MCP (the Model Context Protocol) is an open standard that lets an AI app like Claude or ChatGPT use tools outside the chat, such as reading your posts or saving a draft. A connector is the entry you add in the AI app so it knows where those tools live. A relay is a vendor server in the middle that passes requests back and forth, and an Application Password is a password WordPress generates for one app, revocable without touching your main login. Not sure whether your blog is self-hosted WordPress or WordPress.com? This guide to blogging platforms sorts that out.
The hosted camp runs the server for you: your AI app signs in to the vendor’s service, and that service calls your blog. The on-site camp puts the server on your blog as a plugin, so the AI app talks to your site directly, with no vendor account and no meter. In exchange, you install and update that plugin yourself. The hosted two confirm or gate risky work by default, but on a self-hosted blog they still put a plugin on it (Jetpack, or WPVibe’s for its deeper features), and WPVibe also keeps a login on its servers and meters your daily calls.
If you’re after WordPress’s own MCP plugin, it’s the MCP Adapter, but one name from older tutorials needs clearing up first. Automattic’s old wordpress-mcp plugin has been archived and is no longer maintained, and its README names the MCP Adapter as the canonical plugin for MCP in WordPress. Skip any guide that still installs wordpress-mcp.
One thing is constant across all four options: whatever the AI reads on your blog goes back to your AI app and is processed by its model, which runs in the AI vendor’s cloud unless it runs locally. Other MCP plugins for WordPress exist too, but this guide sticks to these four.
WordPress MCP servers compared at a glance 📋
The four were compared on where your requests go, what you need to connect, price and daily limits, where the login is kept, what each does before a risky change, activity logs, and what the AI can work on, using each vendor’s own docs, pricing pages, and WordPress.org listings. Easy MCP AI’s approval pause and the MCP Adapter’s out-of-the-box abilities were also checked hands-on with Claude Code, plus one Claude-on-the-web connection attempt to the Adapter; Jetpack was compared from its documentation, and WPVibe from its documentation plus its plugin’s own wp-admin screens, because a full hands-on run needs a WordPress.com or WPVibe account and their hosted servers.
Here’s the whole comparison on one screen. Prices are for the WordPress side; the AI app you connect may cost money on its own:
| Jetpack and WordPress.com | Easy MCP AI | WPVibe | MCP Adapter | |
|---|---|---|---|---|
| Where your requests go | WordPress.com’s hosted server | Your blog, directly | WPVibe’s relay | Your blog, directly |
| Account you need | WordPress.com | None | WPVibe | None |
| Price | No Jetpack plan needed to connect; tools vary by plan and hosting | Free | Free, or paid plans from $99 a year | Free |
| Daily limit | None stated | None; a rate limit you set | 100 calls per rolling 24 hours on Free | None |
| Before risky changes, by default | The AI must get your OK in the chat for every write | Nothing pauses until you switch approvals on | Hard-to-undo work waits for approval; some deletes do not | No approval step documented |
| Activity log | Yes | Audit log on the blog | Approval Log on the blog; usage logs at WPVibe | Not documented |
| Themes and page design | Templates, menus, and global styles | Blocks, plus templates and global styles once an admin switches those tools on, and content in existing Elementor elements | Theme drafts and page-builder pages | Not documented |
| Claude and ChatGPT on the web | ChatGPT app directory; Claude via the WordPress.com connector in Claude’s directory, or Jetpack’s external-agent steps for a self-hosted blog | Claude as a custom connector; ChatGPT as a custom MCP server, depending on your plan and workspace settings | Directory listings for both | Default OAuth sign-in unsupported; Claude’s request-header route untested |
The four options, one by one 🔍
Now the detail, in the same order.
1. Jetpack and WordPress.com
Jetpack is Automattic’s plugin that connects a self-hosted blog to WordPress.com, and if your blog already runs it, this route starts with one settings switch, followed by your AI app’s own connection steps. WordPress.com runs a built-in MCP server, and a self-hosted blog connected through Jetpack uses that same server and the same tool catalog: there is no separate Jetpack MCP server to set up. MCP access starts switched off, and one connection can give your AI access to every site on your WordPress.com account.
As a blogger, the appeal is that the AI can draft posts, tidy categories, answer comments, and check your stats through an account you already have. The details that matter:
- Where your requests go: to WordPress.com’s hosted server, which then talks to your blog. The sign-in uses OAuth through your WordPress.com account, so your password never reaches the AI app.
- What it costs: nothing extra to connect. MCP access works on every Jetpack-connected site, free plans included. Which tools a given site gets still depends on its plan and hosting: plugin management, for instance, needs a plan that includes plugin installation. Jetpack’s MCP guide has the details.
- Out of the box: posts, pages, comments, categories, templates, menus, and global styles, plus Jetpack features such as backup, scan, monitor, newsletter, and site stats. Read and write permission groups switch on or off independently, and the settings are shared by every AI app on the account. ChatGPT connects from its app directory, Claude reaches WordPress.com sites through the WordPress.com connector in Claude’s directory, and a self-hosted Jetpack blog connects Claude through Jetpack’s external-agent steps while Jetpack’s own Claude connector is still listed as coming soon.
- Where it’s stronger: every write needs your confirmation in the chat. The AI must describe the change, get your explicit OK, and pass that confirmation to the server, and writes are never auto-executed. Deleted posts and pages stay in the trash for 30 days.
- Watch out: the confirmation is a flag the AI itself sends, not an approval page on your blog, so the safeguard depends on the AI playing along. Media, categories, and tags skip the trash and are permanently deleted.
2. Easy MCP AI
Easy MCP AI is a free plugin that turns your blog itself into the MCP server. The AI app connects to your site directly, and every tool call runs as a real WordPress user with that user’s permission checks. There is no hosted relay, no Easy MCP account, and no vendor quota. Claude adds it as a custom connector, and ChatGPT as a custom MCP server; adding one in ChatGPT depends on your plan and workspace settings.
As a blogger, it suits someone who wants real chores done (drafts, categories, SEO fields, comments) without a meter ticking. On a new install, the rate limit is 120 requests per minute per token, while Force draft on create, Self-service API keys, and Ask before destructive actions all start switched off. The card at its defaults:
Worth knowing:
- Where your requests go: straight from your AI app to your blog, signed in with OAuth or an API key the site stores only as a hash and binds to itself. The plugin itself calls no AI provider.
- What it costs: nothing, with every tool included and no paid tier. There is no daily quota; each connection has a rate limit you set.
- Out of the box: posts, pages, media, comments, categories, menus, users, and revisions, plus tool groups for Yoast SEO, Rank Math, and WooCommerce, each off until you switch it on, with the WooCommerce group covering products, orders, coupons, and store setup. Gutenberg blocks are editable too, and template and global-styles edits work once an admin switches those tools on.
- Where it’s stronger: the paper trail. The Audit log records every MCP tool call while it is on (it is on by default), and the Change history keeps before and after snapshots of changes made through MCP, so the AI can restore many of them. Switch on Ask before destructive actions and its delete, uninstall, and other destructive tools pause for your approval.
- Watch out: approvals are off by default, so nothing pauses until you switch them on. Tools on the Never ask for list skip the pause unless they are also on Always ask for, which wins; a site’s approval filter can override both lists; and API keys marked Unattended never pause, while updates through the post and page tools do not pause unless you add them to Always ask for, though the same edit sent through the general REST write tool does pause. The API-key form also starts on Full access, so start with a Read-only key, and bind the connection to a user whose role fits the job: an Editor account for content chores, not your admin login.
A few more limits: page-builder editing rewrites text, links, and images in the content fields of existing Elementor widgets, and of two other builders’ elements on tested versions only, with no adding, removing, or moving, and there’s no Divi, Bricks or Beaver Builder support. It cannot edit theme files, and OAuth sign-ins need HTTPS on live sites, while API keys should use HTTPS too. Its general REST tools can also reach other plugins’ routes as the connected user, so switching a tool off removes that tool, not every route to the action. It holds 30,000+ active installs and a 98/100 rating from 16 ratings, and the one three-star review is about connecting to Claude. Treat those numbers as a starting point, not a verdict: this guide to picking plugins shows how to read them.
3. WPVibe
WPVibe, from SeedProd, is the polished hosted option: a relay service between your AI app and your blog, with a free WordPress plugin on the site for its deeper features. It is listed in the ChatGPT app directory and Claude’s connectors directory, and it shows 90,000+ active installs with 185 five-star reviews out of 187. WPVibe is candid about the trade on its security page: “We do not claim that site content never leaves your host.”
As a blogger, it suits someone who wants theme drafts and page-builder help from the AI and whose workload fits a daily allowance. The plans, per account, on annual billing:
- Free: $0, with 100 calls per rolling 24 hours; new accounts get 300 for their first 7 days, once per site.
- Pro: $99 per year, 500 calls a day.
- Power: $299 per year, 2,000 calls a day.
- Agency: $599 per year, 5,000 calls a day, plus client invites.
- Scale: $899 per year, 10,000 calls a day.
The annual cards show the first four tiers:
The allowance is shared across every site you connect, and it counts successful reads as well as writes: updating 200 posts one by one takes 200 calls, while failed calls do not count. Banked resets and upgrades can clear the count, and WPVibe’s own advice for big jobs is to batch the work. The details:
- Where your requests go: through WPVibe’s hosted relay. The AI calls WPVibe, and WPVibe calls your blog over HTTPS (it only connects to sites served over HTTPS), using a WordPress Application Password stored encrypted on WPVibe’s servers. Your normal WordPress password is never stored.
- What it costs: the ladder above. Every plan includes every tool and unlimited connected sites, and the free plan covers light work and evaluation.
- Out of the box: content and settings work, theme drafts with a private preview and a backup on publish, page-builder pages written through each builder’s own save pipeline (Divi included), WP-CLI-style commands, and file operations.
- Where it’s stronger: hard-to-undo work waits for your approval by default: permanent deletes of posts, pages, comments, users, or plugins, raw SQL writes, site-wide search and replace, and admin-access changes all pause with a preview first. The safety FAQ lists the full set.
- Watch out: the meter is real, and the two reviews below five stars both name the call limit as the friction. Everyday edits do not ask, and a per-site switch called Dangerously bypass approvals can turn the prompts down to a minimum: it is off by default, admin-only, and WPVibe’s own tools refuse to switch it on.
4. WordPress MCP Adapter
The MCP Adapter is WordPress.org’s own free plugin, and it is a building block rather than a finished product. It adds one address to your blog and exposes whatever abilities your plugins have marked public. On a fresh site, that is three read-only abilities covering site, user, and environment info: in checked runs, asked to list recent posts or to write one, the AI found nothing it could use and said so. It’s listed in the plugin directory, published by WordPress.org, and installs like any other plugin:
As a blogger, this one fits if a plugin you rely on publishes abilities, or if you enjoy a technical setup: most desktop apps connect through a small helper that needs Node.js on your computer, and the sign-in uses a WordPress Application Password. The site-owner guide walks through it. Worth knowing here:
- Where your requests go: from your AI app, or a helper on your computer, straight to your blog. The Application Password lives in your AI app’s settings on your computer.
- What it costs: nothing, and there is no vendor service in the path. It does need WordPress 6.9 or newer, and HTTPS on a live site, because WordPress only offers Application Passwords on sites served over HTTPS; local development sites are the exception, and a site on your own computer can connect over WP-CLI with no password at all.
- Out of the box: three tools, one to list the public abilities on your site, one to read an ability’s details, and one to run it. It provides no AI features of its own.
- Where it’s stronger: it is the foundation WordPress itself is building on, and abilities act as the WordPress user you connect with: an assistant connected as an Editor cannot do what an Editor cannot do.
- Watch out: the web versions of Claude and ChatGPT can’t connect to it through their OAuth sign-in, because WordPress doesn’t include an OAuth server; Claude’s connector dialog also offers a request-headers option, but whether that works with an Application Password is untested, and one live attempt from Claude on the web, using its default sign-in, failed at the OAuth step. The Adapter’s own documentation describes no approval step or activity log of its own, though every Application Password shows when it was last used.
Approvals, logs, and prompt injection 🛡️
The difference that matters most on a live blog is what happens before something irreversible. Deleting a tag is the tidy test case, because WordPress keeps no trash for tags or categories, and media is deleted permanently on most sites. With Jetpack’s server, the AI must get your confirmation in the chat for every write, permanent deletes included. WPVibe waits for approval on hard-to-undo operations, but its docs note that categories, tags, menu items, and media on most sites are deleted for good through the REST route, with no approval page. Easy MCP AI pauses deletes only after you switch on Ask before destructive actions: in one checked run with the switch on, asked to delete an unused tag, the AI confirmed no post used it, then stopped with “The site requires your approval first.” and ran the delete only after approval on the site. So at their defaults, Easy MCP AI does not pause a tag delete and WPVibe does not pause one sent through the REST API, while Jetpack’s protocol asks for confirmation on every write. The MCP Adapter’s documentation describes no approval step.
The paper trails differ too. Easy MCP AI keeps its Audit log and Change history on the blog, Jetpack shows an activity log of agent actions in your account, WPVibe records approved operations in an Approval Log in wp-admin and generally keeps usage logs on its side for up to 24 months, and the MCP Adapter documents error logging aimed at developers, while WordPress’s own Application Passwords screen shows when each password was last used.
One risk applies to all four, and no default setting removes it: prompt injection. Text the AI reads (comments, form entries, imported posts) can hide instructions, and OWASP puts it first on its risk list for AI applications. The mitigations are unglamorous, and they reduce the impact rather than remove the risk: use read-only or narrow credentials for chores that touch untrusted content, bind every connection to a user whose role fits the job, switch on approval prompts for destructive work where the option exists, and read the log after the AI has been in.
💡 Pro tip: whatever you try first, start with the narrowest access it offers (a Read-only key or access level where one exists, otherwise a low-role WordPress user), watch whatever log it offers (or the Application Password’s last-used date) for a few days, and only then widen the permissions.
Which one should you pick? 🎯
No single one wins, because the four answer different needs:
- Jetpack and WordPress.com may suit you if your blog already runs Jetpack, you’d rather switch on MCP in its settings than install another MCP plugin, and you like every write needing your OK in the chat.
- Easy MCP AI may suit you if you want real blog chores done with no vendor account, no daily meter, and a log of every MCP tool call on your own blog, and you don’t mind switching its approval prompts on.
- WPVibe may suit you if you want a guided hosted service with theme drafts and builder help, and your workload fits inside a daily call allowance.
- The MCP Adapter may suit you if a plugin you rely on publishes abilities, or you like building on the same foundation WordPress is standardizing on.
Test one at a time: run one MCP plugin per site, and back up first. Switching off is simple with each: disconnect the AI app in your WordPress.com account’s connected-applications screen for Jetpack, revoke keys under Easy MCP AI’s Connections screen or switch on Pause AI access on its Dashboard, disconnect the site or revoke the Application Password for WPVibe, and revoke the Application Password under Users > Profile for the MCP Adapter. When you are ready to wire one up, the step-by-step setup is in the guide to connecting Claude to WordPress.
👉 Get Easy MCP AI free from WordPress.org
Final thoughts on choosing a WordPress MCP server
Here’s the recap, with what you give up for each:
- Jetpack and WordPress.com: your requests go through WordPress.com’s server, one sign-in reaches every site on the account, and the write check rests on a confirmation the AI itself sends.
- Easy MCP AI: no account, quota, or relay, but its approval prompts stay off until you switch them on, and the plugin is yours to install and update.
- WPVibe: a guided hosted service with approvals for hard-to-undo work and theme drafts, in exchange for a login kept on its servers and a daily call allowance.
- MCP Adapter: WordPress.org’s own free building block, exposing public abilities from WordPress and plugins, with no built-in OAuth sign-in and an untested Claude web request-header route.
None of the four removes the need to supervise an AI with write access. Whichever one you pick, hand it a small chore first and check what changed before you give it a bigger one.
Which chore would you hand to an AI first, and which of the four would you trust with it? Tell us in the comments!
