mcpField
C
cloud

cloud

github.com/browser-useDevelopment119.4k3.2k installsUpdated 2d ago
Repository

About cloud

cloud is a reference skill for using Browser Use Cloud APIs, SDKs, and integrations. It guides developers toward hosted task execution or browser access for an existing agent, with guidance for API versions, sessions, and browser lifecycle.

Key features

  1. 01Guidance for Cloud REST APIs and SDKs
  2. 02References for v2, v3, and v4
  3. 03Browser and hosted-agent integration paths
  4. 04Session, profile, and authentication guidance
  5. 05Browser lifecycle and billing cautions

Use cases

  1. 01Submit tasks to a hosted agent
  2. 02Connect an existing agent to a cloud browser
  3. 03Maintain integrations using older API versions

MCP support

The reference index links to MCP guidance, but the provided content does not describe MCP operations.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/browser-use/browser-use --skill cloud

After installing, type/cloudin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
api-v2.md
api-v3.md
api-v4.md
browser-api.md
features.md
patterns.md
quickstart.md
sessions.md
references/guides/
chat-ui.md
subagent.md
tools-integration.md

Details

From the project README

Browser Use Cloud Reference

Reference docs for the Cloud REST API, SDKs, and integration patterns. Read the relevant file based on what the user needs.

Choose a starter

  • Hosted task in, result out: use the V4 SDK runs resource in references/api-v4.md.
  • Your existing agent needs a browser: use the V4 SDK browsers resource or REST/CDP, then explicitly stop the browser.
  • Local framework development: use the open-source browser-use skill, not Cloud SDK calls.

Eligible new Google, GitHub or Microsoft signups get a one-time $1 Cloud credit. No card required; email/password signups do not qualify. Pricing and eligibility. Use gpt-5.6-luna for the free starter; paid-only models need a top-up.

Reuse BROWSER_USE_API_KEY, or guide the user through Cloud signup and key creation. Keep keys server-side, never in prompts or client bundles.

API & Platform

TopicRead
Current v4 setup, first run, sessions, workspaces, browsersreferences/api-v4.md
Legacy v2 setup, pricing, FAQreferences/quickstart.md
v2 REST API: all 30 endpoints, cURL examples, schemasreferences/api-v2.md
v3 BU Agent API: sessions, messages, files, workspacesreferences/api-v3.md
Sessions, profiles, auth strategies, 1Passwordreferences/sessions.md
CDP direct access, Playwright/Puppeteer/Seleniumreferences/browser-api.md
Proxies, webhooks, workspaces, skills, MCP, live viewreferences/features.md
Parallel, streaming, geo-scraping, tutorialsreferences/patterns.md

Integration Guides

TopicRead
Building a chat interface with live browser viewreferences/guides/chat-ui.md
Using browser-use as a subagent (task in → result out)references/guides/subagent.md
Adding browser-use tools to an existing agentreferences/guides/tools-integration.md

Critical Notes

  • Use v4 for new hosted-agent integrations. Keep v2 or v3 only when maintaining an existing integration or using a resource not yet wrapped by the v4 SDK.
  • Cloud API base URL: https://api.browser-use.com/api/v2/ (v2), https://api.browser-use.com/api/v3 (v3), or https://api.browser-use.com/api/v4 (v4)
  • Auth header: X-Browser-Use-API-Key: <key>
  • Get API key: https://cloud.browser-use.com/new-api-key
  • Set env var: BROWSER_USE_API_KEY=<key>
  • Cloud SDK: uv pip install browser-use-sdk (Python) or npm install browser-use-sdk (TypeScript)
  • Python v2: from browser_use_sdk import AsyncBrowserUse
  • Python v3: from browser_use_sdk.v3 import AsyncBrowserUse
  • Python v4: from browser_use_sdk.v4 import BrowserUse or AsyncBrowserUse
  • TypeScript v2: import { BrowserUse } from "browser-use-sdk"
  • TypeScript v3: import { BrowserUse } from "browser-use-sdk/v3"
  • TypeScript v4: import { BrowserUse } from "browser-use-sdk/v4"
  • SDK 3.11.3 or newer exposes browsers.create and browsers.stop in the v4 namespace, alongside the v4 REST /browsers resource. Always stop a browser explicitly; closing CDP does not stop billing.
  • CDP WebSocket: wss://connect.browser-use.com?apiKey=KEY&proxyCountryCode=us

Comments

Markdown supported