Browser MCP MCP Server
Automate existing browser sessions locally via AI agents for private workflows.
Data last scanned today · Reviewed today
Overview
Browser MCP provides an MCP server and Chrome extension that enables AI applications like Claude, Cursor, and VS Code to interact directly with your web browser. By leveraging your existing browser profile, it allows AI models to perform tasks while keeping you logged into your services. Automation occurs locally on your machine, which prevents browser activity from being transmitted to remote servers. It also utilizes your actual browser fingerprint to assist in bypassing basic bot detection and common CAPTCHA barriers.
Our verdict
With a high-risk security score of 31/100, this tool should be approached with caution. The repository has not been updated in over 455 days, significantly increasing the likelihood of unpatched issues. Furthermore, it is a community-maintained project rather than an official vendor release, and its lack of editorial review means the codebase hasn't been vetted for current best practices. It is recommended for users who prioritize privacy in local automation but are comfortable managing the risks of stale dependencies.
- Operates locally to maintain user privacy
- Uses existing browser profile for logged-in sessions
- Includes only 5 direct dependencies
- Avoids detection by using real browser fingerprints
- Last commit was 455 days ago
- Single contributor presents high bus-factor risk
- Cannot be built independently from its original monorepo
- Community-maintained without official vendor support
Setup
{
"mcpServers": {
"browsermcp-mcp": {
"args": [
"-y",
"@browsermcp/mcp"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What software components are required to use Browser MCP?
Browser MCP requires the MCP server and the accompanying Chrome extension to function.
›Does the server create a new browser instance for automation?
No, it utilizes your existing browser profile to perform automation, which allows you to maintain logged-in sessions.
›Where does the browser automation processing occur?
Automation takes place locally on your machine, ensuring your activity data remains on your device and is not sent to remote servers.
›Can I build this repository directly from the source code?
No, the repository currently cannot be built on its own due to dependencies on utility and type files located in a separate monorepo.
Alternatives
Badge
Maintain this server? Add the live badge to your README.