Board WebMCP

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

Prerequisites

Core Workflow

  1. Ensure the fixed board link exists:
    • command -v board-webmcp-cli
    • if missing or pointed at the wrong URL, run skills/board-webmcp/scripts/ensure-links.sh
  2. Inspect the bridge and tool schema before calling tools:
    • board-webmcp-cli -h
    • board-webmcp-cli nodes.list -h
    • board-webmcp-cli nodes.upsert -h
  3. Read current board state:
    • non-collaborative automation: board-webmcp-cli nodes.list, board-webmcp-cli edges.list
    • collaborative visible session:
      • board-webmcp-cli bridge.session.mode.set '{"mode":"headed"}'
      • board-webmcp-cli bridge.open
      • board-webmcp-cli nodes.list
      • board-webmcp-cli edges.list
  4. Apply updates with structured inputs:
    • board-webmcp-cli diagram.export format=json
    • collaborative visible session should keep the same runtime in headed
    • board-webmcp-cli nodes.upsert '{"nodes":[{"label":"Fraud Service","kind":"service"}]}'
    • board-webmcp-cli edges.upsert '{"edges":[{"sourceNodeId":"gateway","targetNodeId":"orders","protocol":"grpc"}]}'
    • board-webmcp-cli layout.apply mode=layered
    • board-webmcp-cli diagram.export format=json
  5. When a human is editing or reviewing the same board live:
    • check current state with board-webmcp-cli bridge.session.status
    • if needed, switch to headed with board-webmcp-cli bridge.session.mode.set '{"mode":"headed"}'
    • board-webmcp-cli bridge.open
    • keep all reads and writes on board-webmcp-cli for that same collaborative session
    • board-webmcp-cli selection.get
    • board-webmcp-cli bridge.close
    • if the human closed the board window manually, the headed owner session has ended; run board-webmcp-cli bridge.open again to start a new headed session on the same profile

Default Target

The default public target is:

https://board.holon.run

The default board profile path is:

~/.uxc/webmcp-profile/board

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

skills/board-webmcp/scripts/ensure-links.sh

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

skills/board-webmcp/scripts/ensure-links.sh --url http://127.0.0.1:4173

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

npx playwright install

Guardrails

References