Apify
Web data and browser automationCloud platform of ready-made scrapers ("Actors") and automation. Its hosted MCP server at mcp.apify.com lets AI assistants run Actors and get structured web data back.
Independent review. Unpaid; no partnership with Browser Use. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Open-source library and cloud service that lets AI agents operate a web browser. The cloud MCP server connects client apps such as Claude, Cursor and Windsurf, or any MCP client. Useful when a site has no API; review anything that submits or buys.
Judgment, not a score. Documentation checked 2026-10-18.
Connections: MCP connections · APIs · Portability and vendor lock-in.
Cloud is pay as you go. Browser time is US$0.02/hour and residential proxy traffic US$5/GB. Hosted agents also incur model cost plus a 20% fee; browser and network usage remain additional. BYOK pays the model provider separately and retains Browser Use's orchestration fee. Purchased credits do not expire; top-ups start at US$5. Checked October 18, 2026. source ↗
The documented remote MCP server runs V3 sessions and includes setup for Claude Code, Claude Desktop, Cursor and Windsurf. The newer Cloud quickstart uses API V4; these interfaces and workspace IDs are not interchangeable. File upload is documented through V4 workspaces. Documentation reviewed; these integrations have not been tested by IonBin. source ↗
How Browser Use connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
| Platform | MCP / connector | API (agent-written code) | Browser | Upload / export |
|---|---|---|---|---|
| Claude (incl. Claude Code) | Not documented Browser Use has an official MCP server and Claude (incl. Claude Code) supports MCP, but Browser Use's docs don't name this pairing. Auth setup may differ. Browser Use MCP docs ↗Claude (incl. Claude Code) MCP docs ↗ | Not documented Claude (incl. Claude Code): Claude Code edits files and runs commands Browser Use publishes an API, but this pairing still needs network, authentication and execution-scope checks. Browser Use API ↗Claude (incl. Claude Code) docs ↗ | Inferred Claude Code with the Claude in Chrome extension (Chrome, Edge and other Chromium browsers). Browser Use is a web app; the pairing itself is not documented. Claude (incl. Claude Code) browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Browser Use's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route. Browser Use file docs ↗Claude (incl. Claude Code) file docs ↗ |
| OpenAI Codex | Not documented Browser Use has an official MCP server and OpenAI Codex supports MCP, but Browser Use's docs don't name this pairing. Auth setup may differ. Browser Use MCP docs ↗OpenAI Codex MCP docs ↗ | Not documented OpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Browser Use publishes an API, but this pairing still needs network, authentication and execution-scope checks. Browser Use API ↗OpenAI Codex docs ↗ | Inferred Only in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Browser Use is a web app; the pairing itself is not documented. OpenAI Codex browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Browser Use's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. Browser Use file docs ↗OpenAI Codex file docs ↗ |
| Google Antigravity | Not documented Browser Use has an official MCP server and Google Antigravity supports MCP, but Browser Use's docs don't name this pairing. Auth setup may differ. Browser Use MCP docs ↗Google Antigravity MCP docs ↗ | Not documented Google Antigravity: Agents edit code and run tasks Browser Use publishes an API, but this pairing still needs network, authentication and execution-scope checks. Browser Use API ↗Google Antigravity docs ↗ | Inferred The /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Browser Use is a web app; the pairing itself is not documented. Google Antigravity browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Browser Use's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. Browser Use file docs ↗Google Antigravity file docs ↗ |
Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.
| Level | Status | Detail / source |
|---|---|---|
| Native connector / MCP | Yes | Official docs ↗ |
| API / CLI | Yes | Official docs ↗ |
| Browser / manual | No | Browser access is recorded alongside a documented programmatic route. |
| File upload / import | Yes | Official docs ↗ |
Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.
MCP client support to verify.
No long-form review yet. Verdict is based on research, not hands-on testing.
Cloud platform of ready-made scrapers ("Actors") and automation. Its hosted MCP server at mcp.apify.com lets AI assistants run Actors and get structured web data back.