Getting started

Lightpanda Cloud runs the browser for you. With no process to install or keep alive, an API token is all you need to drive it over CDP, MCP, or the HTTP API.

Create an account and token

⚠️

Your token is shown once, when you generate it. Save it somewhere safe. If you lose it, generate a new one from the console.

Connect your CDP client to Lightpanda Cloud

To generate a ready-to-use snippet, you can use the script generator in the console.

Connect to the region nearest your script. The snippets below all use euwest:

wss://euwest.cloud.lightpanda.io/ws (west Europe)
wss://uswest.cloud.lightpanda.io/ws (west US)

CDP URL

The raw endpoint every CDP client connects to:


wss://euwest.cloud.lightpanda.io/ws?token=YOUR_TOKEN&browser=lightpanda

Puppeteer

We recommend storing your token in an environment variable rather than hard-coding it in your script:


export LPD_TOKEN="your token here"

Then connect Puppeteer:


import puppeteer from 'puppeteer-core';
 
const browser = await puppeteer.connect({
  browserWSEndpoint: `wss://euwest.cloud.lightpanda.io/ws?token=${process.env.LPD_TOKEN}`,
});

See the Puppeteer page for a complete script.

Playwright

We recommend storing your token in an environment variable rather than hard-coding it in your script:


export LPD_TOKEN="your token here"

Then connect Playwright:


import { chromium } from 'playwright-core';
 
const browser = await chromium.connectOverCDP(
  `wss://euwest.cloud.lightpanda.io/ws?token=${process.env.LPD_TOKEN}`,
);

See the Playwright page for a complete script.

Chromedp

We recommend storing your token in an environment variable rather than hard-coding it in your script:


export LPD_TOKEN="your token here"

Then connect Chromedp:


ctx, cancel := chromedp.NewRemoteAllocator(context.Background(),
    "wss://euwest.cloud.lightpanda.io/ws?token="+os.Getenv("LPD_TOKEN"), chromedp.NoModifyURL,
)
defer cancel()

See the Chromedp page for a complete script.

For troubleshooting, your recent sessions and their logs are on the sessions page in the console.

Connection options

The cloud serves Lightpanda by default. For debugging, append browser=chrome to run Google Chrome instead, since Chrome isn’t intended for production traffic. Append browser=lightpanda to force Lightpanda explicitly.

The same URL takes a proxy parameter to route the session through a shared proxy, or through one you added on the proxies page in the console.

Other features: playground, HTTP API and MCP

The cloud also exposes:

a playground to write and run a script from the console, with no local setup at all.
an HTTP API to fetch a page’s HTML or Markdown in a single request, with no CDP script.
an MCP server to drive the browser from AI applications over the Model Context Protocol.