Donut Browser
Donut
Get Started
Documentation

Drive Donut from code.

View as Markdown

The desktop app runs a local REST API on your machine, and AI agents reach it over remote MCP. Everything Donut does in the UI (profiles, proxies, VPNs, launches) is available programmatically. The REST API is free for everyone; the browser-launch and manipulation surface is Pro. Remote MCP starts with Solo, and its browser tools need Pro, Team or Enterprise.

Get started

  • Quickstart: where the local API lives, ports, base path, and the first curl.
  • Import profiles: migrate from Chrome, Chromium, or Brave in bulk — folders, ZIP archives, groups, proxy assignment.

REST API

  • API reference: every endpoint across profiles, groups, tags, proxies, vpns, browsers. Worked examples.
  • Authentication: bearer token from Settings → Integrations → Local API. Where to find it and how to rotate it.
  • Wayfern · Playwright: humanized Playwright wrapper with fingerprint control. Drop-in and CDP-attach modes.

Other surfaces

  • MCP: drive Donut from Claude, Cursor, or any MCP host. MCP is remote only: the local MCP server has been removed.
  • Remote MCP: connect any MCP client to your own desktop through the Donut API. Config snippet included. Solo and up; browser tools from Pro.

Reference

  • OpenAPI spec: machine-readable spec, codegen recipes (TypeScript, Python, Rust).