This is for JComment (com_jcomment, no "s"). The free JComments has its own free add-on, MCP for JComments. Neither add-on works with the other's extension.

Why this exists. Looking after comments is mostly small, repeated jobs: see what's waiting, read a comment in its thread, approve the good ones, clear the spam, work out why nobody is getting notified. Ask in plain language instead: "Check my JComment setup" or "Show me the comments waiting for approval and score them for spam."

What the AI can do. 15 tools in 6 groups:

• Reading (2): list comments by state, item, author, IP address, date or text, or read one comment with its whole thread, reports and author history.
• Replying (1): post a reply as the account, threaded the way JComment threads replies. An identical reply to the same comment is refused, so a retry can't post twice.
• Moderation (2): approve or unpublish comments, and delete them with a dry run first.
• Spam (2): score comments with every rule that fired, and mark spam by unpublishing or deleting it, optionally blacklisting the author as JComment's Ban button does.
• Lists (5): commented items with pending counts, reader reports, subscriptions, the blacklist and the mail queue. All read-only.
• Diagnostics (3): the health check, JComment's settings with group names, and a read-only look at JComment's own tables.

Nothing emails anyone unless you ask. JComment's own admin Publish button emails every subscriber of the item. Here, approving, replying, unpublishing, deleting and banning send nothing by default. Ask for notifications and the tool runs JComment's own notification, for at most 20 comments in one call.

Spam scores decide nothing. They sort comments for review, and each flag says which rule fired and why. No rule looks at the language or script of the text.

The health check reports problems that are easy to miss: reporting that's off although the Settings screen shows it on, a fresh install that gives nobody a Reply button, an empty From email or From name that stops all mail, and what deleting a Joomla user would do to their comments.

Permissions. The AI can never do more than the Joomla account it acts for could do in JComment. Each tool needs MCP for J's Use or Write permission and JComment's Access Administration Interface permission. Approving also needs Edit State, deleting needs Delete, banning needs Create, and replying follows JComment's own can comment and can reply lists. Read-only mode in MCP for J limits it to the reading tools.

What stays private. Unsubscribe hashes, the bodies of queued emails (which carry moderation links) and the updater registration email are never shown.

Getting it. You need CS MCP for J and JComment, purchased from Joomla! Extensions Store. MCP for JComment is a yearly subscription from Cybersalt, or part of MCP for J Pro All Access. Once your Cybersalt account is linked in MCP for J's dashboard, install it from Components → MCP for J → Browse MCP Add-ons. Your subscription covers downloads and updates; the add-on keeps working on your site without it.

Tested on Joomla 6.1 with PHP 8.4 and JComment 2.0: all 15 tools called as a Super User and as a Manager, with comments posted through JComment's own front-end form and every change checked in the database. Joomla 5 and guest posting haven't been tested yet.

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

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