@particle-academy/agent-integrations 0.9.0 → 0.9.1

package/README.md

@@ -1,5 +1,7 @@
 # @particle-academy/agent-integrations
 
+[![Fancified](art/fancified.svg)](https://particle.academy)
+
 MCP-driven agent presence in collab sessions. Each open session gets a **micro-MCP server** running in-page; agents (in-browser or external via relay) connect to it and act as participants — adding sticky notes, drawing, moving items, leaving cursor trails.
 
 Also ships the **agent UX surface**: a chat-and-tool-log panel, an on-canvas presence cursor, and a brief activity highlight for items the agent just touched.
@@ -173,6 +175,12 @@ shuttles JSON-RPC frames — it doesn't run tools or hold state.
 - **`docs/relay-protocol.md`** — the on-the-wire JSON envelope, with notes on
   the three transports the protocol supports (Reverb, WebRTC, SSE+POST).
 
+The agent at the far end needs an MCP client. Beyond pasting the session URL
+into an existing one (Claude Code, Cursor, …), there's
+**[`mcp-relay-client`](https://github.com/Particle-Academy/mcp-relay-client)** —
+a single-file, zero-dependency client (bash / Python / TS / Go) built for these
+relay sessions: `curl -O …/connect.sh && bash connect.sh "<session-url>" tools`.
+
 Pattern (Reverb):
 
 ```ts

package/docs/agent-hookable-demos.md

@@ -41,7 +41,10 @@ Three pieces. You write zero of them yourself if you follow this guide:
    complete Laravel controller).
 
 3. **The agent's client.** Out of your control — visitors paste your session
-   URL into whatever MCP client they already use.
+   URL into whatever MCP client they already use. If they don't have one, point
+   them at [`mcp-relay-client`](https://github.com/Particle-Academy/mcp-relay-client):
+   a single-file, zero-dependency client (bash / Python / TS / Go) they download
+   and aim at the session URL.
 
 ## End-user UX
 
@@ -54,7 +57,9 @@ This is what visitors actually experience. Every demo follows the same shape:
 4. The page mints a per-session token, registers it with the relay, and shows
    a copyable share URL.
 5. Visitor pastes the URL into their MCP client (`.mcp.json` for Claude Code,
-   Cursor's MCP settings, etc.). The client connects to the relay.
+   Cursor's MCP settings, etc.), or downloads
+   [`mcp-relay-client`](https://github.com/Particle-Academy/mcp-relay-client)
+   and aims it at the URL. The client connects to the relay.
 6. Agent calls tools → tools mutate the host page's React state → visitor
    watches the surface change in real time. Optional: agent cursor + tool-call
    feed render alongside.

package/docs/relay-server.md

@@ -18,6 +18,27 @@ across restarts.
   Code → the relay is hosted somewhere reachable from both the browser and the
   agent's machine.
 
+## Connecting a client to a session
+
+This doc covers running the **broker**. The agent connects from the other end
+with an MCP **client** pointed at a session URL. Two options:
+
+- **A generic MCP client you already have** — paste the session URL into Claude
+  Code's `.mcp.json`, Cursor's MCP settings, Claude Desktop, etc.
+- **[`mcp-relay-client`](https://github.com/Particle-Academy/mcp-relay-client)** —
+  a super-lite, **single-file, zero-dependency** client in bash / Python / TS /
+  Go, purpose-built for these relay sessions. Grab the one you have a runtime for
+  and point it at the session URL:
+
+  ```bash
+  curl -O https://raw.githubusercontent.com/Particle-Academy/mcp-relay-client/main/connect.sh
+  bash connect.sh "https://host/agent-playground?session=ABC&token=XYZ" tools
+  bash connect.sh "<session-url>" call whiteboard_add_sticky '{"x":300,"y":200,"text":"hi"}'
+  ```
+
+  It derives the relay endpoints, session id, and token from the URL and runs the
+  full `initialize` → `tools/list` → `tools/call` handshake for you.
+
 ## Three ways to run it
 
 ### 1. `npx` — local dev / one-off prod

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@particle-academy/agent-integrations",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "description": "MCP-driven agent presence in collab sessions: per-session micro-MCP server, pluggable bridges to fancy-* packages, and agent UX components (panel + on-canvas cursor).",
   "repository": {
     "type": "git",
@@ -221,11 +221,11 @@
     "fancy"
   ],
   "peerDependencies": {
-    "@particle-academy/fancy-artboard": "^0.1.0",
-    "@particle-academy/fancy-flow": "^0.2.0 || ^0.3.0",
-    "@particle-academy/fancy-sheets": "^0.1.0",
-    "@particle-academy/fancy-slides": "^0.1.4 || ^0.2.0 || ^0.3.0 || ^0.4.0 || ^0.10.0",
-    "@particle-academy/fancy-whiteboard": "^0.1.0",
+    "@particle-academy/fancy-artboard": ">=0.1.0",
+    "@particle-academy/fancy-flow": ">=0.2.0",
+    "@particle-academy/fancy-sheets": ">=0.1.0",
+    "@particle-academy/fancy-slides": ">=0.1.4",
+    "@particle-academy/fancy-whiteboard": ">=0.1.0",
     "react": "^18.0.0 || ^19.0.0",
     "react-dom": "^18.0.0 || ^19.0.0"
   },
@@ -247,8 +247,8 @@
     }
   },
   "devDependencies": {
-    "@particle-academy/fancy-slides": "^0.10.0",
-    "@particle-academy/fancy-whiteboard": "^0.1.5",
+    "@particle-academy/fancy-slides": "^0.12.0",
+    "@particle-academy/fancy-whiteboard": "^0.2.0",
     "@types/node": "^22.0.0",
     "@types/react": "^19.0.0",
     "@types/react-dom": "^19.0.0",