WordPress MCP Servers for Multiple Sites, Compared (2026)

An MCP server is what lets Claude, ChatGPT or another AI app use tools on your WordPress sites. If you look after more than one site, the question is which server can see all of them, what it can change, and what happens when a change goes wrong.

We compared six options from their own documentation in November 2026: InstaWP’s mcp-wp, the MainWP MCP Server, Modular DS MCP, the WordPress.com MCP server (which Jetpack sites also use), the official WordPress MCP Adapter, and TalkToWP. TalkToWP is our product, so we have tried to be stricter about it than about the others. We did not run every product. Where a vendor’s page does not say something, the table says “not stated” rather than guessing.

What is the best WordPress MCP server for multiple sites?

It depends on what you already use. MainWP users should start with MainWP’s own MCP server. Agencies that want a hosted connection that works in claude.ai and ChatGPT should look at Modular DS, WordPress.com via Jetpack, or TalkToWP. Developers who want direct content editing on up to 10 sites from a desktop app can use InstaWP’s mcp-wp.

Short version by need:

If you mainly want to…	Look at
Run updates across sites you already manage in MainWP	MainWP MCP Server
Edit content, media and users on a handful of sites from Claude Desktop	InstaWP mcp-wp
Manage updates, backups and uptime from a hosted dashboard, inside claude.ai or ChatGPT	Modular DS MCP
Work on WordPress.com sites, or self-hosted sites already on Jetpack	WordPress.com MCP
Expose your own plugin’s features to AI on one site	MCP Adapter
Ask what is wrong across a fleet, then apply plugin and theme updates with automatic rollback	TalkToWP

How did we compare them?

Eight criteria, each defined so the cells mean the same thing across columns:

• Hosted or local: does the server run on the vendor’s infrastructure (you paste a URL), on your own computer (a Node.js program your AI app starts), or inside each WordPress site?
• Authentication: how the AI app proves who you are. OAuth means a sign-in and approval screen. Application Passwords are WordPress’s revocable app passwords.
• Site limit: how many sites one connection can reach.
• Read and write scope: what the AI can read and change.
• Monitoring data: whether the server can report uptime, errors, security or performance, not just site settings.
• Rollback: whether a change the server makes can be undone automatically.
• Status: beta, experimental or stable, as the vendor describes it.
• Price: what you pay for the server and the product it depends on.

Hosted servers with OAuth are the ones that work in claude.ai and ChatGPT in the browser. Local servers work in Claude Desktop, Claude Code, Cursor and similar apps. That one difference rules options in or out for many people.

WordPress MCP servers compared: setup and access

	InstaWP mcp-wp	MainWP MCP Server	Modular DS MCP	WordPress.com MCP	MCP Adapter	TalkToWP
Hosted or local	Local (Node.js on your computer)	Local (Node.js 20.19+ on your computer)	Hosted (mcp.modulards.com/mcp)	Hosted (public-api.wordpress.com/wpcom/v2/mcp/v1)	Inside each WordPress site	Hosted (app.talktowp.com/mcp)
Authentication	Application Password per site, in environment variables	Application Password for your MainWP Dashboard user	OAuth sign-in, no API keys	OAuth 2.1	Application Password, or WP-CLI for a local site	OAuth 2.0 with consent screen; read and write scopes
Works in claude.ai and ChatGPT web	No (local)	No (local)	Yes, per vendor	Yes (WordPress.com connector and ChatGPT plugin)	No (no OAuth server)	Yes in claude.ai (listed in Claude’s directory). In ChatGPT it works as a custom MCP connector; which plans can add one is set by OpenAI
Site limit	Up to 10 sites	The sites in your MainWP Dashboard; no cap stated in its docs	Depends on your Modular DS plan	Every site on the WordPress.com account, including Jetpack-connected sites	One site per connection	Free: 1 site. Agency: 10 (+$5 per extra). Scale: 50. Enterprise: 100
What you install on sites	Nothing new (uses the REST API)	Nothing new for MCP if you already use MainWP	Not stated on its MCP page	Jetpack, for self-hosted sites	The MCP Adapter plugin	TalkToWP’s WordPress plugin

WordPress MCP servers compared: what they can do and cost

	InstaWP mcp-wp	MainWP MCP Server	Modular DS MCP	WordPress.com MCP	MCP Adapter	TalkToWP
Read and write scope	Content of any type, taxonomies, media, users, comments; list, activate, deactivate and create plugins; optional read-only SQL	Official docs list 64 tools across sites, updates, clients, tags and batch operations; destructive operations stop at a confirmation gate	100+ tools across most dashboard tasks. Reports, notifications and the Patch & Protect add-on are not available yet	Posts, pages, media, comments; templates, menus, styles; settings; plugins (search, install, update, activate, remove)	Whatever abilities the site exposes. On WordPress 7.1 core, three read-only abilities	15 read tools; 21 change tools for updates, content, pages and templates, WooCommerce, and files in wp-content
Plugin updates	No update tool listed	Yes, with confirmation on Dashboard 6.3+	Yes	Yes (plugin management write group)	Only if a plugin registers an ability for it	Yes, plugin, theme and core
Monitoring data	None	Not itemised in its docs; example prompts include sites that haven’t synced in 24 hours	Uptime, vulnerabilities, backups, per the vendor	Jetpack Backup and Scan state, Monitor downtime alert status	None	Uptime every 5 minutes, Lighthouse and Core Web Vitals, PHP errors, WP-Cron, security headers, incidents
Rollback	None documented	Not described in its safety docs	Not defined on the page we read; the example mentions a confirmation prompt before a safe update runs	Not described on the Jetpack MCP page	None	Plugin and theme updates: snapshot, check, automatic rollback. Core updates and file writes: no rollback
Status	Not labelled beta or stable in its README	Open source (GPL-3.0); no beta label in its docs	Described as beta, in an “experimental phase”	Live; free-plan Jetpack sites have access through 30 November 2026	Experimental, v0.7.1	Live
Price	Free, open source (licence not stated on its README page)	MCP server free; the MainWP Dashboard it connects to is a separate product	MCP included on all plans during its experimental phase; no prices on the MCP page	Jetpack AI or Jetpack Complete plans for MCP access; no prices on the Jetpack MCP page	Free	Free (1 site, MCP read only); Solo $9, Agency $49, Scale $199, Enterprise $359 per month, introductory

Sources: InstaWP mcp-wp, MainWP MCP quickstart, Modular DS MCP, WordPress.com MCP docs, Jetpack MCP support page, WPShout on the MCP Adapter and TalkToWP MCP. Checked November 2026.

MainWP MCP vs InstaWP MCP: which is better for multiple sites?

They do different jobs. MainWP’s server is for site management: updates, syncing, plugins, themes, clients and tags across every site in your MainWP Dashboard. InstaWP’s mcp-wp is for content: posts, pages, media, users and comments on up to 10 sites. Both run locally and use Application Passwords.

Choose MainWP’s MCP server if you already run a MainWP Dashboard. It talks to the Dashboard, not to each site, so nothing new goes on your child sites. It needs Dashboard 6.0 or later on HTTPS with WordPress 6.9 or later, and Node.js 20.19 or later on your computer; some features, including update confirmation, need Dashboard 6.3 (MainWP quickstart). Its safety design is careful: a destructive request first produces a preview and a one-time confirmation token, the token must match the same operation and be less than 5 minutes old, and a “safe mode” blocks destructive calls entirely (MainWP safety). The docs also say what it cannot do: log into wp-admin, bypass WordPress permissions or run arbitrary code.

Choose InstaWP’s mcp-wp if the work is content. You list each site’s URL, username and Application Password as numbered environment variables, and every tool accepts a site ID; the README says it supports up to 10 sites (InstaWP mcp-wp). It has a single set of tools for any content type, including custom post types, plus media, users and comments. For plugins it can list, activate, deactivate and create them, but the README lists no tool for updating them. An optional read-only SQL tool needs a custom endpoint on the site and an administrator-level user.

Neither reports uptime or errors. If you need to know which sites are unhealthy, that has to come from somewhere else.

Notes on each option

Modular DS MCP

Modular DS is a hosted management dashboard, and its MCP server is hosted too. You paste https://mcp.modulards.com/mcp into Claude or ChatGPT, sign in with your Modular DS account, and pick read-only or read and write (Modular DS help). The vendor calls it a beta with 100+ tools, and lists what is missing so far: creating or scheduling reports, managing notifications and configuring its Patch & Protect add-on (Modular DS). Its example prompts include update automations gated on an “Update Copilot” score, which the page does not explain. Of the options here, it is the closest to a full maintenance dashboard you can drive from claude.ai.

WordPress.com MCP (and Jetpack)

If your sites are on WordPress.com, or your self-hosted sites already run Jetpack, this is one connection for all of them, signed in with OAuth 2.1 (WordPress.com docs). Read and write permissions are set by group, and plugin management covers installing, updating and removing plugins. It can read Jetpack Backup and Scan state and Monitor’s downtime alert status (Jetpack). MCP access for self-hosted sites is part of the Jetpack AI and Jetpack Complete plans, and free-plan sites can connect through 30 November 2026. The catch for agencies: every site has to be connected to a WordPress.com account, and the tools act through that account.

The official MCP Adapter

The adapter is infrastructure for one site at a time. It turns abilities registered by WordPress core and plugins into MCP tools. It has no OAuth sign-in, so claude.ai and ChatGPT in the browser can’t connect to it on their own, and on WordPress 7.1 core exposes only three read-only abilities (WPShout). It is the right base for plugin developers. It is not a fleet tool. For why it fails on the web apps, see can Claude or ChatGPT manage WordPress.

TalkToWP

TalkToWP’s MCP server is hosted, signs in with OAuth and covers every site on your TalkToWP account (TalkToWP MCP). Its difference is the monitoring data underneath: an AI can ask which sites have PHP errors, stalled cron or weak security headers, read what changed before an incident, and check a plugin’s update risk before applying it. Changes are off by default and need a paid plan, the write scope, AI actions enabled for that site by its owner, and the specific action on that site’s allowed list. Plugin and theme updates are snapshotted, checked afterwards and rolled back automatically if the site returns a server error or WordPress’s critical-error page. Connect it to Claude or ChatGPT; the free plan is read-only and covers one site.

What it does not do:

• WordPress core updates cannot be rolled back, and files written with write_site_file are not snapshotted.
• It does not run backups. Keep your backup tool.
• There are no tools to install or delete plugins, change users or roles, or run database queries. That is deliberate, but it means some jobs still need wp-admin or another tool.
• Site data comes from the last push by its plugin, so it can be out of date until the AI asks the site to push fresh data.
• Its update risk score shows “no data” until a plugin has at least 10 observations.
• The free plan is read-only.
• It needs its own plugin on every site, even if you already run ManageWP or MainWP.

Which WordPress MCP server should you choose?

Your setup	Choice	Why
Agency on MainWP	MainWP MCP Server	Uses the Dashboard you already have; confirmation gate and safe mode
Agency on Modular DS	Modular DS MCP	Hosted, works in web apps; you choose read-only or read and write
Sites on WordPress.com or Jetpack	WordPress.com MCP	One OAuth connection for all sites on the account
Content team, up to 10 sites, desktop app	InstaWP mcp-wp	Broad content, media and user tools
Plugin developer	MCP Adapter	Official base for exposing abilities
Want diagnosis plus plugin and theme updates with rollback in claude.ai	TalkToWP, alongside your existing dashboard	Monitoring data and per-site permissions; no backups, no core rollback

Whichever you pick, start read-only for a week. See what the AI gets right before you let it change a live site. For the update side, our decision table for updating plugins applies whether a person or an AI clicks the button. If you run a fleet, the agency page and the agency maintenance checklist cover how TalkToWP sits alongside your dashboard.

Frequently asked questions

What is the best WordPress MCP server for multiple sites?

There isn’t one best. MainWP’s server suits MainWP users, Modular DS and TalkToWP suit agencies wanting a hosted connection that works in claude.ai, WordPress.com suits Jetpack sites, and InstaWP’s mcp-wp suits content work on up to 10 sites.

What is the difference between MainWP MCP and InstaWP MCP?

MainWP’s server manages sites through your MainWP Dashboard: updates, plugins, themes, clients. InstaWP’s mcp-wp edits content, media, users and comments on up to 10 sites. Both run on your computer and use Application Passwords.

Which WordPress MCP servers work in claude.ai and ChatGPT?

The hosted ones with OAuth sign-in: WordPress.com (for WordPress.com and Jetpack sites), Modular DS and TalkToWP, per their documentation. Which ChatGPT plans can add a custom MCP server is set by OpenAI. Local servers such as MainWP’s and InstaWP’s work in desktop and coding apps instead.

Can an MCP server roll back a bad plugin update?

Some can, for some changes. TalkToWP snapshots plugin and theme updates and restores them automatically if the site breaks, but cannot roll back core updates. For the others, rollback through MCP is not described on the pages we read.

Is the WordPress MCP Adapter good for managing many sites?

No. It runs inside one site and connects one site at a time. It is the official base for exposing abilities, and on WordPress 7.1 core exposes only three read-only ones.