Getting Started

This guide is the shortest path to a working local bridge session.

Choose A Source Mode

Before You Start

Use the bridge only for research, development, testing, and normal authorized user flows. Do not use repository-provided adapters for unauthorized scraping, access-control bypass, or abusive automation against third-party services.

Direct CLI

Run a native site directly:

node packages/local-mcp/dist/cli.js --url https://board.holon.run --headless

Run X through the built-in adapter:

node packages/local-mcp/dist/cli.js --site x --headless --user-data-dir ~/.uxc/webmcp-profile/x

Run Google or Gemini through the built-in adapter:

node packages/local-mcp/dist/cli.js --site google --headless --user-data-dir ~/.uxc/webmcp-profile/google

Run Weibo through the built-in adapter:

node packages/local-mcp/dist/cli.js --site weibo --no-headless --user-data-dir ~/.uxc/webmcp-profile/weibo

Fixed Site Links

For daily usage, prefer one stable uxc link per site:

skills/webmcp-bridge/scripts/ensure-links.sh --name board --url https://board.holon.run
skills/x-webmcp/scripts/ensure-links.sh
skills/google-webmcp/scripts/ensure-links.sh
skills/weibo-webmcp/scripts/ensure-links.sh

This creates commands such as:

First Commands

Check the tool schema first:

<site>-webmcp-cli -h
<site>-webmcp-cli <operation> -h

Inspect the current bridge session:

<site>-webmcp-cli bridge.session.status

If the site needs a visible browser:

<site>-webmcp-cli bridge.session.mode.set '{"mode":"headed"}'
<site>-webmcp-cli bridge.open

Next