The private browser for AI agents

The app writes the MCP config for these 22 clients in one click

• Claude Code
• Claude Desktop
• Cursor
• Codex
• VS Code
• Zed
• Windsurf
• Gemini CLI
• GitHub Copilot CLI
• Cline
• Cline CLI
• Goose
• OpenCode
• Kilo Code
• Kiro CLI
• Kimi Code
• Grok Build
• Antigravity
• Mastra Code
• MCPorter
• Pi
• fx

{
  "mcpServers": {
    "donut-browser-remote": {
      "url": "https://api.donutbrowser.com/api/mcp",
      "headers": { "Authorization": "Bearer dmk_…" }
    }
  }
}

import { chromium } from "wayfern";

const res = await fetch(
  `http://127.0.0.1:10108/v1/profiles/${id}/run`,
  { method: "POST", headers: { Authorization: `Bearer ${token}` } },
);
const { remote_debugging_port } = await res.json();

const browser = await chromium.connectOverCDP(
  `http://127.0.0.1:${remote_debugging_port}`,
);

• Fingerprint in the engine

  Wayfern, Donut’s Chromium-based engine, sets each profile’s fingerprint in C++, under the page’s JavaScript. Fingerprint editing and other operating systems’ fingerprints are on Pro.

• A proxy or VPN per profile

  HTTP, HTTPS, SOCKS4, SOCKS5 or WireGuard. DNS goes through the same route, and WebRTC leak protection keeps the real IP out of the page.

• Timezone and language from the IP

  Both follow the proxy’s exit IP. If they do not match, Donut does not start the profile.

• Cookies of its own

  Each profile keeps its own cookies and storage. Import or export them as JSON, Netscape or Playwright storage state.

• Sales

  The task: Before each call, the agent reads the prospect’s website and your CRM record, then writes a one-page brief. It stops before anything is sent.

  Why its own profile: Each rep’s CRM and email stay signed in to that rep’s profile, on that rep’s IP address. No agent works in another rep’s session.

  AI agents for sales

• Recruiting

  The task: The agent reads new applicants in your ATS, opens each public portfolio and drafts a shortlist for you to check.

  Why its own profile: Candidate data stays in a profile on your disk. Donut stores none of it. Only your agent’s model provider sees what the agent reads.

• Operations

  The task: Once a month, the agent signs in to each vendor portal, downloads the invoices and lists the renewals due in 30 days.

  Why its own profile: One profile per portal keeps the same login, device and IP every month, so each portal sees a returning user.

• Research

  The task: The agent runs the same search from three countries, saves every source and builds an evidence table with links.

  Why its own profile: Each profile has its own exit IP, timezone and language, so each search runs as a local reader’s would.

• Developers

  The task: Your code starts profiles from the local API and connects Playwright over CDP. Your agent reaches the same profiles over remote MCP.

  Why its own profile: The debug port listens on 127.0.0.1, so the local path stays on your computer.

  Automation with Playwright