Tap
Let your agent drive logged-in browser workflows in your real Chrome while cookies and passwords never leave your machine.
Overview
Tap is an MCP server for the Build phase that runs logged-in browser tasks in your local Chrome with credentials kept on your machine.
What is this MCP server?
- Browser MCP for logged-in tasks using your installed Chrome
- Credentials stay local; zero-token replay model for sensitive sessions
- Ships as @taprun/cli (npm) and taprun (PyPI) v0.17.0 with `mcp start` stdio entry
- Dual registry packages (npm + PyPI) with the same MCP start command
- Version 0.17.0
- 2 registry packages: npm @taprun/cli and PyPI taprun
- Stdio transport via positional args mcp start
Community signal: 8 GitHub stars.
What problem does it solve?
Agents cannot safely or reliably act inside sites that require your real login without brittle cookie export or cloud browsers.
Who is it for?
Solo builders automating authenticated web UIs during integration work who already use Chrome daily.
Skip if: Fully API-backed workflows, CI-only headless pipelines without a desktop Chrome, or teams that forbid local browser control by agents.
What do I get? / Deliverables
After registering Tap, your agent can replay browser workflows in Chrome with local auth and reduced token-heavy credential chatter.
- Stdio MCP server wired to your Chrome for agent-driven navigation
- Repeatable logged-in task replay without exporting tokens to the model
- Dual-package install path documented on taprun.dev and GitHub
Recommended MCP Servers
Journey fit
Authenticated browser automation is a build-time integration pattern when wiring agents to sites that lack APIs. Integrations is where MCP bridges your agent to external systems; Tap attaches that bridge to your existing Chrome session.
How it compares
Local Chrome browser MCP, not a remote headless farm or a single-site API wrapper skill.
Common Questions / FAQ
Who is Tap for?
Indie developers and agent users who need logged-in browser automation with sessions that stay on their own Chrome install.
When should I use Tap?
Use it while building integrations when a vendor portal or admin UI has no API and you want MCP-driven clicks and forms in a real profile.
How do I add Tap to my agent?
Install @taprun/cli via npm or taprun via PyPI v0.17.0, run `mcp start` for stdio, and add the server block to Claude Code or your MCP host config.