MCP for Akeeba Backup
Introduction
MCP for Akeeba Backup 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) 7 tools for Akeeba Backup, Core or Pro: read the backup profiles, see which backups exist and where their archives are, take a new backup, and delete old ones.
Why this exists. The moment you most want a fresh backup is just before you change something, and that's when stopping to take one is easiest to skip. With this add-on, "take a backup before we update Joomla" is something you ask for in the same conversation. The backup runs through Akeeba's own engine with the profile's own settings, so it's the same backup you'd have taken from Akeeba's backup page.
What the AI can do. 7 tools in 4 groups:
- Profiles (2): list the backup profiles, and read one, with its settings for accounts allowed to see them.
- Backup records (2): list backups newest first, with where each archive is (on this server, in remote storage, or neither) and whether it can be restored, and read one record. The list names the newest good backup, so "when did this site last back up?" has a straight answer.
- Taking a backup (2): start a backup with a profile, then move it on step by step until Akeeba says it's done, the way Akeeba's own backup page does, so a backup of any size finishes without hitting a time limit.
- Deleting (1): delete a backup, or only its archive when you've copied it somewhere else. Frozen backups are left alone.
Every tool describes itself to the AI app, so there's nothing to configure. Ask in plain language: "Back the site up now" or "Which of my backups can I restore from?"
Backups in remote storage count. When a profile uploads each archive to Google Drive, S3, Dropbox or the like and removes the local copy, Akeeba marks the record as having no files, even though the backup is good. These tools say where each archive is kept, so a good backup in the cloud isn't read as missing.
Passwords and keys stay hidden. A profile's settings can hold the archive password, remote storage passwords and keys, OAuth tokens and, in Pro's Multiple Databases feature, database passwords. They're shown only to accounts with Akeeba's Configure permission, and every password, key and token is masked unless a Super User asks to see it.
Permissions. The AI can never do more than the Joomla account it acts for could do in Akeeba Backup itself. On top of MCP for J's Use and Write permissions, every tool needs Access Administration Interface on Akeeba Backup; taking a backup needs Backup, deleting needs Download, and a profile's settings need Configure, the same rules as Akeeba's own screens. Profiles at an access level the account doesn't have are left out. Read-only mode in MCP for J limits it to the reading tools.
Getting it. You need CS MCP for J and Akeeba Backup 10, Core or Pro. Install it from Components → MCP for J → Browse MCP Add-ons or with the downloaded ZIP. Restore isn't one of the tools: it runs through Akeeba's own restore tools.
Tested on Joomla 5.4 and 6.1 with Akeeba Backup Core 10.5.0 and Pro 10.5.0: on each, a full backup taken through the tools and checked on disk, the masking checked against a profile holding eight kinds of secret, deletes checked on disk and in the database, and the permission checks run with Super User, Administrator and Manager accounts on every tool. Uploads to remote storage weren't part of this test.
Joomla 5 and 6, PHP 8.2+. GPL-2.0-or-later. Not made or endorsed by Akeeba Ltd.
Current release: 1.0.6
Documentation: https://docs.cybersalt.com/extensions/mcp-for-akeeba-backup
Changelog: https://docs.cybersalt.com/extensions/mcp-for-akeeba-backup/changelog
MCP for Akeeba Backup
- Version:
- 1.0.6
- Developer:
- Cybersalt
- Last updated:
-
Nov 20 2026
8 hours ago - Date added:
- Nov 20 2026
- License:
- GPLv2 or later
- Type:
- Free download
- Includes:
- p e
- Compatibility:
- J5 J6
Share