BrowserTap MCP Server

BrowserTap MCP is an MCP integration. MCP server that drives the real Chrome you already use, through an extension and CDP.

Packages and local setup

The published pypi package is browsertap-mcp, version 0.4.12. Its declared MCP transport is stdio.

The package declares BROWSERTAP_PREFERRED_BROWSER: Which connected browser an unqualified call targets: chrome, edge or opera. Defaults to whichever registered first.; BROWSERTAP_MODE: Approval profile: lab or safe. Defaults to lab, which skips approval prompts and still enforces the cross-process lock, the quiet-input gate, target activation and on-screen confirmation; safe asks before every physical input.; BROWSERTAP_BRIDGE_PORT: Base loopback port for the bridge daemon. Defaults to 18765.; BROWSERTAP_STATE_DIR: Directory holding the bridge token and runtime state. Defaults to ~/.browsertap..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.4.12 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.