Why this exists. Keeping a download library tidy is mostly small, fiddly jobs: add a new version, move a file to the right category, find the downloads whose files have gone missing, work out which group can download what. Each one is a few screens in the admin. A jDownloads user asked for this add-on, and it answers from jDownloads' own tables and folders.

What the AI can do. 17 tools in 5 groups:

• Categories (4): list, read, create and change, including renaming or moving a category, folder and all.
• Downloads (6): list, read, create, change, publish or unpublish, and delete.
• Files (2): attach a file that's already in the upload folder, and list the files no download uses.
• Lookups (3): licences, download and upload limits per user group, and each group's effective permissions.
• Diagnostics (2): the health check and a read-only table viewer.

Every tool describes itself to the AI app, so there's nothing to configure. Ask in plain language: "Check my jDownloads setup" or "Move the Archive category under Old Releases."

The health check lists downloads whose files are missing, files no download uses, folders with no category, and whether your upload folder can be reached directly from the web. jDownloads' default upload folder can be, and a file fetched that way skips access levels and the counter.

Every category is also a folder. A rename or move checks the disk before anything is written, moves the folder in one step, and checks the database against the disk afterwards.

Edits keep what you didn't send. jDownloads' own admin save can't be used outside its form: there it blanks some fields, deletes screenshots and resets permissions. So downloads are written through its table, one field at a time, and tags, custom field values, permission rules, checksums, screenshots and the counter stay as they were. Nothing here sends an email.

Careful with files. Files are attached from inside the upload folder only: no .., no symbolic links, no type jDownloads' settings block, and never a type the server could run. jDownloads has no trash, so a download has to be unpublished before it can be deleted, deleting needs a confirmation, and the file stays unless you ask for it to go.

Permissions. The AI can never do more than the Joomla account it acts for could do in jDownloads. On top of MCP for J's Use and Write permissions, every tool needs jDownloads' Access Administration Interface permission, and each change checks the permission it needs on that category or download: Create, Edit, Edit Own, Edit State or Delete. Reading the permission matrix needs Configure ACL & Options. Joomla's text filters apply to descriptions as they do in jDownloads' own form. Read-only mode in MCP for J limits it to the reading tools.

What stays private. Category and download passwords and visitor IP addresses are never returned, and they can't be used to filter or sort.

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

Tested on Joomla 5.4 and 6.1 with jDownloads 4.1.7: all 17 tools called with the writes checked in the database and on disk, and the permission checks with Super User, Administrator and Manager accounts on every tool. Multilingual sites and jDownloads' manual folder mode haven't been tested yet.

Joomla 5 and 6, PHP 8.2+. GPL-2.0-or-later.

Current release: 1.0.1
Documentation: https://docs.cybersalt.com/extensions/mcp-for-jdownloads
Changelog: https://docs.cybersalt.com/extensions/mcp-for-jdownloads/changelog