BrowserTap MCP

io.github.LinVireoPublished by GitHub account LinVireov0.4.12Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyBrowser Automation

Overview

AI-generated overview

A local MCP server that drives the real Chrome, Edge or Opera browser you already use, through a browser extension and CDP.

What you can do
Controls a connected desktop browser through an extension and the Chrome DevTools Protocol, so the assistant can act on real pages rather than a headless instance. Targets a preferred browser (chrome, edge or opera) for unqualified calls, defaulting to whichever registered first. Runs a local bridge daemon on a loopback port and keeps its token and runtime state in a state directory. Offers two approval profiles: lab, which skips approval prompts, and safe, which asks for confirmation; both still enforce a cross-process lock, a quiet-input gate, target activation and on-screen confirmation.
When to use it
Useful when an assistant should work inside the user's everyday logged-in browser on a desktop machine, for example to inspect or interact with pages that need an existing session. Not suited to headless servers or remote-only setups.
Requirements
Runs as a local process on a desktop machine via the PyPI package browsertap-mcp over stdio. Needs a supported browser (Chrome, Edge or Opera) with the companion extension connected. Optional environment variables: BROWSERTAP_BRIDGE_PORT (default 18765), BROWSERTAP_MODE (lab or safe, default lab), BROWSERTAP_PREFERRED_BROWSER, BROWSERTAP_STATE_DIR (default ~/.browsertap). No authentication is declared.
Before you install
The default lab mode skips approval prompts, so browser actions may proceed without asking; choose safe mode if confirmation matters. The bridge token and runtime state are stored in BROWSERTAP_STATE_DIR, so protect that directory. The server acts on the user's real, logged-in browser, so actions can affect live accounts and data.

Installation

In SourceWeft

  1. Open BrowserTap MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.12LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.