Skip to content

Weavetab/.github

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 
 
 

Repository files navigation


██╗    ██╗███████╗ █████╗ ██╗   ██╗███████╗████████╗ █████╗ ██████╗
██║    ██║██╔════╝██╔══██╗██║   ██║██╔════╝╚══██╔══╝██╔══██╗██╔══██╗
██║ █╗ ██║█████╗  ███████║██║   ██║█████╗     ██║   ███████║██████╔╝
██║███╗██║██╔══╝  ██╔══██║╚██╗ ██╔╝██╔══╝     ██║   ██╔══██║██╔══██╗
╚███╔███╔╝███████╗██║  ██║ ╚████╔╝ ███████╗   ██║   ██║  ██║██████╔╝
 ╚══╝╚══╝ ╚══════╝╚═╝  ╚═╝  ╚═══╝  ╚══════╝   ╚═╝   ╚═╝  ╚═╝╚═════╝

Browser control infrastructure for AI agents.


weavetab @weavetab/skills Docs Changelog


WeaveTab is a browser control platform built for AI agents. The MCP server at its core connects any Chromium-based browser, Chrome, Edge, Brave, to any MCP-compatible agent runtime through a structured protocol layer. Agents call tools. The server translates them into Chrome DevTools Protocol commands and returns structured output against a live, persistent browser session.

The platform extends beyond the MCP server. WeaveTab ships a pre-built skills library for common browser flows, an SDK for building on top of the platform, and has a native browser extension and a purpose-built AI agent in active development.


How It Works

The MCP server holds an open CDP session to a running Chromium instance. When an agent calls a tool, navigate, click, extract, evaluate, the server translates it into the appropriate CDP command sequence and returns structured output. Sessions persist across calls. Tabs are real. There is no screenshot pipeline, no DOM heuristic layer, no virtual display.


Platform

Product Install Description Status
WeaveTab MCP npm i -g weavetab MCP server. Exposes Chrome, Edge, and Brave as structured, agent-callable browser tools via CDP. stable
WeaveTab Skills npx @weavetab/skills Pre-built browser action library. Scraping, form interaction, and navigation flows, composable and agent-ready. stable
WeaveTab SDK npm i @weavetab/sdk Developer layer for extending the platform and building custom browser tools. in development
WeaveTab Extension coming soon Native browser extension with enhanced control surface, cross-origin coordination, and persistent injection. planned
WeaveTab Agent coming soon Purpose-built AI agent with deep integration across the full WeaveTab platform. planned

Quickstart

MCP Server

npm install -g weavetab
{
  "mcpServers": {
    "weavetab": {
      "command": "weavetab",
      "args": ["start"]
    }
  }
}

Your agent now has a live Chromium browser. Navigate, click, extract, and evaluate across any page, any tab, any session.

Skills

npx @weavetab/skills

Repositories

Repository Description
weavetab/mcp-builder MCP server source. Tool definitions, CDP command layer, session registry.
weavetab/skills Skills library source. Pre-composed browser flows, agent-ready.
weavetab/sdk SDK source. Developer surface for extending the platform. In development.

Design Rationale

MCP as the transport. The Model Context Protocol gives agents a typed, discoverable interface to tools. Any MCP-compatible runtime connects to WeaveTab with no adapter code. The server is model-agnostic by design.

CDP as the control layer. Chrome DevTools Protocol provides unmediated access to what the browser is actually doing. Clicks land where CDP says they land. Evaluations run in the real page context. Network events are real network events. The control surface is exact.

Chromium as the target. Chrome, Edge, and Brave all expose the same CDP surface. WeaveTab targets the protocol, not the product. Whichever Chromium-based browser is running is the one the agent drives.


Resources

Documentation . Changelog . weavetab.dev


built by @fy2ne

About

wt`s readme

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors