browsertap-mcp

Purpose: Automating real browser interactions, screenshots, cookies, and physical input through a developer-accessible MCP server.

Inferred · not functionally tested

Audience: developers building browser automation and AI agent workflows

Inferred · not functionally tested

Functions: browser_automation, agents

Inferred · not functionally tested

Interfaces: API: unknown · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org · github.com. These links do not verify the individual claims.

browsertap-mcp sits in PulseGate's Browser DevTools & extensions category. Inferred · not functionally tested: It focuses on automating real browser interactions, screenshots, cookies, and physical input through a developer-accessible MCP server. Inferred · not functionally tested: It is built as an open-source project for developers building browser automation and AI agent workflows. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: browsertap-mcp is available on the command line, and it can be self-hosted.

Behind browsertap-mcp is LinVireo, and it first shipped in 2026. Development happens publicly on GitHub with 83 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include real-browser control, CDP transport, and browserBridge integration. Basis unknown · not verified: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.