Membership lesson · Build Your Jarvis · Module 9 — The plug socket (MCP)

Wire the socket — first connection

The socket gets built — and proven without a single guest tool used in anger. core/mcp/ arrives with the client on the official SDK, talking to local servers the app launches as child processes it owns; the socket panel where servers are added by member-pasted launch config only, connected and disconnected with one control, every discovered tool's full label readable before anything else happens; and the registry hand-off that is the module's whole thesis — foreign tools land in the Module 6 registry under server-prefixed names, default ask-first, structurally barred from always-allow, governed by the card and journal with zero new gate code. First guest: the browser server, npx-launched — connected, labels read at the door, tools visible enough for Jarvis to name them in chat — and then the plug pulled: process dead, tools gone from the toolbox mid-sentence, an honest nothing's-plugged-in answer. The browsing waits for 9.3; today is the door, the rules, and the off switch, in that order, as ever.

This lesson ships with the paid path. Checkout isn't live yet — start with the free projects (Ground Zero + Off the Grid), or join the waitlist.