What is the WP Rollback MCP server?
The WP Rollback MCP server from AcrossAI lets Claude, ChatGPT, Cursor and any other MCP client put an installed plugin or theme back on an earlier version — the recovery step for a bad update. It runs inside WordPress through the free Abilities Manager and MCP Manager plugins, driving WordPress core’s own upgrader — with no third-party relay in between. WP Rollback is optional, and adds the one thing core cannot do.
Looking for another plugin? Browse all WordPress MCP integrations or the Updates and Versions integrations.
What your AI can do
WordPress only ever moves forward. Once a plugin is on 4.3.5 there is no route back to 4.3.1 — and that is the single most common thing you need after an update breaks a site. These abilities add the missing direction, and the reads that make it safe to use.
Roll a plugin or theme back
Move an installed plugin or theme onto any version WordPress.org published, in either direction. Settings and content survive, and an active plugin comes back active.
See which versions exist
Every release the directory published for one asset, newest first, with the installed one marked and each labelled older, same or newer than it.
Pre-flight before anything moves
Check the version exists, whether it is older or newer, and the two things people forget: whether other sites on a multisite use it, and whether it is the active theme.
Repair without changing version
Re-apply the official package for the version already installed, fixing files that have been altered or lost — the repair for what a checksum check reports.
Troubleshooting
An update broke the site. Three things that go wrong next.
Rolling back is easy to get wrong in ways that only show up later.
The downgrade undoes itself
WordPress offers the newer version again at the next update check, and an automatic update takes it back. Every rollback here warns about it explicitly.
The plugin comes back deactivated
Overwriting a plugin’s folder drops it out of the active list as a side effect nobody asked for — which looks exactly like the old version crashing. It is reactivated, and the response says so.
A multisite moves every site at once
Rolling back a network-activated plugin affects the whole network. check-asset-rollback reports that before you commit.
Try asking
Paste one into Claude, ChatGPT or Cursor once your site is connected.
“That last Akismet update broke my contact form — put it back on the previous version.”
“What versions of this plugin can I go back to?”
“Is it safe to roll this theme back? It is the active one.”
“The checksum check says this plugin has modified files — fix it.”
“Roll WooCommerce back one minor version, then verify the files.”
“Can this site roll plugins back at all?”
WP Rollback + AI questions
Is there an MCP server for rolling back WordPress plugins?
Yes. AcrossAI turns your WordPress site into an MCP server with dedicated version-targeting abilities, so Claude, ChatGPT, Cursor or a local model can put a plugin or theme onto a chosen version directly. It’s free on WordPress.org.
Do I need the WP Rollback plugin installed?
No — and this is the part worth reading. Version moves go through WordPress core’s own upgrader, which has backed the previous copy up and restored it on failure since WordPress 6.3. So rolling a plugin or theme back works on a site that has never heard of WP Rollback.
What WP Rollback adds is its local archive of versions it has installed before. That is the only route to an earlier version of a plugin WordPress.org does not host — a premium or privately-distributed one. If you need that, install it; otherwise you do not.
Is it safe? What if the rollback fails halfway?
The previous copy is moved aside before the new package is applied, and restored automatically if the package fails — on WordPress’s shutdown hook, so it survives even a PHP timeout. That is WordPress core’s own mechanism, not ours. The swap also happens behind maintenance mode, so visitors never hit a half-written plugin.
Will I lose my settings or content?
No. A plugin’s settings and data live in the database, not in its folder, and only the folder is replaced. For themes, Customizer settings and template edits are also stored outside the theme directory, and child themes are separate folders that are never touched.
Does a rollback stick?
Not on its own. WordPress will offer the newer version again at the next update check, and an automatic update can undo it — so disable updates for that plugin if the older version has to hold. Every rollback response says this explicitly rather than leaving you to find out.
Can it roll back WordPress core?
Not through these abilities — they cover plugins and themes. WordPress core has its own: core/rollback-wp-core moves it once, and the WP Downgrade integration holds it on a chosen version.
Can I roll back a premium plugin?
Only to a version this site already holds a local archive of, which requires WP Rollback. WordPress.org publishes no release history for premium or privately-hosted plugins, so there is nothing to download. The abilities say so by name rather than failing vaguely.
Who can run these abilities?
Only administrators, and the writes additionally require an explicit confirm. Changing the active theme’s version needs a second flag on top of that, because visitors see the result immediately.
Which AI assistants work with it?
Any MCP client: Claude, ChatGPT, Gemini, Grok, Cursor, Claude Code, and local runtimes such as Ollama, LM Studio and Open WebUI.
Does my site data pass through AcrossAI’s servers?
No. Your WordPress site runs the MCP server and your AI client connects to it directly. Packages are downloaded from WordPress.org by your own site. There is no hosted gateway in the middle.
Is AcrossAI affiliated with WP Rollback?
No. AcrossAI built and maintains this integration independently, using WordPress’s own APIs and WP Rollback’s public services.
