MCP browser fleet

Give your AI agents a browser fleet

Give each agent its own browser profile — build it your way: with your AI, the API, or by hand. It keeps its logins, state, and personality across every run.

Quickstart commandcopy
curl -LsSf https://get.shade.atlas-ai.au/install | sh
With your AI over MCP
With the API REST
By hand in the console

One command installs it and signs you in with GitHub or Google — no API key to copy, no card. Your logins, fingerprint personality, and session state then persist across every agent run.

Fleet primitives

Built for agents that return to the same work.

Your agents come back to real browsers that are already logged in, with a visible console and a human who can step in without tearing down the run.

Build a profile your way

Each browser is a profile you set up three ways: with your AI over MCP, through the API, or by hand in the console. Logins are one thing it remembers — so agents come back to the same accounts instead of signing in again.

Save, load, and clone sessions

Agents can pause a logged-in workflow, resume it later, or clone a prepared browser state into another slot without starting from a blank browser.

Opt-in anti-detect personality

Fingerprint personality is opt-in and explicit. Shade does not promise bypass magic, CAPTCHA solving, or residential proxies.

IP, DNS, and WebRTC leak checks

Run a slot-level health check before giving an agent sensitive work. Surface mismatched egress, resolver, and WebRTC exposure early.

Live fleet console with takeover

See every running slot in one console, step into a session when an agent gets stuck, and hand control back without breaking the MCP connection.

Synthetic action view

The live fleet console reconstructs what agents are doing from structured events, so supervisors can track many slots without streaming every page tree through the model.

Live console

See what your agents are doing

The console shows you what happened in plain terms — clicks, navigations, downloads, takeovers — not raw page data.

Comparison

Why Shade.

Browserbase and Steel are strong browser clouds. Playwright-MCP is a strong local bridge. Shade is the one where you pay by usage with a free amount every day, and your browsers stay logged in as you.

CapabilityShadeBrowserbaseSteelPlaywright-MCP
How you payUsage-based, free amount every dayPaid browser-hoursPaid browser-hoursYour own machine
Build & configure a profileYour AI, the API, or by handReusable contextsReusable profilesYour local profile
Connects to agentsMCP, one connectionAPI + SDKAPI + SDKLocal, per client
Watch and take overLive console, step in anytimeRecordings + live viewSession embedsLocal only

Pricing teaser

Free every day, then pay for what you use.

Starter

Monthly credits + daily free amount

For one builder. Free credits every day, plus a monthly balance for bigger runs.

$29/mo
  • Free credits, refreshed daily
  • Browsers that stay logged in
  • Session save/load
  • Leak checks

Scale

High-volume monthly credits

For production agent fleets running many browsers at once.

$299/mo
  • Large monthly credit balance
  • Fleet console
  • Structured event stream
  • Priority onboarding

You pay for what you use, in credits. Free credits land every day — no card needed to start. Add a payment method when you want more.

MCP-native by default

Give every agent a browser that stays logged in.

Start free