Browser Use
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
Docs checkedRemote Streamable HTTP · Metadata observed 2026-10-24
Connect Browser Use
Create your Cloud API key
Open Browser Use Cloud account settings and create an API key. Use the Cloud MCP documentation for this hosted connection.
Publisher instructions ↗Add the remote server
Add https://api.browser-use.com/v3/mcp to your MCP client. Configure Authorization with Bearer followed by your API key. Store the key in your client’s private credential settings.
Publisher instructions ↗Connect from your client
Save the connection and initialize it from your client. Follow the publisher’s client-specific instructions if a local bridge is needed.
Publisher instructions ↗
Connection address
https://api.browser-use.com/v3/mcpUse this address when adding the remote connection to your MCP client.
Credentials and access
Browser Use Cloud API key; Authorization bearer header recommended.
Setup notes from publisher documentation
- The publisher confirms the V3 MCP endpoint in this guide. Create a Browser Use Cloud API key in your account settings.
- The recommended header is Authorization: Bearer YOUR_API_KEY. The Registry snapshot lists X-Browser-Use-API-Key, which the publisher still supports as a legacy option.
- Use the cloud setup instructions for this connection; the separate local Browser Use server has different installation and LLM credential requirements.
Registry configuration snapshot (1 inputs)
Configure these in your MCP client. This page does not collect credentials. Requiredness and secret flags below come from the Registry snapshot; publisher notes above can clarify alternative setup paths.
Required in this Registry configuration
X-Browser-Use-API-Key Required · SecretBrowser Use Cloud API key from https://cloud.browser-use.com/settings
Registry definition:/remotes/0/headers/0Sources & review
Documentation checked 2026-10-23. Cloud endpoint and credential header checked against publisher documentation. No authenticated session or tool call was performed.
Registry inputs are a dated snapshot. Publisher checks are separate, scoped observations. The downloadable bundle preserves the original draft plus the documentation review; it is not a ready-to-run client configuration.
Inspect the source binding
com.browser-use/browser-use
Connection: /remotes/0
SHA-256: 267174a8a8a51dd4890908c8198ad59b5a0764de5b170d01d5040b01f5c8a1e6