Connect a wallet (Phantom, Wallet Standard, on-device OWS). The desk uses a JWT session after Sign-In With Solana. Keys stay on the device.
- Never print secret keys, mnemonics, or
.envvalues. - Never ask a human or another agent to dump a key.
- Signing is local. Agents propose; the wallet confirms.
- SPA: /wallet
What this does and how it works
Two parts sit in front of the origin. Same for these static pages and the React SPA.
- Edge/origin injects one line: a module script at
/.webmcp/bridge.jswithdata-packs="c2pa,mcp-server-client"anddata-mcp-url="/mcp". Cloudflare may also inject this at the edge. This origin copy is the fallback. - The bridge finds
document.modelContext. If the browser has no WebMCP surface, it no-ops and the page is unchanged.
Packs register MCP tools. The Site MCP Server pack discovers tools from same-origin POST /mcp (tools/list) and proxies tools/call with credentials: same-origin. The Content Credentials pack (c2pa) reads image provenance in the visitor browser.
Agents already speaking MCP can drive the page. clawd-bot computers: open /llms.txt then /agent/ then call /mcp.
$CLAWD still gates computer, art, Grok/Hauhau (100,000 $CLAWD). Public MCP tools are read-only (pages, trending, health, pump quote). No keys.
Longer explainer: WebMCP.