MCP for StageIt
Introduction
MCP for StageIt is a free add-on for CS MCP for J, the free extension that turns a Joomla 5 / 6 site into its own MCP server. It gives the AI app you connect (ChatGPT, Claude, Codex, Cursor, VS Code with GitHub Copilot, Gemini CLI or any other MCP app) 11 tools for StageIt, the staging extension from PHP Web Design: check the staging copy, build one, push it to live, restore a backup of live, and remove the staging copy.
Why this exists. In StageIt's admin, a build or push runs from a page you keep open in the browser until it finishes, and its command line needs shell access to the server. This add-on runs StageIt's own steps the way StageIt's command line does, so you can ask for them in plain language from your AI app, and the result is the same as pressing StageIt's own buttons.
What the AI can do. 11 tools:
- Status (3): what StageIt's own status command reports (whether a staging copy exists, when it was built, the last backup and push, and whether a push or a remove would be allowed right now and why not), StageIt's pre-checks, and the list of backups.
- Build (2): build a staging copy from live.
- Push (2): push the staging copy to live, after StageIt backs up live.
- Restore (2): put a backup of live back, files and database.
- Remove (2): remove the staging copy and its tables, keeping the backups.
Ask in plain language: "Is my staging site up to date?" or "Push staging to live."
Long operations finish. Each call runs StageIt's steps for a while and hands back a resume token; your AI app keeps calling until the answer says done. The last part of a push or restore, while live's files and database are swapped, runs in one call that carries on even if your AI app stops waiting, and the status tells you afterwards how it ended.
The same safety checks as StageIt's command line. A push is refused when the staging copy is incomplete, an earlier run didn't finish, or backups are switched off. A remove, or a new build over an existing staging copy, is refused while that copy hasn't been pushed to live, because its work would be lost. One operation runs at a time, every operation is written to StageIt's audit log with the user who started it, and only StageIt's own backup folders can be restored.
Permissions. The AI can never do more than the Joomla account it acts for could do in StageIt. On top of MCP for J's Use and Write permissions, every tool needs StageIt's Access Administration Interface permission, and building, pushing, restoring and removing also need StageIt's Configure ACL & Options permission, which Super Users have, because they replace the whole site or the staging copy. Read-only mode in MCP for J limits it to the status tools.
Getting it. You need CS MCP for J and StageIt: 6.4.0 or later on Joomla 6, 5.8.0 or later on Joomla 5. Install it from Components → MCP for J → Browse MCP Add-ons or with the downloaded ZIP.
Tested on Joomla 6.1 with StageIt 6.6.4 and on Joomla 5.4 with StageIt 5.9.4: a build, a change on the staging copy, the safety checks, a push, a restore of the backup taken before it (on a database with linked tables) and a remove, each checked in the files, the database and the site's front end, and the permission checks run with Super User, Administrator and Manager accounts on every tool. The test sites were small; try a large site somewhere safe first.
Joomla 5 and 6, PHP 8.2+. GPL-2.0-or-later.
Current release: 1.1.1
Documentation: https://docs.cybersalt.com/extensions/mcp-for-stageit
Changelog: https://docs.cybersalt.com/extensions/mcp-for-stageit/changelog
MCP for StageIt
- Version:
- 1.1.1
- Developer:
- Cybersalt
- Last updated:
-
Nov 19 2026
14 hours ago - Date added:
- Nov 17 2026
- License:
- GPLv2 or later
- Type:
- Free download
- Includes:
- p e
- Compatibility:
- J5 J6
Share