Tabryn
Connects AI agents to your Chrome browser via MCP, enabling real-time control of existing tabs, sessions, and application state for development workflows.
README
<div align="center">
Tabryn
The Browser Runtime for AI Agents
Your browser. Your session. Any agent.
<br/>
Installation • Features • Architecture • Tools • CLI • Contributing
</div>
Tabryn connects AI coding agents to the Chrome browser you're already using — existing tabs, existing sessions, real application state — through a universal MCP browser runtime.
Why Tabryn?
Browser automation traditionally means running a separate browser or profile. Coding agents need controlled access to the real development browser — the one with your logged-in sessions, your localhost tabs, your actual application state. Tabryn bridges this gap.
<br/>
Features
| Feature | Description |
|---|---|
| Real Browser State | Access your actual Chrome tabs, sessions, and cookies |
| MCP Native | First-class Model Context Protocol support |
| Zero Config | Works out of the box with your existing Chrome |
| Secure by Design | Local-only communication, no credential exposure |
| Multi-Agent | Works with Claude Code, Codex, Kiro, OpenCode, Gemini CLI, and more |
<br/>
Installation
# Clone and build
git clone https://github.com/idugeni/tabryn.git
cd tabryn
npm install
npm run build
# Set up native messaging host
node dist/cli/index.js install
Load Chrome Extension
- Open
chrome://extensions - Enable Developer mode
- Click Load unpacked
- Select the
extension/directory
That's it! Extension will auto-configure on first connection.
Add to MCP Client
<details> <summary><strong>Claude Code</strong></summary>
claude mcp add tabryn -- node /path/to/tabryn/dist/mcp/index.js
</details>
<details> <summary><strong>VS Code / Cursor</strong></summary>
Add to .vscode/mcp.json:
{
"servers": {
"tabryn": {
"command": "node",
"args": ["/path/to/tabryn/dist/mcp/index.js"]
}
}
}
</details>
<details> <summary><strong>Other MCP Clients</strong></summary>
Add to your MCP config:
{
"mcpServers": {
"tabryn": {
"command": "node",
"args": ["/path/to/tabryn/dist/mcp/index.js"]
}
}
}
</details>
Verify
node dist/cli/index.js doctor
<br/>
Architecture
┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ AI Agent │────▶│ MCP Server │────▶│ Bridge │────▶│ Chrome │
│ │◀────│ │◀────│ │◀────│ Extension │
└─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘
stdio TCP Native Messaging DevTools API
Supported Agents:
Claude Code ─┐
Codex CLI ───┤
Kiro ────────┤
OpenCode ────┤
OpenClaw ────┼──→ Tabryn ──→ Your Chrome
Hermes ──────┤
Gemini CLI ──┤
Custom Agent ┘
<br/>
Available Tools
| Tool | Description |
|---|---|
list_tabs |
List all open Chrome tabs |
select_tab |
Activate a specific tab |
create_tab |
Open a new tab |
close_tab |
Close a tab |
navigate |
Navigate to URL or go back/forward |
read_page |
Read page accessibility tree |
screenshot |
Capture tab screenshot |
click |
Click at coordinates |
type |
Type text into focused element |
scroll |
Scroll the page |
form_input |
Set form element values |
execute_js |
Execute JavaScript in page context |
read_console |
Read console messages |
read_network |
Read network requests |
reload |
Reload the page |
wait |
Wait for page condition |
<br/>
Example: Development Workflow
┌──────────────────────────────────────────────────────────────────────────┐
│ Agent: Edit code → Run dev server → list_tabs → find localhost tab │
│ Agent: screenshot → inspect UI → read_console → find errors │
│ Agent: click → interact → reload → verify fix │
└──────────────────────────────────────────────────────────────────────────┘
<br/>
CLI Commands
| Command | Description |
|---|---|
tabryn install |
Set up native messaging host and extension |
tabryn mcp |
Start the MCP server |
tabryn doctor |
Diagnose setup and connection issues |
<br/>
Configuration
Environment Variables
| Variable | Default | Description |
|---|---|---|
TABRYN_PORT |
18766 |
TCP port for MCP server ↔ Bridge communication |
<br/>
Security
Tabryn is designed with security as a first-class requirement:
- No credential exposure — Cookies, passwords, and session tokens are never sent to agents
- Permission boundaries — Users control which tabs are accessible
- Input validation — All messages are validated before processing
- Local-only communication — All traffic stays on localhost
See SECURITY.md for the full security model.
<br/>
Architecture Decision Records
- ADR-0001: Communication Protocol — Why Native Messaging + TCP
<br/>
Contributing
See CONTRIBUTING.md for development setup and guidelines.
<br/>
License
<br/>
<div align="center">
Built with ❤️ for the AI agent community
</div>
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。