LeonTing1010/tap
Universal protocol for AI to operate websites — 77 pre-built taps, MCP native, zero AI at runtime
Platform-specific configuration:
{
"mcpServers": {
"tap": {
"command": "npx",
"args": [
"-y",
"tap"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
<p align="center"> <h1 align="center">Tap</h1> <p align="center"><b>Make every interface programmable by AI.</b></p> </p>
<p align="center"> <a href="https://github.com/LeonTing1010/tap/actions/workflows/ci.yml"></a> <a href="https://github.com/LeonTing1010/tap/releases/latest"></a> <a href="LICENSE"></a> <a href="https://github.com/LeonTing1010/tap/stargazers"></a> <a href="#built-in-taps"></a> </p>
<p align="center"> <a href="README.zh-CN.md">中文</a> </p>
Tap is a universal protocol for AI to operate any interface. Define 8 kernel primitives, get 16 stdlib operations, cover every human-interface interaction. AI forges .tap.js scripts once — then any agent runs them deterministically, zero AI at runtime.
77 taps across 40 sites — Twitter/X, Reddit, GitHub, YouTube, Bilibili, Zhihu, Xiaohongshu, Weibo, Medium, arXiv, and many more. Works with your Chrome login session. No API keys needed.
forge_inspect → forge_verify → forge_save → tap.run
AI analyzes AI tests AI saves runs forever, zero AIOne agent forges a tap, every agent benefits.
Existing browser automation tools require AI at every step, or bind to one language, one runtime. Tap takes a different approach — the POSIX approach:
| Problem | Tap's Answer | |---------|-------------| | AI is slow and expensive at runtime | **Forge once, ru
Loading reviews...