Browser automation MCP server and Chrome extension that lets AI applications control a connected tab in the user's existing browser profile.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
5 prerequisites to line up before setup. Have accounts and credentials ready first.
Safety & privacy surface
4 safety and 3 privacy notes across 5 risk areas. Review closely: credentials & tokens, third-party handling.
{
"mcpServers": {
"browsermcp": {
"command": "npx",
"args": ["@browsermcp/mcp@latest"]
}
}
}BrowserMCP is a browser automation MCP server paired with a Chrome extension. It lets AI applications such as Claude, Cursor, VS Code, and Windsurf automate a connected tab in the user's existing browser profile rather than launching a fresh browser instance.
The project emphasizes local automation, reuse of the user's current browser profile, and workflows where an AI assistant can test web apps or automate repetitive browser tasks.
These sources were reviewed on 2026-06-05. Prefer the live docs for current extension installation, server config, supported clients, and troubleshooting.
Install and pin the BrowserMCP extension from the project site, then add the MCP server to your AI application:
{
"mcpServers": {
"browsermcp": {
"command": "npx",
"args": ["@browsermcp/mcp@latest"]
}
}
}
Open the extension, click Connect on the tab you want the agent to control, and then issue browser automation requests through your MCP client.
BrowserMCP is convenient because it uses a real browser profile, but that also makes it sensitive. Prefer a dedicated testing profile, keep unrelated accounts closed, and require approval for submissions, payments, account updates, data deletion, or communication with other people.
Treat connected-tab content, screenshots, console output, and form fields as sensitive. They can contain personal data, credentials, customer records, or internal application state.
content/mcp/playwright-mcp-server.mdx covers Playwright-driven browser
automation, content/mcp/chrome-devtools-mcp-server.mdx covers the official
Chrome DevTools server, and content/mcp/chrome-mcp-server.mdx covers the
separate hangwin/mcp-chrome extension bridge. This entry covers the
BrowserMCP/mcp project and its BrowserMCP extension workflow.
Show that BrowserMCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/browsermcp-server)BrowserMCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Browser automation MCP server and Chrome extension that lets AI applications control a connected tab in the user's existing browser profile. Open dossier | Chrome extension-based MCP server that exposes an existing Chrome browser profile to AI assistants for tab management, page content, screenshots, interaction, history, bookmarks, and network inspection. Open dossier | Browser-control MCP server and CLI that lets AI agents use a real Chrome session, including logged-in browser state, site adapters, DOM snapshots, authenticated fetches, network traces, screenshots, and page actions. Open dossier | Mozilla-maintained MCP server for automating Firefox through WebDriver BiDi, with tools for page navigation, snapshots, UID-based input, screenshots, network requests, console messages, dialogs, history, viewport changes, optional JavaScript evaluation, privileged Firefox contexts, preferences, and WebExtension. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | Not reviewed | Not reviewed | Not reviewed | Not reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| Submitter | oktofeesh1 | oktofeesh1 | oktofeesh1 | oktofeesh1 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — | |
| Category | mcp | mcp | mcp | mcp |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | BrowserMCP | hangwin | epiral | Mozilla |
| Added | 2026-06-05 | 2026-06-05 | 2026-06-06 | 2026-06-06 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓BrowserMCP can navigate pages, click controls, type text, submit forms, capture screenshots, inspect accessibility snapshots, read console logs, and automate the connected tab. Because it uses the user's real browser profile, logged-in sessions and account permissions may be available to the agent. Require human approval before purchases, messages, account changes, destructive actions, or actions that violate a site's terms. Use a test profile or non-production account for end-to-end testing and repetitive automation. | ✓This server controls the user's existing Chrome browser profile and can reuse logged-in sessions. Tools can navigate pages, click elements, fill forms, inspect tabs, capture screenshots, inspect network traffic, read history, manage bookmarks, and inject scripts. Use a dedicated browser profile for agent work and avoid sensitive accounts unless the workflow explicitly requires them. Do not allow agents to submit forms, make purchases, change account settings, or perform irreversible actions without human approval. The project describes itself as early-stage and under active development; test carefully before relying on it for critical workflows. | ✓bb-browser can control a real browser session, inspect pages, click elements, fill inputs, evaluate JavaScript, fetch URLs with browser authentication, capture screenshots, and inspect network traffic. Commands may act as the logged-in user on social, finance, job, developer, shopping, and knowledge websites. Keep the daemon bound to trusted local interfaces unless you deliberately configure remote access through a private network. Review community site adapters before using them with authenticated accounts or valuable sessions. Require human approval before posting, submitting forms, changing account settings, applying to jobs, making purchases, or running destructive site actions. | ✓Browser pages can contain prompt-injection text in visible content, hidden HTML, ARIA labels, console output, network responses, or page metadata. The server can navigate pages, click, hover, fill forms, drag, upload files, accept dialogs, dismiss dialogs, go through history, change viewport size, close tabs, and restart Firefox. Enabling evaluate_script allows arbitrary JavaScript in page context; compromised instructions could read page data, modify the DOM, or interact with accessible browser APIs. Enabling privileged context tools with the required Firefox system-access environment variable can expose privileged Firefox APIs and may extend beyond web-content sandbox boundaries. Connect-existing mode can attach to a real browsing session with cookies, logins, active tabs, history, and saved state, so avoid it unless the profile is dedicated to automation. Accepting insecure certificates weakens TLS validation and can hide man-in-the-middle or misconfiguration signals. |
| Privacy notes | ✓Connected tab content, screenshots, form fields, console logs, and page state may be exposed to the MCP client and model. Logged-in pages can contain personal data, customer information, credentials, tokens, internal URLs, or private documents. Although the project describes local automation, prompts and tool results still flow through the chosen AI application and model provider. | ✓Open tabs, page content, screenshots, browsing history, bookmarks, cookies/session-derived page state, and network request metadata may be exposed to the MCP client and model. Screenshots and network responses can contain credentials, personal data, customer data, tokens, and private documents. Browser automation prompts may reveal personal browsing habits, internal applications, and authenticated service access. | ✓Tab URLs, titles, DOM snapshots, page content, selected elements, screenshots, network requests, responses, console output, traces, and authenticated fetch results may be exposed to the MCP client and model. Browser login state is used by the page and browser; even if cookies are not extracted directly, commands can act through authenticated sessions. Network request bodies and response data may contain tokens, account data, personal messages, search history, customer information, or internal application data. The upstream privacy doc says communication is local and there is no telemetry or external server, but model providers still receive any data your MCP client sends in prompts or tool results. | ✓Page content, DOM snapshots, accessibility labels, console messages, network requests, headers, screenshots, uploaded file paths, extension names, Firefox prefs, and browser logs can be sent to the MCP client and model. A regular Firefox profile can expose cookies, saved sessions, browsing history, account data, extensions, and private tabs to browser automation. Screenshot save paths, uploaded files, downloaded artifacts, and model transcripts can reveal local project names, test data, credentials shown on pages, or customer information. Use a separate profile, minimize enabled capabilities, avoid sensitive sites, and review provider/browser data handling before automating logged-in sessions. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Let MCP clients control and inspect a local Chrome browser through the mcp-chrome extension and bridge.
Connect Claude, Codex, Cursor, and other agents to a local Chrome session with bb-browser's MCP mode, local daemon, Chrome extension, 100+ site commands, browser automation tools, and local-only privacy model.
Source-backed guides for putting this to work.
Debug web apps with Claude in Chrome and Claude Code together.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.