Why this exists. Approval, email confirmation, generated passwords and the emails that carry them depend on settings spread across several screens. When one is off, the first you hear of it is a new member who can't get in. This add-on started with a Pending email whose confirmation link came out empty, which you can't see from the admin.

What the AI can do. 32 tools in 7 groups:

• Diagnostics (4): an overview with member counts, a health check, and a read-only table viewer.
• Configuration (3): the registration audit, reading settings, and changing named settings.
• Members (4): list and search, read a member with every field grouped by tab, set field values, and see the moderation queue.
• Moderation (5): approve or reject, confirm an email address, ban or unban, block or unblock, and read member reports.
• Fields (7): list, read, create, change and delete fields, see the field types, and set a field's options.
• Tabs (5): list, read, create, change and delete tabs.
• Community (4): connections, member lists, CB's plugins, and publishing or unpublishing one.

Every tool describes itself to the AI app, so there's nothing to configure. Ask in plain language: "Who's waiting for approval?" or "Add a Company field to the Contact Info tab."

The registration audit shows your Pending and Welcome emails as CB will send them, says which one goes out at each step, and flags what quietly breaks sign-up: a [CONFIRM] link that renders empty, confirmation switched on with no email to carry the link, or generated passwords that no email delivers.

Emails wait until you say so. Approving, rejecting, confirming, banning and unbanning all make CB email the member. Here, none of those goes out unless you ask, and each comes back in the response for you to read first. If CB's Generate Registration Passwords setting is on, approving replaces the member's password and only the email carries the new one, so the tools refuse to approve quietly.

Things it handles for you. Deleting a field deletes every member's answer, so the tool shows how many there are and needs a second confirmation. Writes go through CB's own code, so its events fire, and each write is read back and reported. New fields stay off the registration form unless you ask.

Permissions. The tools follow CB's own access rules for the account making each request. Working with members needs access to Joomla's Users manager, moderating also needs permission to change their state, and only a Super User can moderate a Super User. Fields, tabs, lists, plugins and diagnostics follow the matching parts of CB's admin. Read-only mode in MCP for J limits it to the reading tools. Member field values go through CB's own filter, as they do when a member saves the form.

What stays private. Passwords, CB's confirmation code, registration IP addresses, CB password fields, the settings of CB's plugins and the Joomlapolis key are never returned. Masked columns can't be used to filter or sort, and the session and private-message tables can't be read at all.

Getting it. You need CS MCP for J and Community Builder. Install it from Components → MCP for J → Browse MCP Add-ons or with the downloaded ZIP. It covers the free Community Builder core, not Joomlapolis's paid add-ons.

Tested on Joomla 6 with Community Builder 2.12.0: all 32 tools called with the writes checked in the database, and the permission checks with Super User, Administrator and Manager accounts.

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

Current release: 1.0.3
Documentation: https://docs.cybersalt.com/extensions/mcp-for-community-builder
Changelog: https://docs.cybersalt.com/extensions/mcp-for-community-builder/changelog