Controls an existing Chrome, Edge, or Opera profile through an extension and CDP, with tools for tabs, pages, input, downloads, and state.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by BrowserTap MCP.
get_setup_statusreport `package_version`, `bridge_version`, `extension_version`, `protocol_version`, connection state, ports, tabs, and the required recovery action. A missing bridge listener is started automatically when spawning is enabled; `restart_bridge_required=true` means a bridge that is still running must…
get_automation_profileinspect whether the current MCP process uses `lab` or `safe`.
set_automation_profileswitch the current MCP process between `lab|safe`; the override is not persisted and does not reload the extension.
list_tabslist connected tabs under `data.tabs`, including their full session handles and `browser` fields. Answers while another tool is still running; `default_session_id` is this request's snapshot of the MCP process default and `default_session_settled=true`. Parallel agents should still pass an explicit…
list_all_tabs*(no tab needed)* list every open tab, including `chrome-extension://` pages that `list_tabs` hides. Those never become sessions, so they have no session id; drive them with `cdp_command(tab_id=...)`.
switch_tabset this MCP process's *target* tab for later calls. A `url_pattern` must match exactly one tab; if several match, select one with its full `session_id`. A `browser` filter matching multiple profiles also requires an explicit `session_id`. It does **not** raise the tab or focus the browser: `activa…
BrowserTap MCP MCP server exposes browser automation tools through MCP while reusing an open Chromium-based browser profile. It supports Chrome, Edge, and Opera, including existing tabs and logged-in sessions. The server can read page content, follow navigation, interact with controls, execute JavaScript, download files, and inspect or change browser state such as cookies and web storage.
The connection uses a browser extension and a local bridge that communicates with the browser through CDP. This design lets an agent work with a real profile instead of a disposable browser session. It also means the profile may contain authenticated accounts, stored data, extensions, and other user state.
An MCP client calls tools against the local server. BrowserTap tracks browser profiles, tabs, session handles, and tab ownership so calls can target a specific tab when several agents or browser windows are active. list_tabs reports connected session tabs, while list_all_tabs also exposes extension pages that do not become sessions. Calls can select a full session identifier when a URL or browser filter is not unique.
Page operations normally run in the selected tab and can remain in the background. Tools cover CSS or structured-locator clicks, text entry, key presses, dragging, scrolling, JavaScript execution, conditional waits, and URL waits. execute_js and other delayed operations can return an operation identifier that get_execute_js_result later retrieves without replaying the action.
Browser-level tools handle tab creation and closure, downloads through the browser’s native download manager, cookies, storage, and temporary site permissions. Dialog tools inspect or answer browser dialogs, while upload_files handles file inputs that JavaScript cannot set directly. The lab and safe automation profiles control certain approval behavior; changing the profile applies only to the current MCP process.
The project requires Python 3.10 or newer, Chrome, Edge, or Opera, a running browser user session, the BrowserTap Bridge extension, and an MCP client. Claude Code and Codex can use the documented plugin installation path. Cursor, Claude Desktop, and other MCP clients use the standard MCP installation described by the project.
After starting an agent session, call get_setup_status to obtain the extension path and connection details. In the browser’s extensions page, enable Developer mode and choose Load unpacked, then select that directory. Use the corresponding edge://extensions or opera://extensions page for Edge or Opera. The bridge listener can start automatically when spawning is enabled, but setup status may still require a bridge restart or extension action.
The BrowserTap MCP MCP server includes tools for:
This automation controls a real browser profile, so shared profile state is not isolated between concurrent tasks. Use explicit tab targets and owner-aware cleanup when managing agent-created tabs. The extension must be installed manually the first time. Background operation does not generally move the desktop cursor, but the project’s lab-only leave-dialog recovery and Windows native file-dialog capabilities have additional desktop requirements. Browser visibility can also differ from tab connection state; activate_tab is the explicit operation for bringing a tab and its window to the foreground.
Factual signals from GitHub, npm, and our automated checks — not a rating.
No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/browsertap-mcp)<a href="https://allmcps.com/mcp/browsertap-mcp"><img src="https://allmcps.com/api/badge/browsertap-mcp?style=directory" alt="BrowserTap MCP on AllMCPs" /></a>