Skip to content

guodaxia103/tabrix

Folders and files

NameName
Last commit message
Last commit date

Latest commit

ย 

History

367 Commits
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

Tabrix

Release NPM Version NPM Downloads License: MIT TypeScript

Turn real Chrome into an MCP-native AI execution layer.

Tabrix is a Chrome extension + local native server that lets any MCP client operate your daily browser session safely and efficiently, with your existing logins, cookies, and browsing context.

Documentation: English | Chinese


Why Tabrix

  • Real browser session, not a clean-room browser process
  • Model/client agnostic (works with any MCP-compatible assistant)
  • Local-first architecture for privacy-sensitive workflows
  • Production-focused diagnostics (tabrix status, doctor, smoke)

What You Can Build

  • Browser copilots for research, QA, operations, and support
  • Cross-tab task automation with semantic context
  • Safe web workflows with human-in-the-loop checkpoints
  • MCP toolchains that combine browser, filesystem, and APIs

Quick Start (3 Minutes)

1) Install CLI

npm install -g @tabrix/tabrix@latest
# or
pnpm install -g @tabrix/tabrix@latest

If pnpm does not run postinstall scripts:

tabrix register

2) Install Chrome Extension

Download from Releases, then load the tabrix-extension-vX.Y.Z.zip unpacked folder at chrome://extensions.

3) Verify Environment

Check runtime status:

tabrix status

Run diagnostics:

tabrix doctor

Run smoke test:

tabrix smoke

4) Connect from MCP Client (Streamable HTTP)

{
  "mcpServers": {
    "tabrix": {
      "type": "streamableHttp",
      "url": "http://127.0.0.1:12306/mcp"
    }
  }
}

Configs for popular AI assistants and MCP clients (OpenClaw, CoPaw, Claude Desktop, Cursor, Cline, Cherry Studio, Dify, etc.): Client Config Quick Reference

๐ŸŒ Remote Control

Typical remote MCP config:

{
  "mcpServers": {
    "tabrix": {
      "url": "http://<LAN_IP>:12306/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TABRIX_TOKEN>"
      }
    }
  }
}

Turn on Remote Access in extension popup and expose:

  • http://<LAN_IP>:12306/mcp

Enable In 30 Seconds

  1. Open extension popup -> switch to Remote -> enable Remote Access
  2. Open Token Management and copy current token (or click refresh)
  3. Paste LAN config to your MCP client and start remote automation

Security Default

  • Remote mode must use bearer-token authentication
  • Extension Token Management page supports view/copy/refresh
  • Token validity is configurable:
    • Set custom days in Token Management -> Refresh Token
    • Or set MCP_AUTH_TOKEN_TTL (0 means never expire)
  • If MCP_AUTH_TOKEN env is set, env token always has priority

Core Capabilities

  • Browser navigation and tab/window control
  • Page interaction (click, fill, keyboard, upload)
  • Rich extraction (web content, interactive elements, console)
  • Network capture and request replay helpers
  • Screenshot, GIF recording, performance trace analysis
  • Bookmarks/history operations and JavaScript execution

CLI Commands

Installed executables:

tabrix
tabrix-stdio

First-time guided setup:

tabrix setup

Register Native Messaging host:

tabrix register

Fix local execution permissions:

tabrix fix-permissions

Update MCP port:

tabrix update-port <port>

Check current runtime status:

tabrix status

Diagnose issues (--fix applies common auto-fixes):

tabrix doctor
tabrix doctor --fix

Run browser-path smoke test:

tabrix smoke

Run stdio-only smoke test:

tabrix stdio-smoke

Export diagnostics report (copy to clipboard):

tabrix report --copy

Daemon lifecycle commands:

tabrix daemon start
tabrix daemon status
tabrix daemon stop

Full command reference: CLI.md

Full tool list: TOOLS API (EN) | TOOLS API (ZH)

Roadmap (Open Source + Product)

  • Smart DOM Understanding and dehydration pipeline
  • Workflow recording and deterministic replay
  • Policy-based safety and permission model
  • Team workspace and multi-operator collaboration
  • Firefox extension support

If you want to co-build any roadmap item, open an issue with label proposal and architecture notes.

Contributing

Contributions are welcome from both first-time contributors and maintainers.

High-impact contribution areas

  • Reliability and reconnect stability
  • Tool schema consistency and DX
  • Cross-platform install and packaging quality
  • Benchmarking and regression test coverage

Community First (Current Phase)

Our current priority is community growth and project reputation:

  • Lower onboarding friction for new users and contributors
  • Keep release quality high with transparent changelogs and issue triage
  • Improve reliability across platforms and MCP clients
  • Build an open roadmap with active maintainer feedback

Long-term, once adoption and ecosystem maturity are in place, we may explore sustainable paths that remain compatible with the open-source community.

Project Origin and Credits

Tabrix is a community-driven continuation of hangwin/mcp-chrome.

We appreciate the original maintainers and contributors who created the foundation. Tabrix exists to provide sustained maintenance, clearer roadmap execution, and faster iteration.

Documentation Index

For Users

For Developers

License

MIT. See LICENSE.

About

MCP-native Chrome automation layer for AI assistants. Open source, community-driven, and production-focused

Topics

Resources

License

Contributing

Security policy

Stars

Watchers

Forks

Packages

 
 
 

Contributors