# Browser Use Cloud MCP server > Run cloud browser-agent sessions for web tasks, form filling and data extraction, with follow-up tasks and saved login profiles. - Listing: https://mcp.tc/i/browser-use-cloud - Connect: use the server's own URL `https://api.browser-use.com/v3/mcp` (with your API key); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: API key - Category: [Browser Automation](https://mcp.tc/c/browser-automation) - Vendor: Browser Use - Homepage: ## About Connects an assistant to the Browser Use v3 cloud agent. You start a sandboxed browser session with a task in plain language, poll it for status and output, read the agent's steps, and send follow-up tasks to a session kept alive. Sessions can use saved browser profiles for sites that need a login, and can return structured output through a schema. Runs as a hosted streamable HTTP endpoint at https://api.browser-use.com/v3/mcp. Tool calls need a Browser Use API key sent in the x-browser-use-api-key header. Keys are created in the Cloud dashboard settings. ## What it can do - Start a cloud browser agent session from a plain-language task - Poll session status, output, step count, cost and live URL - Send follow-up tasks to an idle keep-alive session - Read the agent's browser actions and reasoning step by step - Stop a single task or destroy the whole session - Use saved browser profiles for tasks behind a login - Request structured output with an output schema ## Tools (7) - `run_session`: Create a browser agent session and run a task, with optional model, profile, schema and proxy… - `send_task`: Send a follow-up task to an idle keep-alive session to reuse its browser context. - `get_session`: Get a session's status, output, step count, cost breakdown and live URL. - `get_session_messages`: Get the agent's messages and steps for a session, with pagination. - `stop_session`: Stop the current task or destroy the session sandbox entirely. - `list_sessions`: List recent sessions for the project with status and cost. - `list_browser_profiles`: List cloud browser profiles that hold saved logins for authenticated tasks. ## Example prompts - "Open a browser session and extract the pricing table from example.com as JSON." - "List my browser profiles, then use the LinkedIn one to check my notifications." - "Fill out the contact form on this site with these details and report the result." - "Send a follow-up task to my running session to click the next page and collect the rows." ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http browser-use-cloud https://api.browser-use.com/v3/mcp --header "x-browser-use-api-key: " ``` 2. Replace the placeholder with your key before you run it, then check it with `/mcp` inside Claude Code. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Custom connectors can’t send this server’s key header, so use the `mcp-remote` bridge. Open **Settings → Developer → Edit Config** and add: `claude_desktop_config.json`: ```json { "mcpServers": { "browser-use-cloud": { "command": "npx", "args": [ "-y", "mcp-remote", "https://api.browser-use.com/v3/mcp", "--header", "x-browser-use-api-key: " ] } } } ``` 2. Replace the placeholder with your key and restart Claude Desktop. The bridge needs Node.js on your computer. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "browser-use-cloud": { "url": "https://api.browser-use.com/v3/mcp", "headers": { "x-browser-use-api-key": "" } } } } ``` ### VS Code Add it to `.vscode/mcp.json`. VS Code asks for the key the first time and stores it securely: `.vscode/mcp.json`: ```json { "servers": { "browser-use-cloud": { "type": "http", "url": "https://api.browser-use.com/v3/mcp", "headers": { "x-browser-use-api-key": "${input:x-browser-use-api-key}" } } }, "inputs": [ { "type": "promptString", "id": "x-browser-use-api-key", "description": "x-browser-use-api-key", "password": true } ] } ``` ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "browser-use-cloud": { "serverUrl": "https://api.browser-use.com/v3/mcp", "headers": { "x-browser-use-api-key": "" } } } } ``` 2. Refresh the MCP server list in Cascade. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add browser-use-cloud --url https://api.browser-use.com/v3/mcp ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.browser-use-cloud] url = "https://api.browser-use.com/v3/mcp" env_http_headers = { "x-browser-use-api-key" = "X_BROWSER_USE_API_KEY" } ``` Codex reads the header values from the environment variables named in `env_http_headers`. ### Gemini CLI ```bash gemini mcp add --transport http --header "x-browser-use-api-key: " browser-use-cloud https://api.browser-use.com/v3/mcp ``` This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "browser-use-cloud": { "type": "http", "url": "https://api.browser-use.com/v3/mcp", "headers": { "x-browser-use-api-key": "" } } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://api.browser-use.com/v3/mcp`. ## Details - Server version: 3.0.0 - MCP protocol version: 2024-11-05 - Last checked: 2026-10-03 (reachable) - Listed: 2026-10-03 - Updated: 2026-10-03 --- Source: https://mcp.tc/i/browser-use-cloud (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report