Playbook · Agency

Run a client's whole brand from one Loopi account.

One account, one profile per client — and that profile is the wall between brands: separate domain, mail, socials, and credentials, nothing bleeding across. The client connects the two things only they can — their domain and their social logins — and your agent does the rest over MCP: email from their domain, a link-in-bio on their domain, an audit of their socials, and this week's posts drafted in their voice for your approval.

What it does for you

Running a client brand usually means a maze of logins, DNS tickets, and per-platform busywork — repeated for every client. This collapses it into one profile and one prompt per brand. When the play is done you'll have:

• One isolated profile per brand — separate lists, sending domain, link-in-bio, and social credentials. The profile is the permission boundary; nothing bleeds across clients.
• Email from their domain — a verified mail.theirbrand.com sender, a main list, a welcome sequence, and a signup form, all wired together.
• A link-in-bio on their domain — links.theirbrand.com, username claimed, starter links live.
• Their socials audited — best and worst posts, the format that wins, the best time to post — across every platform they've connected.
• You post on their behalf — tell your agent "schedule this week's posts" and it drafts them in the brand's voice; you approve with one click, then they go live.

The play

Create a profile for the brand, invite them to it, and let them connect the two things only they can — their domain and their socials. From there your agent runs the brand: it wires mail and link-in-bio, audits the socials, and drafts the posts.

1 · A profile per brand — the permission wall

In Loopi, a profile is a brand. It's not a folder — it's the boundary that separates everything: the brand's sending domain, its subscriber lists, its link-in-bio, and its social credentials all live inside one profile and never touch another. Create the client's profile yourself in Account → Profiles (profile creation is an account-owner action, not something the agent does over MCP), then point your agent at that one profile. Every channel the agent wires lands inside that wall.

2 · Invite the brand — they connect what's theirs

From the profile's settings, enter the client's email and hit Invite collaborator. Loopi sends them a link; when they accept, they get a seat scoped to their profile only — they can't see your other clients.

The invite exists because two steps require the account holder's own login, and no agent or agency can stand in for them:

• Their domain — the Website tab. The client enters theirbrand.com and points their domain at Loopi. Loopi mirrors their existing records first (so their live site and inbox keep working), then takes over the zone — which is what lets your agent stand up mail.theirbrand.com and links.theirbrand.com as children of that zone, with the DNS written automatically.
• Their socials — the Content tab. Platform OAuth (Instagram, TikTok, YouTube, LinkedIn, Bluesky) needs the client's own login. They connect their accounts; the tokens stay profile-scoped and never mingle with your other clients' credentials.

Here's the panel the client sees in the Content tab — they connect each account they want you to run, and disconnect anytime:

Send them Connect your social accounts with the invite — it's the client-facing walkthrough for the OAuth on each platform.

3 · Your agent wires mail and link-in-bio

Now the labor — and it's all your agent's, over MCP. It registers mail.theirbrand.com as the sending domain, builds the list, welcome, and signup form, then claims the link-in-bio and connects links.theirbrand.com. Because the client delegated their domain in step two, both subdomains are children of the zone Loopi manages — the agent writes their DNS records for you. If the client kept their domain elsewhere, the agent reports the exact SPF/DKIM/DMARC and CNAME records to paste instead. Either way you never chase a DNS ticket.

4 · Audit their socials, then draft their week

Once the brand's accounts are connected, the same agent reads their analytics — the last 90 days across every platform via content.listPostAnalytics — and tells you what's working: best and worst posts, the winning format, the best time to post. Then it drafts the week's content in the brand's voice and files it as pending review with content.bulkCreatePost, so nothing publishes until you approve. The deeper versions of these two steps live in their own playbooks — Audit your socials with Claude and Cross-post a video with Claude.

What Loopi handles for you

• The profile wall. Every client is its own profile with separate domains, lists, link-in-bio, and platform tokens. You point an agent at one profile and it physically cannot reach another client's data.
• The subdomain DNS. When the client's domain is delegated to Loopi, mail.theirbrand.com and links.theirbrand.com are provisioned with their records written into the managed zone — no copy-paste.
• The client's logins stay the client's. Platform OAuth and domain ownership are theirs; you operate the brand without ever holding their passwords.
• Approval before anything ships. Agent-drafted posts land in pending review. You approve and schedule; the client can be looped in to approve too. The agent drafts — it doesn't publish on its own.

How to do it with Loopi

First, a Loopi account — about 60 seconds. Then connect your agent to the client's profile over MCP. Two ways, same endpoint:

Claude Code (one command)

claude mcp add --transport http loopi https://api.loopi.social/mcp
# then, in your agent:
> connect to loopi mcp

Claude Desktop, Cursor, Gemini (JSON config)

Drop this into the app's MCP config (Claude Desktop: Settings → Developer → Edit Config):

{
  "mcpServers": {
    "loopi": {
      "type": "http",
      "url": "https://api.loopi.social/mcp"
    }
  }
}

Either way, you authorize once in the browser, and the agent is now pointed at the client's profile.

Then just ask — in plain language

This is the whole point. Once the profile is connected, you don't fill out forms or learn a dashboard — you tell your agent what you want, in plain English, and it makes the right Loopi calls under the hood. Each of these is a complete instruction on its own:

Help me set up a link in bio for this brand.

Help me set up a mailing list with a welcome message and a signup form.

Help me schedule posts for this week.

Run them one at a time, or string them together — "set up the link-in-bio, the mailing list, and this week's posts." The agent asks for anything it's missing and reports back what it built.

Wire this play up — connect Loopi to your AI agent →

Each step has its own playbook

Those plain-language asks each map to a deeper playbook. If you want the full walkthrough of any one channel — or to run a step by hand — here they are:

• Send email from the client's domain — the sending domain, DNS records, and the first test send.
• First list and welcome sequence — the list, the welcome, and the signup form, wired together.
• Claim the link-in-bio — username, custom domain, starter links, click tracking.
• Audit the socials with Claude — what's working, what's not, and what to do next.
• Cross-post a video with Claude — one video to TikTok, Reels, and Shorts from a single prompt.