Self-hosted WordPress MCP means the MCP server runs inside your own site, while hosted MCP means a provider runs the server for you and holds the access it needs to reach your site. For a single blog or a WooCommerce store, self-hosted keeps access, logs and removal in your own hands; for an agency running many sites from one place, a hosted login trades that control for convenience.
MCP (Model Context Protocol) is the standard that lets an AI assistant such as Claude read and change things in WordPress through a controlled set of tools. If the concept is new, start with what MCP means for WordPress. This guide assumes you already know you want AI access and need to pick the model that should deliver it.
The proof points below come from tests run on 2 November 2026: the same prompts in Claude, three runs each, against a self-hosted setup (Easy MCP AI on the site) and two hosted ones (the WPVibe relay and WordPress.com’s MCP through Jetpack). Easy MCP AI is made by Themeisle, the company behind this blog.
What “self-hosted” and “hosted” mean for WordPress MCP
With self-hosted MCP, the MCP server is a plugin that runs inside your WordPress site, and the AI client talks straight to the site with nothing in between. Your credentials and activity logs stay in your own database.
With hosted MCP, the MCP server runs on the service’s infrastructure. The service reaches your site through a stored password or a platform connection and relays the AI’s requests in from outside.
Hosted is a range, not a single design. WPVibe is a relay service: you approve each site once, and the relay reaches it with a stored WordPress Application Password. WordPress.com’s MCP is a platform’s own server: your site connects through Jetpack, and access follows your WordPress.com account. Both are hosted, yet they differ on exactly the things that matter, which is why this guide keeps telling you to check.
Your web host may offer MCP too, and it helps to know which layer it works on. Some hosts’ MCP manages the hosting account: sites, domains, backups. Pressable’s MCP is one example, and store data such as products and orders still comes through a WordPress MCP plugin on the site. When a host does offer MCP for your content, Hostinger and InstaWP are two examples, and in both the server runs inside the WordPress install, which is the self-hosted model. Hostinger’s AI plugin comes pre-installed on new WordPress sites on its Business and Cloud plans, and InstaWP’s InstaMCP is a per-site server that lives with the install.

How the two models were tested
Three everyday prompts (list users, list recent orders, rename a post) ran three times each on a WooCommerce test store with 32 users and 24 orders, each run in a fresh Claude session. Two more prompts ran with a store and a blog connected at the same time, through the self-hosted setup and the relay: one listed posts on both sites, one renamed a post on the blog.
Listing users with their roles and renaming a post succeeded in every run on all three setups. The one gap was orders, covered in the store section below. Speed was not the story. The story is what each connection can reach, who it acts as, and what it leaves behind.
If you run a blog
A blog’s concerns are simple setup, control over who can publish, and a way back from a bad AI edit.
Setup is the weak spot in the “self-hosted is for developers” objection: here it is a plugin and a sign-in screen. You install Easy MCP AI, the AI client opens a consent screen on your site, you sign in as your own WordPress user, and you pick an access level for that connection: Full access, Read-only or Custom. Every AI call then runs as that account, so the AI can never do more than that user could. (For the click-by-click walkthrough, see the WordPress MCP setup guide.)
Who can publish depends on the account behind the connection. In the tests, an Editor account edited posts successfully through Easy MCP AI and through WPVibe, and both credited the edits to that Editor. Past content, WPVibe refused the Editor: listing plugins, through WP-CLI or the REST API, needed an administrator. On the self-hosted side, what a connection can do is the WordPress role narrowed further by the access level chosen at sign-in.
Seeing what the AI changed is where the models diverge. Easy MCP AI keeps a change history on the site that shows the old and new value of each AI edit, kept for 30 days by default and tied to the matching WordPress revision. WPVibe’s on-site Approval Log records destructive operations and approval-bypass changes, so an ordinary title change does not appear in it; the plugin also keeps a short “Post updated” summary without the old value. WordPress.com leaves no MCP record on the site itself; its history is kept in Jetpack’s Activity Log on WordPress.com.
💡 PRO TIP: give each person their own connection under their own WordPress account instead of sharing one admin login. With Easy MCP AI, revisions, the activity log and the change history then show who was behind each change.
If you run a WooCommerce store
A store raises the stakes, because customer names, order totals and statuses are exactly the data you do not want traveling further than necessary.
First question: can the AI reach orders at all? Listing orders from the last 30 days worked in 3 of 3 runs through the self-hosted plugin and through the relay, and in 0 of 3 through WordPress.com’s MCP, whose tools do not expose orders (only Products, Forms and Form Responses are reachable as content types). Hosted services differ here, so check the tool list before you count on order reporting.
Second question: who sees the data? With the self-hosted model, order content travels from your site straight to your AI client and its provider; no third party sits in the middle holding a credential. A relay adds one more stop: the service stores a working password for your site and passes the AI’s requests through. That can be perfectly well run, and it is still one more place your store’s access exists.
Per-connection access levels help here too. With Easy MCP AI, the person signing in chooses Full access, Read-only or Custom for that one connection, on a consent screen that lives on your own site:

If you run an agency with client sites
Agencies have seen this exact trade-off before. MainWP is free, self-hosted software: your dashboard runs on your own server, and your site list and client details stay in your own WordPress database. ManageWP and WP Umbrella give you one dashboard run by the service, with each site connected through a plugin. A dashboard you run yourself, or one run by a service. MCP access for AI is the same choice, with a new credential to think about.
The tests show the shape of it. Once both test sites were approved, one WPVibe connection reached both and handled the two-site prompts in every run. WordPress.com’s connection went further: one sign-in put every site on that WordPress.com account within the AI client’s view, and the consent screen offered no per-site choice and no per-connection access level:

The self-hosted setup took the opposite shape: one connection per site, each with its own sign-in and its own access level, so the two test sites needed two connections. More setup, smaller reach per credential.
Hosting tools can bring the one-login shape back even when the server is self-hosted. Hostinger Connector, an extension for your code editor, signs in with your Hostinger account and adds every site with Hostinger’s AI plugin active, issuing a short-lived token for each. The servers still run on each site, but one sign-in reaches all of them.
That is the concrete answer to “hosted must be more secure, a company runs it.” A hosted service can be well run. The question is how many sites one leaked or forgotten credential reaches. With one connection per site, it reaches that site. With one login across thirty client sites, it reaches all thirty, including any you forgot were still attached.
When you stop using a connection 🚪
Removal is the least glamorous part of this decision, and the tests found surprises. The short version: uninstalling a plugin only ends AI access when the credential lives in the plugin.
Uninstalling Easy MCP AI removed its database tables and options, and the access token that had worked before was refused from then on. Access ended with the plugin; the only leftover is the dead connector entry in your AI client, which you remove there.
Deleting the WPVibe plugin did not cut access. The relay kept reading and even editing the store through a still-valid administrator Application Password. WPVibe says so on its own admin page, which deserves credit:
“Deactivating or deleting WPVibe does not disconnect this site and does not revoke the WordPress Application Password it uses; connected AI assistants keep reaching the site through the WordPress REST API. To cut access, do both: revoke the WPVibe Application Password under Users > Profile > Application Passwords, and remove this site from your WPVibe account.”

The fix is the documented two-step: revoke the Application Password, then remove the site in your WPVibe account. After revocation in the test, the relay’s requests were refused and WPVibe marked the site “Needs attention.” On the second test site, removing it through WPVibe from the AI client also revoked the password on the site itself.
WordPress.com had its own surprise. On the WooCommerce store, removing the Jetpack plugin still left WordPress.com connected, because WooCommerce runs the same Jetpack connection for its own features; WordPress.com’s MCP could still edit posts on the store. A full disconnect of the site from WordPress.com ended it. The lesson: before you delete a connector, find out where its credential lives.
🆘 BEFORE YOU UNINSTALL: for any hosted connection, revoke the credential (Application Password or account connection) first, then remove the plugin. Removing the plugin alone can leave a working key behind.
When hosted is the better choice
- You run many client sites and one sign-in matters most. Once each site is approved, one relay connection reaches all of them; the self-hosted model needs one connection per site.
- Your sites already live on WordPress.com or are Jetpack-connected. WordPress.com’s MCP adds account-level tools (domains, DNS, plans) to its content tools, and a free Jetpack connection plus switching MCP on in your WordPress.com account was enough to use it.
- You don’t want to run the MCP server yourself. With hosted MCP the service runs the server; your site keeps a connector plugin or a platform connection.
The quick chooser 🧭
| Situation | Self-hosted MCP | Hosted MCP |
|---|---|---|
| Blog | A plugin and a sign-in screen; each person connects as their own WordPress user; in the tested plugin, a before/after change history on the site. | No server to run; check what gets logged on your site (in the tests: destructive-action records plus brief activity summaries, or nothing MCP-specific). |
| Store | Order data goes from your site straight to the AI client; access level chosen per connection. | Varies: the relay listed orders, the platform MCP had no orders access (0 of 3 runs). |
| Agency | One connection per site; a leaked credential reaches one site. | One login can reach every connected site; convenient, with a wider reach per credential. |
| Leaving | In the tests, uninstalling the plugin ended access and removed its data. | In the tests, removing the plugin alone did not end access; revoke the password or disconnect the site. |
Pick the model whose trade-off you can live with: a little more setup per site, or a credential that lives somewhere else and may outlive the plugin. For a head-to-head of two specific tools, see Novamira vs WPVibe; for a wider look at the field, see the best WordPress MCP server plugins.
Which model fits your setup, and did anything in the removal tests surprise you? Share it in the comments section below! 👇
FREE GUIDE
4 Essential Steps to Speed Up Your WordPress Website
Follow the simple steps in our 4-part mini series and reduce your loading times by 50-80%. 🚀


















