Updating WordPress core from my phone. No dashboard. No SSH. Just a few messages in a chat app.
WordPress 7.0.4 landed as a security release, so I reviewed it and applied it — standing up, on mobile data, in about two minutes. Here’s how that works and what you’d need to do it yourself.
The two plugins
Both are free on WordPress.org.
- AcrossAI Abilities Manager — registers the operations your site can perform and gives you a single admin page to browse, toggle and govern every one of them. The core update abilities live here.
- AcrossAI MCP Manager — publishes those abilities to your AI assistant over the Model Context Protocol, using WordPress’s own Application Passwords for authentication.
Abilities Manager decides what exists. MCP Manager decides who can reach it. Neither is doing anything exotic — an ability you haven’t enabled simply cannot be called, and every request authenticates as a real WordPress user with that user’s capabilities and nothing more.
The abilities doing the work
Three of them, all in the Core category:
wp-core-update-check— reports the running version, whether an update is offered, and the PHP and MySQL requirements attached to it. Read-only.wp-core-update— applies the update. Re-running when nothing is pending is a clean no-op.wp-core-rollback— moves to an earlier version the WordPress.org API still offers. Marked destructive, and it refuses when the target isn’t older than what’s installed.
Everything runs through WordPress’s own updater — Core_Upgrader, the exact same class behind Dashboard → Updates. No bundled updater, no custom download logic, no custom integrity checks. Each ability requires both manage_options and update_core, matching WordPress core’s own admin gate, and honours DISALLOW_FILE_MODS.
That matters more than it sounds. The failure modes are WordPress’s familiar ones, and so are the recovery paths.
The best part isn’t the speed
Updating WordPress core from mobile is a nice trick, but it isn’t the reason to bother.
The reason is being able to ask “what’s in this update, and can it break my site?” before installing anything.
Click Update Now in the dashboard and you get a version number. Not what changed. Not whether it’s a security fix or a feature release. Not whether it’s likely to affect what you’ve built. You click, and you find out afterwards.
Asking the question first got me the actual shape of the risk: WordPress 7.0.4 is a single security fix — an authenticated Author-and-above remote code execution via malicious file upload, on sites using Imagick and Ghostscript. Three conditions have to hold before you’re exposed. If you run a single-author site on a host using GD, your practical exposure is close to nil. If people you haven’t personally vetted hold Author accounts, it’s urgent.
That’s a decision I could make in ten seconds because I had the information — and it’s the same decision whether you’re at a desk or reading it on a phone at a bus stop. The button couldn’t have told me any of it.
Works with whichever assistant you already use
MCP is an open standard, not a vendor integration. Claude, ChatGPT, Cursor, VS Code with Copilot, Grok and other MCP-capable clients all connect to the same site with no changes on the WordPress side — MCP Manager ships copy-paste configs for each.
Because the connection lives in the assistant rather than in your browser, it behaves identically on mobile and on a laptop. Updating WordPress with Claude on a phone runs the same abilities, in the same order, as it would from a desktop app — there’s no reduced mobile version to work around.
Which also means you’re not locked in. Change assistants next year and your site doesn’t need to know.
Verify after every write
You can’t see the file system from a chat window, so a confirmation read is your only independent check that what you were told actually happened. Ask for a version check after an update, not just before. It costs nothing.
Get the plugins:
AcrossAI MCP Manager · AcrossAI Abilities Manager
Learn more: acrossai.co