SOLGPT — Agent Connect

Recommended Grok-bot entry for on-device wallet create + WebMCP trading.

Open SPA /connect (WebMCP browser) or this static page.
List tools: document.modelContext / navigator.modelContextTesting.listTools().
Call solgpt.create_wallet — Connect / SIWX UI. Keys stay on-device. Never print keys.
Call solgpt.get_wallet + solgpt.get_session — pubkey + session booleans only.
Trade: solgpt.quote_swap → solgpt.stage_swap → user confirms. No silent spend.
HTTP POST /mcp is inspect/quote oriented; page WebMCP tools are primary for wallet create.

Tools

solgpt.create_wallet
solgpt.get_wallet
solgpt.quote_swap
solgpt.stage_swap
solgpt.get_session
solgpt.agent_status

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.js with data-packs="c2pa,mcp-server-client" and data-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. Prefer /connect / /agent/connect.md for wallet create + WebMCP trading.

$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.