When to use it

At the end of a month, before a pricing decision, or any time you want to know whether the membership is growing. Revenue tells you what came in. Churn tells you who left. You want both side by side, per plan.

Before you start

  • A connected MemberPress site (start here).
  • At least a few weeks of payments. On a brand-new site the numbers will mostly be zeros.

What your AI does

  1. Pulls revenue for the last 90 days, grouped by month, with totals and the average payment (memberpress_get_revenue_report).
  2. Lists your plans (memberpress_list_memberships), then pulls churn for the same 90 days for each one (memberpress_get_churn_report).
  3. Checks what “churn rate” means in that report before quoting it: subscriptions that ended in the period, divided by the ones active when it started (memberpress_describe_metric).
  4. Puts it in one table and writes the one-sentence callout. The analysis is done by your own AI. Membership MCP sends it the numbers, nothing more.

What you get back

For a site like example-studio.example, you get back something like:

MonthRevenuePayments
August$6,840214
September$7,120221
October$7,415229
PlanActive at startEndedChurn rate
Monthly1682112.5%
Annual6123.3%

Revenue rose each month, but Monthly lost one member in eight over the period while Annual barely moved: the biggest change is Monthly churn.

What it changes

Nothing. Every tool in this playbook only reads, so it works on a read-only connection too. The calls still appear in the activity log on your site.

Variations

  • A different window: “Revenue by week for the last 30 days, and churn for the same 30 days.”
  • One plan only: “Revenue and churn for the Annual plan since January 1.”
  • By signup month: “Group members by the month they joined over the last year, and show how many of each group are still paying.”
  • Lifetime value: “What is a member worth on average on each plan, from first payment to cancellation?”