board-webmcp

Category: Tools & Productivity | Uploader: holon-run | Downloads: 0 | Version: v1.0（Latest）

Connect to the native board demo through local-mcp and UXC links. Use when the user wants to inspect or edit the shared board at board.holon.run or a local board instance through browser WebMCP.

Changelog: Source: GitHub https://github.com/holon-run/webmcp-bridge

Directory Structure

Current level: skills/board-webmcp/

📁 agents/
- 📄 openai.yaml 293 B
📁 references/
- 📄 usage-patterns.md 1.8 KB
📁 scripts/
- 📄 ensure-links.sh 1.9 KB
- 📄 validate.sh 1.6 KB
📄 SKILL.md 4.1 KB

SKILL.md

---
name: board-webmcp
description: Connect to the native board demo through local-mcp and UXC links. Use when the user wants to inspect or edit the shared board at board.holon.run or a local board instance through browser WebMCP.
---

# Board WebMCP

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

## Prerequisites

- `uxc` is installed and available in `PATH`.
- `npx` 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. Ensure the fixed board links exist:
   - `command -v board-webmcp-cli`
   - `command -v board-webmcp-ui`
   - 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-ui bridge.open`, then `board-webmcp-ui nodes.list`, `board-webmcp-ui edges.list`
4. Apply updates with structured inputs:
   - non-collaborative automation may use `board-webmcp-cli`
   - collaborative visible session should keep all MCP calls on `board-webmcp-ui`
   - `board-webmcp-ui nodes.upsert '{"nodes":[{"label":"Fraud Service","kind":"service"}]}'`
   - `board-webmcp-ui edges.upsert '{"edges":[{"sourceNodeId":"gateway","targetNodeId":"orders","protocol":"grpc"}]}'`
   - `board-webmcp-ui layout.apply mode=layered`
   - `board-webmcp-ui diagram.export format=json`
5. Switch to the UI link when a human is editing or reviewing the same board live:
   - `board-webmcp-ui bridge.open`
   - keep all reads and writes on `board-webmcp-ui` for that same collaborative session
   - `board-webmcp-ui selection.get`
   - `board-webmcp-ui bridge.close`
   - if the human closed the board window manually, run `board-webmcp-ui bridge.open` again to recreate the headed page in the same bridge session
   - if the window flashes open and immediately disappears in an automated or one-shot execution environment, ask the user to run `board-webmcp-ui bridge.open` in their own interactive terminal first

## Default Target

The default public target is:

```bash
https://board.holon.run
```

The default board profile path is:

```bash
~/.uxc/webmcp-profile/board
```

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

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

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

```bash
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:

```bash
npx playwright install
```

## Guardrails

- `board.holon.run` is a shared demo. Writes are visible on the board surface and persisted in browser storage for that profile.
- Prefer `board-webmcp-ui` when a human and AI need to inspect the same diagram state together.
- When a human and AI are sharing one visible board session, do not mix `board-webmcp-cli` into the same profile. Keep the session on `board-webmcp-ui`.
- Use `board-webmcp-ui bridge.open` to reveal the current headed browser session before collaborative editing.
- If the human closes that window manually, `board-webmcp-ui bridge.open` should reopen it in the same headed session.
- In constrained execution environments, `bridge.open` may not keep the UI session alive after the command exits. In that case, the user should run `board-webmcp-ui bridge.open` directly in their local terminal and keep that session open.
- 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:
  - `references/usage-patterns.md`
- Link creation helper:
  - `scripts/ensure-links.sh`

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

board-webmcp

Directory Structure

SKILL.md

Report

Notice