Lock Members-Only Content in MemberPress with AI
Tell the AI which pages, posts, or categories are for members and which memberships unlock them, and get access rules created, drip-scheduled if you want, and checked logged out.
Prerequisites
A connected site running MemberPress with the Developer Tools add-on active, at least one membership, and the content you want to protect. The faster single-page path requires MemberPress AI Foundation 1.5.3 or newer with Allow connected apps to make changes turned on (MemberPress AI → MCP Settings).
I use MemberPress on my WordPress site. Make [the pages, posts, or categories to protect, for example: the Library and Templates pages, and every post in the Premium category] members-only for [membership names]. [Optional: release it [N] days after someone joins.] First list my memberships and my existing access rules with the MemberPress abilities so you have the right IDs and don't create a rule that overlaps one I already have. Show me each rule you plan to create, with the content it covers, the memberships that unlock it, and any drip delay, and wait for my yes. Rules go live the moment they are created. For a single page or post, use the MemberPress create-rule ability when it is available and allowed to make changes (it requires MemberPress AI Foundation 1.5.3 or newer with Allow connected apps to make changes turned on (MemberPress AI → MCP Settings)): rule_type single_page or single_post, content_id set to the page or post ID, membership_ids set to the membership IDs, drip_enabled, drip_amount, and drip_unit if I asked for a delay, and dry_run set to false. Rules created this way are enforced right away, with no cache step. For categories and tags, or if create-rule is missing or refuses to make changes, use the MemberPress Developer Tools REST API (mp/v1/rules) instead, with rule_type set to single_page, single_post, category, tag, or all_pages, rule_content set to the page, post, or term ID, authorized_memberships set to the membership IDs, and drip_enabled, drip_amount, and drip_unit if I asked for a delay. After the last of those rules is in, clear the MemberPress rule cache with the WP-CLI command transient delete mepr_all_models_for_class_meprrule, because rules created through the REST API are not enforced until it is cleared. Read each rule back right after creating it. If its rule type or the content it protects is not what you intended, delete that rule immediately and tell me. Then load each protected page logged out and confirm the content is hidden. Give me the list of protected URLs with the result for each.
Skip pasting the full prompt. Drop this into your AI on a site that already has WPVibe:
Run the “Lock Members-Only Content in MemberPress with AI” recipe from the WPVibe cookbook on my connected site.
The content is written and the memberships exist, but none of it is actually locked yet. Every page, post, and category needs an access rule that says which memberships can see it, and the rules screen asks you to pick the content type, find the item, and tick the memberships for each one. Miss one and your paid content is free to anyone who finds the link.
You tell the AI what should be members-only and which memberships unlock it, including a drip delay if content should open a few days after someone joins. It looks up the right IDs, shows you each rule before creating anything, and waits for your yes. For a single page or post it uses MemberPress's own create-rule ability, which enforces the rule right away. That path requires MemberPress AI Foundation 1.5.3 or newer with Allow connected apps to make changes turned on (MemberPress AI → MCP Settings). For categories, tags, and older versions it creates the rule through MemberPress's REST API and then refreshes the rule cache, which otherwise keeps a new rule from taking effect. Either way, it loads each page logged out to prove the content is really hidden.
Paste the prompt with your content and memberships. Rules take effect as soon as they are created, so review the plan carefully before you approve it. The AI checks each saved rule and deletes any that did not save with the type it intended, because a rule with the wrong type can end up covering far more of your site than you meant.
Outcome
Your members-only content is covered by MemberPress access rules for the right memberships, with any drip delay set, and each page is confirmed hidden to logged-out visitors.