@prefix sioc: <http://rdfs.org/sioc/ns#> .
@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix content: <http://purl.org/rss/1.0/modules/content/> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .

<https://lhero.org/?post_type=lh-portfolio&#038;p=153110>
  a sioc:Post ;
  dc:title "LH MCP BuddyPress Actions" ;
  dcterms:identifier 153110 ;
  dc:modified "2026-11-01T22:12:36Z"^^xsd:dateTime ;
  dc:created "2026-11-01T22:07:34Z"^^xsd:dateTime ;
  sioc:link <https://lhero.org/portfolio/lh-mcp-buddypress-actions/> ;
  sioc:has_creator <https://lhero.org/author/1/#account> ;
  sioc:has_container <https://lhero.org/#posts> ;
  content:encoded """<ul class="lh_portfolio-meta"><li><strong>Type:</strong> Plugin</li><li><strong>Lifecycle Stage:</strong> Active</li></ul>
<p class="wp-block-paragraph">MCP abilities that change BuddyPress group membership, so an AI assistant can add people to a group, remove or ban them, and promote or demote them, without anyone opening wp-admin. It is the write-side companion to <a href="/portfolio/lh-mcp-buddypress-queries/">LH MCP BuddyPress Queries</a>, which stays read-only.</p>



<p class="wp-block-paragraph">No admin UI and no front-end output: abilities only. Network-activate it on a multisite network; it requires BuddyPress with the Groups component.</p>



<h2 class="wp-block-heading">Key features</h2>



<ul class="wp-block-list">

<li>Add, remove or ban up to 100 users in one call, and set their group role (member, mod or admin)</li>


<li>Everything goes through BuddyPress&#8217;s own functions, so notifications, activity and other plugins&#8217; group hooks behave as they would in the browser</li>


<li>A pending membership request or invitation is accepted rather than duplicated</li>


<li>Dry run by default, with a status for every user, so the effect can be checked before anything changes</li>


<li>A group is never left without an admin</li>


<li>Site rules come first: a site&#8217;s own plugins can refuse any change through a filter, and only approved members of the site can be added</li>


<li>An optional note explaining each change is recorded in LH Audit Trail</li>

</ul>



<h2 class="wp-block-heading">Who can use it</h2>



<p class="wp-block-paragraph">Site moderators (BuddyPress&#8217;s <code>bp_moderate</code>) can manage any group, and a group&#8217;s admins can manage their own group, so a team captain can look after their team. Network administrators are not held to the site rules.</p>


<ul class="lh_portfolio-doc-toc"><li><a href="https://lhero.org/portfolio/lh-mcp-buddypress-actions/mcp-abilities/">MCP abilities</a></li><li><a href="https://lhero.org/portfolio/lh-mcp-buddypress-actions/notes/">Notes</a></li><li><a href="https://lhero.org/portfolio/lh-mcp-buddypress-actions/changelog/">Changelog</a></li></ul>"""^^rdf:XMLLiteral ;
  sioc:content """Type: PluginLifecycle Stage: Active
MCP abilities that change BuddyPress group membership, so an AI assistant can add people to a group, remove or ban them, and promote or demote them, without anyone opening wp-admin. It is the write-side companion to LH MCP BuddyPress Queries, which stays read-only.



No admin UI and no front-end output: abilities only. Network-activate it on a multisite network; it requires BuddyPress with the Groups component.



Key features





Add, remove or ban up to 100 users in one call, and set their group role (member, mod or admin)


Everything goes through BuddyPress&#8217;s own functions, so notifications, activity and other plugins&#8217; group hooks behave as they would in the browser


A pending membership request or invitation is accepted rather than duplicated


Dry run by default, with a status for every user, so the effect can be checked before anything changes


A group is never left without an admin


Site rules come first: a site&#8217;s own plugins can refuse any change through a filter, and only approved members of the site can be added


An optional note explaining each change is recorded in LH Audit Trail





Who can use it



Site moderators (BuddyPress&#8217;s bp_moderate) can manage any group, and a group&#8217;s admins can manage their own group, so a team captain can look after their team. Network administrators are not held to the site rules.


MCP abilitiesNotesChangelog""" ;
  sioc:topic <https://lhero.org/lh_portfolio-type/plugin/>, <https://lhero.org/lh_portfolio-lifecycle-stage/active/>, <https://lhero.org/?taxonomy=lh_portfolio-tags&term=mcp>, <https://lhero.org/?taxonomy=lh_portfolio-tags&term=buddypress>, <https://lhero.org/?taxonomy=lh_portfolio-tags&term=groups>, <https://lhero.org/?taxonomy=lh_portfolio-tags&term=membership>, <https://lhero.org/?taxonomy=author&term=cap-1> .

<https://lhero.org/author/1/#account> rdfs:seeAlso <https://lhero.org/author/1/?feed=lhrdf&format=turtle> .
<https://lhero.org/lh_portfolio-type/plugin/> rdfs:seeAlso <https://lhero.org/lh_portfolio-type/plugin/?feed=lhrdf&format=turtle> .
<https://lhero.org/lh_portfolio-lifecycle-stage/active/> rdfs:seeAlso <https://lhero.org/lh_portfolio-lifecycle-stage/active/?feed=lhrdf&format=turtle> .
<https://lhero.org/?taxonomy=lh_portfolio-tags&term=mcp> rdfs:seeAlso <https://lhero.org/?taxonomy=lh_portfolio-tags&term=mcp&feed=lhrdf&format=turtle> .
<https://lhero.org/?taxonomy=lh_portfolio-tags&term=buddypress> rdfs:seeAlso <https://lhero.org/?taxonomy=lh_portfolio-tags&term=buddypress&feed=lhrdf&format=turtle> .
<https://lhero.org/?taxonomy=lh_portfolio-tags&term=groups> rdfs:seeAlso <https://lhero.org/?taxonomy=lh_portfolio-tags&term=groups&feed=lhrdf&format=turtle> .
<https://lhero.org/?taxonomy=lh_portfolio-tags&term=membership> rdfs:seeAlso <https://lhero.org/?taxonomy=lh_portfolio-tags&term=membership&feed=lhrdf&format=turtle> .
<https://lhero.org/?taxonomy=author&term=cap-1> rdfs:seeAlso <https://lhero.org/?taxonomy=author&term=cap-1&feed=lhrdf&format=turtle> .