BrowserTap MCP

MCP server that drives the real Chrome you already use, through an extension and CDP. It runs locally over stdio via the published package.

People who work with browser automation and chrome devtools protocol and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in Python.

VERIFIED ACTIVE

LAST COMMIT 2026-09-14 · ★ 1 · VERIFIED 2026-09-18

MIT · Python servers · how we verify → /methodology

01 · Install BrowserTap MCP

before you install - you'll need

The README does not document required environment variables for a basic install.

Claude Code

claude mcp add linvireo-browsertap-mcp -- uvx browsertap-mcp

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "linvireo-browsertap-mcp": {
      "command": "uvx",
      "args": [
        "browsertap-mcp"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

repo age created 2026-08-12 - young repo, little track record yet

license MIT - declared in the repository

pypi package browsertap-mcp - check the name against the project README before installing (PyPI has no namespace ownership)

registry namespace io.github.LinVireo is GitHub-verified and matches the repo owner

03 · What BrowserTap MCP can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

v0.5.4 · 2026-09-14

BrowserTap 0.5.4 makes page observations directly usable by agents and fixes premature navigation initialization timeouts. · scan_page now reports actionable controls, their state, recommended input tools, and complete…

v0.5.3 · 2026-09-14

BrowserTap 0.5.3 adds Claude Code and Codex plugins and direct input for nested, cross-origin and out-of-process iframe forms. · Highlights · Install the MCP server and its caller Skills through the host plugins and…

v0.4.12 · 2026-08-23

First BrowserTap release published to PyPI. · Install: · bash · pip install "browsertap-mcp[desktop]" · Added · Physical-input coordinates are checked against the real display geometry, and a · point on no display at…

04 · Who maintains BrowserTap MCP

BrowserTap MCP is maintained by linvireo. It's the only MCP server we track from this author; the repo dates to Aug 2026.

05 · Facts

repository: github.com/linvireo/browsertap-mcp
website: https://github.com/LinVireo/browsertap-mcp
category: browser automation - actively maintained as of 2026-09-18.
release cadence: 3 releases in the last 90 days (latest 2026-09-14)
registry: io.github.LinVireo/browsertap-mcp (active, first published 2026-08-23)
packages: pypi:browsertap-mcp

06 · BrowserTap MCP FAQ

What is BrowserTap MCP?

MCP server that drives the real Chrome you already use, through an extension and CDP. It runs locally over stdio via the published package.

Is BrowserTap MCP still maintained?

Yes - as of 2026-09-18, its last commit was 2026-09-14 and it shipped 3 releases in the last 90 days. We re-verify nightly.

How do I install BrowserTap MCP?

Run `uvx browsertap-mcp`. The README does not document required environment variables for a basic install. You can also paste the ready-made client config above.

Does BrowserTap MCP run locally?

Yes - it's a stdio server: it runs on your machine (via uvx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to BrowserTap MCP

Alternatives to BrowserTap MCP

Maintained browser automation servers if BrowserTap MCP isn't the fit.

Pairs well with

Servers that cover what BrowserTap MCP doesn't - only shown when the pairing reason fits the companion.