Specific implementation researched
Browser Use
Implementation, permissions and documented client compatibility.
A directory listing or verification does not replace a security audit. No installation is triggered automatically here. Do not enter API keys in public forms.
What is specifically documented?
- Connected service
- Browser Use
- Publisher
- Browser Use
- Origin
- Officially from the named publisher
- Deployment mode
- Local
- Transport
- stdio über browser-use --cli-mcp; Browser kann lokal oder in Browser Use Cloud laufen.
- Authentication
- Existing local Chrome session; cloud access through browser_login or BROWSER_USE_API_KEY.
- Read capabilities
- Retrieve page information and screenshots
- Write capabilities
- Control the browser through a Python harness · Navigate, click, type and execute JavaScript
- Permissions
- Local mode controls the open Chrome browser, including existing logins. Cloud mode uses a separate cloud session.
- Required plan
- No confirmed information
- Additional costs
- No confirmed information
- Maintenance status
- The current guide uses --cli-mcp. The older --mcp mode is deprecated; old tool names no longer work.
- Review date
- 11/10/2026
Support by client
Documented setup is not an independent functional test. General MCP support does not imply full compatibility.
| Client | Status | Source |
|---|---|---|
| Claude Desktop | Setup documented | Documentation ↗ |
| Claude Code | Not verified | — |
| Claude Web | Not verified | — |
| Cursor | Setup documented | Documentation ↗ |
Sources & implementation
MCP server - Browser Use ↗Retrieved on 11/10/2026. Provider statements, not a security audit.
Implementation: https://docs.browser-use.com/open-source/mcp