Guide · Mimic + Puppeteer

Puppeteer + Multilogin X

Same ops spine as Playwright: authenticate, ask the local Launcher to start a profile with automation_type=puppeteer, then attach puppeteer-core to the port Multilogin returns. Most teams should still prefer Playwright; use Puppeteer when the desk’s libraries already assume it.

Plan gate: Free has no API — need Pro or higher (pricing). Playwright/Puppeteer attach to Mimic cores; Multilogin’s docs say Stealthfox + Playwright is not available yet (assume the same constraint for Puppeteer until their examples say otherwise).

Source of truth

Mode A vs Mode B

Flow

1. POST https://api.multilogin.com/user/signin
   body: { "email": "...", "password": "<md5 hex of password>" }
   → data.token (~30 min)

2. GET https://launcher.mlx.yt:45001/api/v2/profile/f/{folder_id}/p/{profile_id}/start
     ?automation_type=puppeteer&headless_mode=false
   Authorization: Bearer {token}
   → data.port

3. puppeteer.connect({ browserURL: `http://127.0.0.1:${port}`, defaultViewport: null })

4. Use an existing page — do not launch a naked Chromium

5. Stop the profile via Launcher when the job ends

Minimal connect snippet

import puppeteer from "puppeteer-core";

const browser = await puppeteer.connect({
  browserURL: `http://127.0.0.1:${portFromLauncher}`,
  defaultViewport: null,
});
const pages = await browser.pages();
const page = pages[0] || await browser.newPage();
await page.goto("https://example.com");

When connect fails

Ops for ads / MMO desks

Automate reporting and QA. Keep humans on policy-sensitive clicks. Isolation: Facebook ads · Google ads · multi-account ads.

Need Multilogin first? Browser → SAAS50. Cloud Android → MIN50. Affiliate desk — not Multilogin Support.

Get codes on Telegram Puppeteer kit Prefer Playwright