Installation

Install from source with Bun. You need Bun plus a Chromium the engine can launch (Chromium 152 or newer), or borrow your driver's browser over CDP instead.

Prerequisites

• Bun — the toolchain. Get it at bun.sh.
• Chromium 152+ — any of chromium, google-chrome, or google-chrome-stable on PATH, or point CHROMIUM_PATH at the binary.
• No account, no registry service, nothing hosted.

Install from source

git clone <repo> agent-webmcp && cd agent-webmcpbun installbun run gate        # deterministic checks — green or stopbun run compile     # dist/agent-webmcp, standalone binary

Release binaries (per-OS, no registry) attach to GitHub releases from 0.1.0 on. Until then, the binary you just compiled is the install: put dist/agent-webmcp on your PATH.

export PATH="$PWD/dist:$PATH"agent-webmcp --version   # expect 0.1.0

Verify the install

agent-webmcp doctor      # environment reportagent-webmcp mcp list    # the 7 served tools

doctor prints a JSON environment report (Bun version, platform, Effect version). If open later fails with no chromium executable on PATH, install Chromium or set CHROMIUM_PATH to the binary.

Add it as an MCP server

{  "mcp": {    "agent-webmcp": {      "command": ["agent-webmcp", "mcp", "serve"]    }  }}

Pin the registry root in the server entry so every spawned server resolves identically (some harnesses spawn per-call servers with varying working directories):

{  "mcp": {    "agent-webmcp": {      "command": [        "agent-webmcp",        "mcp",        "serve",        "--registry",        "/abs/path/.agent-webmcp/registry"      ]    }  }}

Then read the version-matched contract with agent-webmcp skill show. See Configuration for root resolution order.