Browser Use MCP server
8 operations0 webhooks
Stealth cloud browsers you drive over CDP with Playwright or Puppeteer, plus hosted browser agent runs, behind one API key.
Try Browser Use with your agent
Connect Browser Use, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in Browser Use on my account, then run one read-only example and show me the result.
Browser Use tools and triggers
Tools are what your agent can do in Browser Use through Corsair's MCP server. Triggers are the Browser Use events a routine can start from.
Browsers
- CreateWrite
POST /browsers — start a cloud browser; returns cdpUrl for Playwright/Puppeteer and a liveUrl
browsers.create
- GetRead-only
GET /browsers/{id} — browser status, URLs, cost, recording
browsers.get
- ListRead-only
GET /browsers — paginated browsers, filter by active/stopped
browsers.list
- StopWrite
PATCH /browsers/{id} — stop a browser and refund unused time
browsers.stop
Runs
- CancelWrite
POST /runs/{id}/cancel — cancel an in-flight run
runs.cancel
- CreateWrite
POST /runs — start a browser agent run for a natural-language task
runs.create
- GetRead-only
GET /runs/{id} — full run once status is terminal: result, tokens, cost
runs.get
- Get StatusRead-only
GET /runs/{id}/status — cheap poll until completed, failed, or cancelled
runs.getStatus
Connect Browser Use to Claude, ChatGPT or Cursor
- 1
Connect Browser Use in Corsair
Add your Browser Use API key once in Corsair. Corsair stores the credential encrypted and makes the Browser Use API calls for your agent, so it never goes into a prompt or a config file. Connect Browser Use
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Browser Use. On a ChatGPT personal plan, connect Browser Use here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. None of Browser Use's operations are destructive, so in the default Cautious mode they all run right away. Strict mode asks before each of its 4 writes, and Read mode allows reads only.
FAQ
Install corsair and @corsair-dev/browseruse, add the Browser Use plugin, and connect with an API key. Then call methods like corsair.browseruse.api.browsers.create() from your app. Corsair syncs data per tenant.
Yes. Browser Use requires an API key from your Browser Use account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit Browser Use, GitHub, Notion, Stripe, and the rest. Trigger Browser Use from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for stealth cloud browsers you drive over cdp with playwright or puppeteer, plus hosted browser agent runs, behind one api key. Common builds include sync jobs, admin tooling, and agents that call Browser Use APIs from your backend. Local DB entities let you query synced Browser Use records without hitting the API on every read.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Browser Use API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/browseruse in the open repo. When Browser Use ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Browser Use data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Browser Use data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put Browser Use on a link in Strict mode and every write waits for your approval, while destructive actions are refused. None of the Browser Use operations are destructive, so the default Cautious mode runs them all without asking. You can change a link's mode at hub.corsair.dev/me.