Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

docs(x-grok): log order 035 Grok Bot connector reference as done with its commit and the unshipped-to-production caveats

nirholas4e492ed83309
diff --git a/prompts/finish/_context/x-grok-PROGRESS.md b/prompts/finish/_context/x-grok-PROGRESS.md
index 2b042fa73..7754f81a7 100644
--- a/prompts/finish/_context/x-grok-PROGRESS.md
+++ b/prompts/finish/_context/x-grok-PROGRESS.md
@@ -86,3 +86,8 @@ Added `agent-get-started`, `daily-3d-brief`, `asset-pack`, `avatar-from-photo` t
- `public/.well-known/mcp.json` now has a `clients` block (`claude`, `chatgpt`, `cursor`, `vscode`, `grok-bot`) with recommended server, auth mode and settings; the file is hand-maintained (the generator only refreshes resources and prompts), so it was edited directly and re-formatted by `build-mcp-surfaces.mjs`. Documented in `docs/mcp.md` as a three.ws extension.
- `/grok` added to the curated `site.llms` Developers group in `data/pages.json`; `public/llms.txt` now lists "three.ws for Grok" beside the connect line. `npm run build:pages` passes.
- New `tests/mcp-directory.test.js` (9 tests): shape, `clients`, and every endpoint routed (route table or `api/<name>.js` through the filesystem phase). `audit:mcp`, `audit:docs`, `check:rules` clean.
+
+## 2026-10-09: order 035 (docs/grok-bot.md) done
+
+- Shipped `docs/grok-bot.md` in 434e50b25 (route `/docs/grok-bot`): connector settings per sign-in mode, which server to pick, the links contract, jobs and idempotency, rate limits and install tokens, scoped keys and the spend rule, the prompts, and a troubleshooting table covering every failure line `scripts/mcp-client-probe.mjs` can emit plus the runtime errors (`-32029`, `-32003`, idempotency codes). Linked from `docs/start-here.md`, a new Grok Bot section in the `docs/mcp.md` client list, and a `STRUCTURE.md` row; `data/pages.json` and `data/changelog.json` entries added, generated feeds rebuilt. `npm run audit:docs` clean, `npm run check:rules` OK.
+- Samples: initialize, session id, `tools/list`, `search_catalog` and `forge_free` ran against production as written. `idempotency_key`, `get_job`, `prompts/list`, `POST /api/mcp-studio/install` and `?auth=oauth` are not in the production build yet (production answers 200 to `?auth=oauth`, 404 to install, empty prompts, rejects `idempotency_key`), so they were run against a local server instead, where `npm run probe:mcp-clients -- --only grok` passes (15 tools, 4 prompts, OAuth ok) while the same command against production fails the sign-in checks until the next deploy. Local generation could not complete (no S3/LLM env), so the idempotent replay shape rests on `docs/mcp-studio.md` and its tests rather than a fresh run.