Board WebMCP

Use this skill to operate the native board demo through @webmcp-bridge/local-mcp.

Prerequisites

• - uxc is installed and available in PATH.
• INLINECODE3 is installed and available in PATH.
• Network access to https://board.holon.run.
• On a fresh machine, or under an isolated HOME, install Playwright browsers first with npx playwright install.
• For local board development, point the setup script at http://127.0.0.1:4173.

Core Workflow

1. 1. Ensure the fixed board link exists:

1. 2. Inspect the bridge and tool schema before calling tools:

1. 3. Read current board state:

1. 4. Apply updates with structured inputs:

1. 5. When a human is editing or reviewing the same board live:

Default Target

The default public target is:

CODEBLOCK0

The default board profile path is:

CODEBLOCK1

Use the helper script to refresh the link for the public deployment:

CODEBLOCK2

Use the helper script to point the link at local development instead:

CODEBLOCK3

If the bridge fails to start on a fresh machine or inside an isolated HOME, install Playwright browsers in that environment first:

CODEBLOCK4

Guardrails

• - board.holon.run is a shared demo. Writes are visible on the board surface and persisted in browser storage for that profile.
• Prefer explicit bridge.session.mode.set over relying on a new launcher invocation to change runtime mode.
• Before collaborative editing, confirm the runtime is actually headed.
• If the human closes that window manually, the headed owner session ends. The next board-webmcp-cli bridge.open starts a new headed session on the same profile.
• Keep the board profile isolated from other sites.
• Use JSON output for automation. Do not depend on human-formatted text output.

References

• - Common command patterns:

• - Link creation helper: