Every client's membership site, from the chat you already work in.

One connection per client site, one account. Your AI does the member lookups, new plans and monthly reports, and every action is logged on the client's site.

One sitting, one client site

Here's what one hour on a client's membership looks like.

1

The monthly report

Revenue by plan, new members, churn and refunds for October, in a table you paste into the client update.

2

Failed payments chased

The four members whose cards failed this week, each with a card-update note written and ready to send.

3

A coupon for their webinar

WEBINAR20, 20% off the first payment, 100 uses, expiring the night of the event.

4

A new plan, previewed before it exists

Studio Annual at $390, shown to you in the chat, and put on sale on the client's site only after your approval in your AI app (once your client signs off).

5

What was logged

Every action, what it touched and whether it was confirmed, in the activity log on that site.


The work it takes off your plate

Monthly reporting

The numbers every client wants, pulled and formatted in one ask.

Member support triage

Who is this, what did they pay for, why can they not see it, and the drafted reply.

Launches and promotions

New plans, coupons and access rules, each previewed before it is created.

Pre-launch audits

Access rules audited for gaps and overlaps before the announcement goes.


Many sites, one connection.

Connect each client site once, then switch on that site’s connection and ask.

  • Logged on that site, under the user you connected as.
  • Previews before changes, and read-only connections for sites where you only report.
  • Connect as many sites as you need on any plan.

On Example Yoga Studio, who is on the Studio plan?

23 members on Studio at example-studio.example, 19 active and 4 in trial. Want the list, or the same for Northside Pilates?


What agencies ask

Is it safe on client sites?

Reads never change anything. Changes show a preview by default, refunds, cancellations and anything that goes live wait for your approval in your AI app, and every action is logged on the client's site. The connection starts from the plugin on that site and can be ended there. Security.

What do you see and store?

Your account email, your plan, the sites you connected and an encrypted credential for each. We log which tool ran, whether it worked and which AI app sent it, never what was in the call. We never hold a WordPress password or your AI provider's keys. What we hold.

Will my clients see Membership MCP?

Yes. It is a plugin in their WordPress admin, under MemberPress › MCP, with an activity log of every call your AI made on their site. Their members never see it.

Can each person on my team have a login?

Not yet. An account belongs to one email address today. Each site still logs every call, so you can see what was done and when.

How many sites can I connect?

As many as you need, on any plan.

Which plan should an agency pick?

Power: 1,000 actions a day across all your sites. Compare plans.

Are there per-client allowances?

Not yet. The daily allowance is shared across every site on the account.

Can the client's own AI use it too?

Yes. The client signs in with their own Membership MCP account and connects the AI they use. Each account has its own daily allowance, and every call from either of you shows in the site's activity log.


Every tool on every plan. Plans only raise the daily volume. Power is $49 a month for 1,000 actions a day.

Compare plans

Start with a site you own.

Connect one site, try the asks, then bring the clients.

Connect once, on your own site. Then just ask.