Drive Donut from any MCP host.

Donut Browser speaks MCP through Remote MCP. Your desktop app keeps an outgoing connection to Donut cloud, an MCP client sends each call to https://api.donutbrowser.com/api/mcp, and your desktop answers it. Remote MCP is included in the Solo, Pro, Team and Enterprise plans. Free does not include MCP.

• Solo: MCP without browser automation: profiles, groups, proxies, VPNs, extensions and the human-in-the-loop tools.
• Pro, Team and Enterprise: also the browser automation tools and recipes.

The local MCP server has been removed

Earlier versions of the app ran an MCP server on your own machine, at http://127.0.0.1:51080/mcp/<token>. That server has been removed. A client that still points at the old local URL gets a 410 answer that says the server moved, and the app shows a notice.

When you sign in on a plan that includes remote MCP, the app offers to move those clients for you: it turns on remote control, creates a credential and points each client at the remote endpoint. Nothing else in the client’s settings changes. You can also start the move from Settings → Integrations.

Set it up

Follow Remote MCP: turn on remote control in Settings → Integrations → Remote MCP, create a credential, and point your client at the endpoint. The app can write the config for the clients it knows, such as Claude Desktop, Claude Code, Cursor, VS Code and Zed.

Tools

Your desktop exposes its tools over remote MCP: profiles, groups, proxies, VPNs, tags, fingerprints, extensions, and browser control (launch, navigate, click, type, scroll, screenshot, evaluate). A tool that your plan does not include answers with PLAN_REQUIRED and names the feature; nothing in your client breaks. On Solo, this applies to every tool that launches, drives or reads a browser.

Two more groups work with you. Your desktop answers ask_human, request_human_help, wait_for_human, get_human_updates and report_progress: with them an agent asks you a question, asks for your help in a profile, waits for you, reads the notes you send and reports its progress. You answer on the Agent page of the desktop app, which also shows what each connected agent is doing. The Donut API itself answers list_recipes, get_recipe, save_recipe, delete_recipe, run_recipe, get_recipe_run and cancel_recipe_run, which manage recipes: a flow recorded once, which an agent can repeat on other profiles without spending model tokens. Recipes need Pro, Team or Enterprise. On Solo, tools/list does not list the recipe tools, and a call answers RECIPES_NOT_ENTITLED.

Some tools stay in the app, because a remote caller must not read your disk or your stored secrets. add_extension, update_extension, detect_browser_profiles and import_browser_profiles read local paths, and export_proxies returns proxy passwords. Over MCP they answer TOOL_IS_LOCAL_ONLY; use the app or the REST API for them. list_proxies and get_proxy return their entries with passwords and VLESS URIs redacted.

See Pricing for what each plan includes.