Why this exists. After a Joomla update, the template manager can report "X Changes found", and each one has to be read against the core file that changed. Override Checker's copy-paste prompt needs an AI that can call your site's REST API, which browser chats can't do. Through MCP for J, an AI app reviews and fixes overrides with its own tools, with no copy-paste step and no browser timeout. Ask: "Review the template overrides Joomla flagged."

What the AI can do. 12 tools in 4 groups:

• Status (1): versions, flagged overrides per template, backup and review counts, and what this account may do.
• Flagged overrides (5): list them, read the override, read the core file, apply a fix, and dismiss a row.
• Backups (3): list them (with whether the live file still matches), read one, and restore one.
• Reviews (3): list saved reviews, read one with the fixes filed under it, and save a new one.

How a fix is written. Your AI reads the whole file, builds the complete new version, and sends it with the checksum of the file it read. Override Checker backs up the current file and writes the new one, and the tool checks the result on disk. If the file changed since it was read, nothing is written. A .php file that doesn't parse is refused, because a broken layout breaks every page that uses it.

What a fix can't add. Your AI reads files from your site, and a hacked file can contain text written to trick it. So Override Checker refuses a fix that adds eval, shell commands, decoding functions, reading or writing files, outbound connections, a new or changed include, variable function calls or superglobals. Code the file already has can stay. Your AI can't turn this off. It reads PHP only, and enough indirection can get past any list, so it's a safety net: keep reading what your AI proposes.

Undoing a fix. Every fix and restore takes a backup first. Fixing an infected override stores the backdoor as that fix's backup, so a backup holding code a fix couldn't add is refused through MCP. You can still restore it yourself from Override Checker's File backups screen.

Permissions. The AI can never do more than the Joomla account it acts for could do in Override Checker. Reading needs MCP for J's Use permission and Override Checker's View permission. Fixing, dismissing, restoring and saving a review need Write in both. Writing a fix writes a PHP file that your site runs, so give Write only to people you'd trust with that. Read-only mode in MCP for J limits it to the reading tools.

Getting it. You need CS MCP for J and Override Checker 2.6.1 or later. Install it from Components → MCP for J → Browse MCP Add-ons or with the downloaded ZIP.

Tested on Joomla 6 on a test site with real flagged overrides: all 12 tools, the refusals, the alternative-layout cases, and an account with only View permission. The fix and restore tools were run again against the released Override Checker 2.6.1. It was tested over MCP's own connection, not from inside each browser chat, and Joomla 5 hasn't been tested yet.

Joomla 6, PHP 8.3+. GPL-2.0-or-later.

Current release: 1.0.0
Documentation: https://docs.cybersalt.com/extensions/mcp-for-override-checker
Changelog: https://docs.cybersalt.com/extensions/mcp-for-override-checker/changelog