@weavetab/mcp 2.5.0-beta.1 → 2.5.0-beta.2

package/mcp.json

@@ -1,18 +1,20 @@
 {
   "name": "@weavetab/mcp",
   "mcpName": "io.github.weavetab/mcp",
-  "version": "2.5.0-beta.1",
-  "description": "Weavetab MCP — Production-grade browser automation MCP server with direct Chrome DevTools Protocol (CDP) control. Direct socket transport, zero WebDriver/Node.js wrapper overhead, deterministic state execution.",
+  "version": "2.5.0-beta.2",
+  "description": "Weavetab MCP — Direct Layer 0 interface for AI agents across web and desktop applications. Direct socket transport, zero wrapper overhead, deterministic state execution.",
   "icon": "icon.png",
   "author": "fy2ne",
   "license": "AGPL-3.0-only",
-  "homepage": "https://weavetab.dev",
+  "homepage": "https://github.com/weavetab/mcp",
   "repository": "https://github.com/weavetab/mcp",
   "keywords": [
     "weavetab",
     "mcp",
     "model context protocol",
     "browser automation",
+    "electron automation",
+    "desktop automation",
     "chrome devtools protocol",
     "cdp",
     "ai agent",
@@ -714,10 +716,10 @@
         "default": 0,
         "description": "Chrome DevTools Protocol attach port"
       },
-      "disableExtensions": {
+      "extension": {
         "type": "boolean",
-        "default": false,
-        "description": "Disable Weavetab Chrome extension integration"
+        "default": true,
+        "description": "Enable Weavetab Chrome extension integration"
       },
       "maxTabs": {
         "type": "number",

package/package.json

@@ -1,10 +1,14 @@
 {
   "name": "@weavetab/mcp",
-  "version": "2.5.0-beta.1",
-  "description": "A production-grade local MCP server for AI browser automation via Chrome DevTools Protocol. No extensions. No cloud. Full control.",
-  "author": "fy2ne",
+  "version": "2.5.0-beta.2",
+  "description": "Direct Layer 0 interface for AI agents across web and desktop applications. No WebDriver. No cloud. Pure control.",
+  "author": {
+    "name": "fy2ne",
+    "email": "hello@fy2ne.me",
+    "url": "https://fy2ne.me"
+  },
   "license": "AGPL-3.0-only",
-  "homepage": "https://Weavetab.dev",
+  "homepage": "https://github.com/weavetab/mcp",
   "repository": {
     "type": "git",
     "url": "https://github.com/weavetab/mcp.git"
@@ -17,6 +21,8 @@
     "mcp",
     "model context protocol",
     "browser automation",
+    "electron automation",
+    "desktop automation",
     "ai agent",
     "claude mcp",
     "cursor mcp",
@@ -74,7 +80,7 @@
     "start": "node dist/index.js",
     "prepublishOnly": "npm run verify && npm run build",
     "test": "node --experimental-vm-modules node_modules/jest/bin/jest.js",
-    "test:unit": "node --import tsx/esm --test \"tests/unit/cache.test.ts\" \"tests/unit/delta.test.ts\" \"tests/unit/sessionMemory.test.ts\" \"tests/unit/trail.test.ts\" \"tests/unit/walker.test.ts\" \"tests/unit/burst.test.ts\" \"tests/unit/navigate.test.ts\" \"tests/unit/select.test.ts\" \"tests/unit/design_extract.test.ts\" \"tests/unit/plugin.test.ts\"",
+    "test:unit": "node --import tsx/esm --test \"tests/unit/cache.test.ts\" \"tests/unit/delta.test.ts\" \"tests/unit/sessionMemory.test.ts\" \"tests/unit/trail.test.ts\" \"tests/unit/walker.test.ts\" \"tests/unit/burst.test.ts\" \"tests/unit/navigate.test.ts\" \"tests/unit/select.test.ts\" \"tests/unit/design_extract.test.ts\" \"tests/unit/plugin.test.ts\" \"tests/unit/electron.test.ts\"",
     "test:e2e": "tsx tests/e2e/smoke_test.ts"
   },
   "dependencies": {

package/server.json

@@ -2,18 +2,18 @@
   "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
   "name": "io.github.weavetab/mcp",
   "title": "Weavetab MCP",
-  "description": "A production-grade local MCP server for AI browser automation via Chrome DevTools Protocol. No extensions. No cloud. Full control.",
+  "description": "Direct Layer 0 interface for AI agents across web and desktop applications. No WebDriver. No cloud. Pure control.",
   "repository": {
     "url": "https://github.com/weavetab/mcp",
     "source": "github"
   },
-  "version": "2.5.0-beta.1",
+  "version": "2.5.0-beta.2",
   "packages": [
     {
       "registryType": "npm",
       "registryBaseUrl": "https://registry.npmjs.org",
       "identifier": "@weavetab/mcp",
-      "version": "2.5.0-beta.0",
+      "version": "2.5.0-beta.2",
       "transport": {
         "type": "stdio"
       },

package/docs/DEV_MODE.md

@@ -1,68 +0,0 @@
-# Weavetab Developer Mode (devMode) & Plugin Profiling Guide
-
-This guide explains Developer Mode (`devMode`), how tool execution timing (`execution_ms`) works, and how it empowers **`weavetab-plugin` developers** and AI agents to profile performance.
-
----
-
-## Enabling Developer Mode
-
-Developer Mode can be enabled in two ways:
-
-1. **Via Configuration (`~/.weavetab/config.json` or `.weavetab/config.json`)**:
-   ```json
-   {
-     "devMode": true
-   }
-   ```
-
-2. **Via Environment Variable**:
-   ```bash
-   WEAVETAB_DEV=1 node dist/index.js
-   ```
-
----
-
-## What Does `devMode` Add?
-
-When `devMode` is active, Weavetab exposes rich execution metadata, visual debugging tools, and mission logging without altering underlying tool execution behavior.
-
-### 1. `execution_ms` & Tool Performance Profiling
-
-In `devMode`, every tool response automatically includes an **`execution_ms`** field:
-
-```json
-{
-  "success": true,
-  "execution_ms": 14,
-  "result": { ... }
-}
-```
-
-* **Purpose**: Measures the exact millisecond duration required to process and complete that specific tool call.
-* **Essential for Plugin Developers**: Allows community developers building custom Weavetab plugins to profile their handlers, measure bottleneck latency, and optimize tool responsiveness.
-* **Agent Context Awareness**: AI agents and users reading tool outputs can monitor tool performance in real time.
-
-### 2. Extension Visual Overlays & Tool Calls
-
-* **Extension Visuals**: Renders real-time tool execution badges and `toolcalls` counters directly within the extension overlay.
-* **Trajectory & Hitbox Inspection**: Visualizes pointer paths, click target bounding boxes, and action status badges during execution.
-
-### 3. Mission Logs (`/logs/`)
-
-* For every completed mission, Weavetab generates a structured mission log file inside `/logs/` (`~/.weavetab/logs/`).
-* Contains full step-by-step tool traces, `execution_ms` timing distributions, and action histories for auditing and debugging.
-
----
-
-## Plugin Performance Profiling
-
-Developer Mode is especially valuable for community developers creating Weavetab plugin packages.
-
-* **Profiling Custom Tool Handlers**:
-  When developing a plugin, enabling `devMode` (`WEAVETAB_DEV=1`) allows you to inspect the `execution_ms` timer on every custom tool response to benchmark performance and optimize your code before publishing.
-* **Manifest & Permissions**:
-  Plugins define their metadata, permissions, and entry points in a `weavetab.json` manifest.
-* **Marketplace Screenshots (`/images/`)**:
-  Plugins can include an `/images` directory with screenshots and logos for display on the official Weavetab Marketplace website (`website/`).
-
-> 📖 For full details on building, packaging, and publishing plugins, see [docs/PLUGINS.md](PLUGINS.md).