# SOLGPT — Agent Connect (WebMCP wallet + trade)

Nav:

- [Home](/agent/index.md)
- [Desk](/agent/desk.md)
- [Pump](/agent/pump.md)
- [Launch](/agent/launch.md)
- [Trade](/agent/trade.md)
- [Tokens](/agent/tokens.md)
- [Markets](/agent/markets.md)
- [Z500](/agent/z500.md)
- [Fire](/agent/fire.md)
- [Crowd](/agent/crowd.md)
- [Trickshot](/agent/trickshot.md)
- [Wallet](/agent/wallet.md)
- [Connect](/agent/connect.md) **(this page)**
- [x402](/agent/x402.md)
- [Clawd bot](/agent/clawdbot.md)
- [Bots](/agent/bots.md)
- [Goal](/agent/goal.md)
- [Computer](/agent/computer.md)
- [Media](/agent/media.md)
- [WebMCP](/agent/webmcp.md)


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

1. Open the SPA [/connect](/connect) (preferred when you have a WebMCP browser) or stay on this static page.
2. List page tools (`document.modelContext` / `navigator.modelContextTesting.listTools()`).
3. Call `solgpt.create_wallet` — opens Connect / SIWX (Phantom embedded, Wallet Standard). **Never prints keys.**
4. Call `solgpt.get_wallet` + `solgpt.get_session` — public address + session booleans only.
5. Trade: `solgpt.quote_swap` → `solgpt.stage_swap` → user/wallet confirms. No silent spend.
6. HTTP `POST /mcp` remains inspect/quote oriented; **page WebMCP tools are the primary wallet-create surface.**

## Tools (page WebMCP)

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

Also live on the SPA: `solana.*`, `solgpt.ask`, `clawd.*`, `x402.*`, `pump.*`.

## Security

- Never print secret keys, mnemonics, seed phrases, or raw JWTs.
- Signing is local. Agents propose; the wallet confirms.
- Related: [Wallet / OWS](/agent/wallet.md), [WebMCP](/agent/webmcp.md).


## What this does and how it works

Two parts sit in front of the origin. Same for these static pages and the React SPA.

1. **Edge/origin injects one line:** a module script at [/.webmcp/bridge.js](/.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.
2. **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](/llms.txt) then [/agent/](/agent/) then call [/mcp](/mcp). Prefer [/connect](/connect) / [/agent/connect.md](/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](/agent/webmcp.md).

SPA desk: [/connect](/connect)