Workspace root for the public Tap packages (spec / adapters / create-tap-script). Not published — exists so npm workspaces can link local source
Workspace root for the public Tap packages (spec / adapters / create-tap-script). Not published — exists so npm workspaces can link local source between packages during development. Each package under packages/ is independently versioned. The tap mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
Logged — in sites** (your bank / internal dashboard / Xiaohongshu / Zhihu) — just tell your agent "set up tap for logged-in sites" right in the chat. TheAccuracy — DeterministicRuntimes — 2 (Chrome extension + Playwright)Platform — DownloadLinux — tap-linux-x64Windows — tap-windows-x64.exeAdapter — Source formatConcern — Cloud-first browser SDKsLayer — ProtectionSandbox — Programs run with zero permissions — no file, network, or system accessLocal-only — Your data, sessions, and API keys never leave your machine — architecturallyThe server ships on npm as @taprun/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Tap's toolset — Logged, Accuracy, Runtimes and 8 more — is a fair guide to whether it matches your workflow. It is maintained by leonting1010; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Tap's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Logged | in sites** (your bank / internal dashboard / Xiaohongshu / Zhihu) — just tell your agent **"set up tap for logged-in sites"** right in the chat. The **tap-setup** skill drives the whole bridge from the chat: it materiali |
| Accuracy | Deterministic |
| Runtimes | 2 (Chrome extension + Playwright) |
| Platform | Download |
| Linux | [tap-linux-x64](https://github.com/LeonTing1010/tap/releases/latest) |
| Windows | [tap-windows-x64.exe](https://github.com/LeonTing1010/tap/releases/latest) |
| Adapter | Source format |
| Concern | Cloud-first browser SDKs |
| Layer | Protection |
| Sandbox | Programs run with zero permissions — no file, network, or system access |
| Local-only | Your data, sessions, and API keys never leave your machine — architecturally |
{
"mcpServers": {
"tap": {
"command": "npx",
"args": ["-y", "@taprun/cli"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.