Loading Now

Self-Hosted vs Hosted WordPress MCP: Privacy, Security and the Multi-Site Trade-off

The distinction between self-hosted and hosted WordPress Model Context Protocol (MCP) is significant. In a self-hosted environment, your MCP server operates within your own website, giving you direct control over access and data management. In contrast, with a hosted MCP, a third-party provider manages the server and the connections. This arrangement is often more convenient for agencies that handle multiple sites from a central location.

MCP (Model Context Protocol) enables AI assistants like Claude to interact with your WordPress site using a specific set of tools. If you’re unfamiliar with this concept, you can begin with this overview of MCP in WordPress. This article presumes that you are aware of your AI access requirement and are ready to select the model that suits your needs.

The testing details below were gathered on 2 November 2026: the same commands were executed in Claude, three times each, across a self-hosted setup with Easy MCP AI and two hosted solutions, namely WPVibe relay and WordPress.comโ€™s MCP via Jetpack. Easy MCP AI is developed by Themeisle, the creator of this blog.

Understanding Self-Hosted and Hosted MCP in WordPress

In the case of self-hosted MCP, the MCP server is implemented as a plugin that runs directly within your WordPress installation, allowing the AI client to interact with the site directly without intermediaries. This means that your credentials and activity logs are stored within your own database.

Conversely, hosted MCP operates on external infrastructure. The service accesses your website via a stored password or a platform connection, relaying AI requests from outside your site.

Hosted services vary considerably and are not unified in design. For instance, WPVibe serves as a relay service: your approval is required for each site after which it uses a stored WordPress Application Password to access them. On the other hand, WordPress.comโ€™s MCP employs its own server and connects through Jetpack, relying on your WordPress.com account for access. While both solutions are hosted, the specifics matter greatly, which this guide emphasises you to consider closely.

It’s also beneficial to know if your web host provides MCP services, as these can function on different layers. Some hosts may manage your hosting account with their MCP, which includes sites, domains, and backups. For example, Pressableโ€™s MCP handles such data, while core data remains managed via a WordPress MCP plugin on the site. If your hosting service includes MCP for your content, providers like Hostinger and InstaWP offer integrated solutions, with Servers running inside the WordPress installation, following the self-hosted model. Hostingerโ€™s AI plugin is pre-installed on new WordPress sites under their Business and Cloud plans, while InstaWPโ€™s InstaMCP operates as a site-specific server linked with your installation.

Concept: one key per site for self-hosted MCP versus one master key for multiple sites under hosted MCP.

Testing Methodology for Each Model

The testing involved three common prompts (listing users, retrieving recent orders, and renaming a post), with three iterations run on a WooCommerce test store encompassing 32 users and 24 orders. Each test was conducted in a fresh Claude session. Additional prompts were performed on a combined store and blog setup, using both the self-hosted setup and the relay: one command listed posts on both platforms, while another renamed a post in the blog.

The tests demonstrated consistent success in listing users with their roles and renaming posts across all setups. The only limitation was related to order retrieval, detailed further in the next section. Speed was not the primary focus; rather, the pivotal elements are what each connection can access, the identity it operates under, and the potential limitations.

Considerations for Blog Owners

Blog management revolves around straightforward setup, controlling publishing permissions, and retaining the ability to reverse AI edits if necessary.

The perceived challenge associated with self-hosted setups being developer-centric is mitigated here, as the process involves a plugin and a simple sign-in interface. Installing Easy MCP AI prompts an authentication screen on your site, where you sign in using your WordPress credentials and select an access level for that connection: Full access, Read-only, or Custom. Each AI operation subsequently runs under that user account, ensuring the AI can only act within the constraints of that user’s permissions. (For a detailed guide, see the WordPress MCP setup guide.)

Publishing control is determined by the account associated with the connection. In tests, an Editor account was able to edit posts via Easy MCP AI as well as WPVibe, with both systems attributing the changes to that Editor. Conversely, WPVibe restricted the Editor from listing plugins; operations via WP-CLI or the REST API required Administrator permissions. In the self-hosted context, capabilities are dictated by WordPress roles, further refined by the access level chosen during sign-in.

Tracking AI edits unfolds differently across models. Easy MCP AI retains a history of changes on the site, showing the original and new values of each AI modification, maintained for 30 days and linked to corresponding WordPress revisions. WPVibe captures destructive changes in its Approval Log and does not log typical title alterations; it summarises updates without retaining original values. Meanwhile, WordPress.com logs MCP-related actions on the site, with historical records stored in Jetpackโ€™s Activity Log on WordPress.com.

PRO TIP: Assign individual connections for each user under their WordPress account, rather than sharing a single admin login. This way, with Easy MCP AI, revisions, activity logs, and modification histories will accurately reflect who made each change.

Considerations for WooCommerce Store Owners

Managing an online store introduces additional complexities, particularly with sensitive information such as customer identities, order amounts, and statuses, which you want to keep secure.

A primary consideration is whether the AI can access order data. In tests, listing orders from the past 30 days succeeded in 3 out of 3 attempts through the self-hosted plugin and the relay, but failed across all attempts with WordPress.comโ€™s MCP, which does not expose order data (accessible content types are limited to Products, Forms, and Form Responses). As hosted services vary, verify the available tools before relying on order reporting.

Secondly, consider who will have access to the data. With the self-hosted model, order content is transmitted directly from your site to the AI client, leaving no third-party intermediaries. In contrast, a relay means an additional intermediary exists: the service stores an operational password for your site and handles AI requests. While this can function securely, it is still an additional point where access credentials are stored.

Per-connection access levels further enhance security. Using Easy MCP AI, the person logging in chooses from Full access, Read-only, or Custom for that specific connection on a consent screen managed on your site:

Easy MCP AI consent screen for test store showing Full access, Read-only or Custom options per connection.

Considerations for Agencies Managing Client Sites

Agencies often face a similar decision. MainWP provides a free self-hosted solution where your dashboard operates from your server, keeping your list of sites and client information under your control. Conversely, services such as ManageWP and WP Umbrella offer centralized dashboards running from their Servers, with each site connected through a plugin. Therefore, you can choose between managing your own dashboard or depending on a service provider, similarly reflected in your choice between MCP access for AI.

The tests reveal clear distinctions. Once both test sites were approved, a single WPVibe connection accessed both and executed dual-site prompts successfully. The connection through WordPress.com provided another advantage: one sign-in allowed visibility of all sites under that WordPress.com account within the AI client, and the consent interface enabled per-site selection and per-connection access level:

WordPress.com MCP consent interface displaying per-site and per-connection access options.

In contrast, the self-hosted setup required individual connections for each site, hence necessitating separate sign-ins and access settings for the two test sites. This approach meant more configuration but limited access to each individual credential.

Hosting solutions can also streamline this process, offering unified login access even if the server is self-hosted. For example, Hostinger Connector pairs with your code editor to log in through your Hostinger account, incorporating each site with active Hostingerโ€™s AI plugin and distributing a temporary token for each. While each site retains its server operation, a single login could access them all.

This raises a valid question regarding security: does a hosted service provide more protection simply because it is managed by a company? A well-operated hosted service can be secure, but consider the implications of how many sites a compromised or forgotten credential might reachโ€”one connection per site limits that risk, whereas a single login across multiple client sites could expose all associated sites, including those you may have overlooked.

Disconnecting a Connection

The process of disconnecting a connection is arguably the least straightforward, and the tests revealed unexpected outcomes. In short, uninstalling a plugin only severs AI access if the credential is stored within that plugin.

When Easy MCP AI was uninstalled, its database entries and configurations were eliminated, rendering the previously functional access token invalid. Consequently, access was terminated with the plugin’s removal; however, a dormant connector entry remains in your AI client that you must eliminate manually.

Conversely, simply removing the WPVibe plugin did not curtail access. The relay continued to read and edit the store through an still-active administrator Application Password. WPVibe acknowledges this limitation on its admin page:

โ€œDeactivating or deleting WPVibe does not disconnect this site and does not revoke the WordPress Application Password it uses; connected AI assistants persist in accessing the site via the WordPress REST API. To terminate access, follow both steps: revoke the WPVibe Application Password under Users > Profile > Application Passwords, and remove this site from your WPVibe account.โ€

Warning from WPVibe admin page regarding the plugin deletion not revoking its WordPress Application Password.

The recommended procedure involves the documented two-step method: first, revoke the Application Password, and then remove the site from your WPVibe account. After performing the revocation in testing, requests from the relay were denied, and WPVibe indicated the site as โ€œNeeds attention.โ€ Furthermore, on the second test site, removing it from the AI client in WPVibe also resulted in the password being revoked at the site level.

WordPress.com presented its own surprises. In the WooCommerce store case, eliminating the Jetpack plugin did not disengage WordPress.com because WooCommerce uses the same Jetpack connection for its own functionalities; thus, WordPress.comโ€™s MCP could still edit posts on the store. A full disconnection from WordPress.com was required to end this access. The key takeaway is to ascertain where a connector’s credentials are stored before removal.

BEFORE UNINSTALLING: For any hosted connection, always revoke the credential (Application Password or account connection) prior to removing the plugin. Dismissing the plugin alone can leave an operational key intact.

When to Opt for Hosted Solutions

  • You manage multiple client sites and want the convenience of a single sign-on. Once you approve each site, a single relay connection can access them all, whereas the self-hosted model requires separate connections for every site.
  • Your sites are already hosted on WordPress.com or are linked through Jetpack. The MCP on WordPress.com supplements account-level management features (domains, DNS, plans) alongside its content capabilities, and simply connecting to Jetpack and enabling MCP on your WordPress.com account suffices for usage.
  • You prefer not to handle the MCP server yourself. With hosted MCP, the service manages the server, while your site retains a connector plugin or a platform integration.

Quick Comparison Guide

ScenarioSelf-hosted MCPHosted MCP
BlogA plugin and a sign-in interface; each user connects with their own WordPress account; the tested plugin preserves a before/after history of changes on site.server management handled externally; ascertain what actions are recorded on your site (in tests: logs of destructive actions and brief activity summaries accompanied by minimal MCP-specific data).
StoreOrder details travel directly from the site to the AI client; access levels defined per connection.Access availability varies: the relay accessed order data, yet the platform MCP had no access (0 of 3 tests successful).
AgencyEach site requires a unique connection; a data breach of credentials affects one site only.Single login can access all connected sites; convenient with a broader reach per credential.
DisconnectingIn tests, uninstalling the plugin ceased access and deleted associated data.In tests, removing the plugin did not terminate access; revocation of the password or disconnection of the site is necessary.

Choose the model whose compromises align with your operational requirements: whether you prefer slightly more setup for each site or a credential that may remain active beyond the plugin’s existence. For a direct comparison of specific tools, check out Vamira vs WPVibe; for a broader overview, see server-plugins/”>the best WordPress MCP server plugins.

Which MCP model suits your setup, and were there any unexpected findings from the removal tests? Feel free to share in the comments below!

Hooray! You’ve reached the end of the article!

Share this content:


Discover more from Qureshi

Subscribe to get the latest posts sent to your email.

Discover more from Qureshi

Subscribe now to keep reading and get access to the full archive.

Continue reading