Tap — Local-First Browser MCP

Browser automation MCP — runs in your own browser with your logged-in sessions. Local-first alternative to Stagehand / Browserbase.

# Tap — Browser Automation MCP for Your Real Browser Tap is a local-first MCP browser-automation runtime. Claude Code, Cursor, Continue, Windsurf, or any MCP-compatible AI agent can drive your real Chrome with your own logged-in sessions — no cloud credentials, no per-step LLM cost, no vendor lock-in. AI participates at compile time only: saved plans replay deterministically at zero LLM token cost. ## Why Tap (vs. Stagehand / Browserbase / Playwright-MCP / BrowserMCP) Every cloud-first browser-automation MCP forces a tradeoff: ship your credentials to someone else's server, OR re-run an LLM on every step ($$$). Tap takes neither: - Runs in YOUR browser — your existing Chrome session with all your cookies, 2FA state, single-sign-on tokens. Credentials never cross a trust boundary; the extension only relays plan steps to the local Tap binary on your machine. - Zero-token replay — the AI agent compiles a plan ONCE into an inspectable JSON artifact. Every subsequent run is pure data + dispatch. No vision loop, no accessibility-tree re-parse, no per-execution tokenbill. - Plans are diff-able JSON — version-controllable, testable, shareable. Not opaque generated code, not LLM scratch-state. ## Features - MCP-native — drop-in for any MCP-compatible host (Claude Code, Cursor, Continue, Windsurf, Cline). 4 meta verbs: capture / verify / mark / run. - Authenticated by default — reuses your live Chrome cookies via Chrome Native Messaging. Same trust model as a browser bookmarklet; no localhost ports, no OS service. - Compile-time AI, runtime zero AI — the AI generates the plan once; runtime is deterministic. Predictable cost, predictable behavior, reproducible failures. - Composite plans — one plan can call other plans (op:tap composition). `tap verify` recursively checks composite plans against live substrates without side-effects.