Server facts
Browser MCP
Project
- Author
- browsermcp
- Repository
- github.com/browsermcp/mcp
- Website
- browsermcp.io
- License
- Apache-2.0
- Category
- Browser Automation
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 7,189
- Last commit
- Data as of
Tags
- Browser Automation
- Chrome Extension
- Existing Sessions
- Local Execution
Overview
Browser MCP connects AI applications to the browser a user already has, pairing an MCP server with a Chrome extension. The README names VS Code, Claude, Cursor, and Windsurf as examples of applications that can use it. Its central distinction is profile reuse: automation operates through the existing browser rather than launching a separate browser instance. That preserves signed-in sessions across services and brings the user's real browser fingerprint into the automation workflow. The project presents this as a way to reduce the basic bot-detection obstacles associated with fresh automated browser sessions, not as a documented guarantee for every website.
Local operation is another stated focus. The README says browser activity stays on the device rather than being sent to remote servers by the automation system, and it attributes lower interaction latency to that local execution. The repository was adapted from Microsoft's Playwright MCP implementation specifically to work with the user's browser. However, the supplied README is a brief project introduction rather than a complete setup guide. It links to external documentation but gives no runnable installation command, environment-variable configuration, or named tool inventory. It also warns that the repository cannot currently build independently because it depends on utilities and types held in the development monorepo.
Install & configure
Requirements
- Chrome with the Browser MCP extension
- A compatible AI application or MCP client
No install command stated in the README — see repo.
A runnable installation command is Not stated in the README. It links to https://docs.browsermcp.io for setup and notes that the repository cannot build independently because of monorepo dependencies.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Claude Desktop setup guideConfig file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Cursor setup guideConfig file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the VS Code setup guideConfig file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Windsurf setup guideConfig file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
No install command stated in the README — see repo. Check the client documentation for a supported connection method.
Read the Claude Code setup guideExamples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Tools
No individual tool names were confirmed in the source material. Check the repository for its current tool list.
Names, permissions, and defaults can change. Check the current upstream documentation before granting access.
Use cases
- Automate a browser session that is already signed into services.
- Connect browser actions to an AI editor or assistant.
- Use an existing browser profile instead of a fresh automated instance.
Strengths
- Reuses existing profile state and logged-in sessions.
- Describes local execution without remote browser-activity storage.
- Designed to work with several AI applications.
Limitations
- The repository cannot currently be built independently of its development monorepo.
- No runnable installation command or tool inventory is stated in the README.
Frequently asked questions
Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.
