If you build or run membership sites for clients, you can connect as many of them as you need to one Membership MCP account and work on all of them from the AI you already use. This page covers setting that up, keeping sites apart, and what your clients see.

Connect each site once

Every site gets the plugin and its own connection:

  1. On each client site, install Membership MCP from MemberPress → Add-ons (type MCP in the Search add-ons box, then click Install Add-on), or the plugin zip, and click Connect, as in Connect your site.
  2. Sign in with the same email each time, so every site lands in your one account.
  3. Add each site to your AI app as its own connector, with that site’s own MCP URL. Your account shows it on that site’s card: open Connect this site on its own and use the Copy button. It works only for that site.

You need an administrator login on each site to connect it. Your account page at app.membershipmcp.ai lists every site you’ve connected.

One connection per site

Each connection reaches only its own site. With more than one site connected, switch on the connection for the site you’re working on before you ask.

Name each connector after its site (“Membership MCP: example-studio.example”) so you can tell them apart and switch on only the one you’re working on. Free Claude accounts can add only one custom connector, so agencies on Claude usually need a paid Claude plan.

Cursor suits agency work well: put the connection in a project’s .cursor/mcp.json and it sits beside that client’s code.

Who sees what

  • Your client sees every action in the Activity log on their own site, the same as if they’d made the connection themselves.
  • Actions run as the administrator who connected the site. Connect with an admin account that belongs to you or your agency, not the client’s personal login, so the log shows clearly who acted.
  • Each site is separate. Nothing your AI reads on one site is written to another unless you ask it to move something across.
  • The client stays in control. Any administrator on the site can pause changes or disconnect at any time, and that cuts off access straight away.

Approvals on client sites

Changes show a preview by default. Riskier ones, such as refunds, cancellations and anything that goes live, always stop at a preview and wait for your approval in your AI app. There’s no approval queue in WordPress, so the person chatting with the AI is the one approving.

If a client wants to sign off on changes themselves, agree on a routine: save plans, rules and posts as drafts, then publish only after the client has looked. Asking “set this up as a draft” does that. For sites where you should only look, use a read-only connection.

Plans for agencies

Your plan sets how many actions you get each day, and that one allowance is shared across every site on your account. Power gives you 1,000 a day, built for busy sites and agencies. If you run many clients, start on Power and check your usage on your account page in the first week.

Separate allowances or billing per client aren’t available yet. If you bill clients for this work, track it outside Membership MCP for now.

Handing a site back

When a client leaves, disconnect their site from its Membership MCP screen, then remove that site’s connector from your AI app. The client keeps the plugin and can connect their own account if they want to. See Remove a site.