sbuilder-mcp-tools

Create or extend a group file under src/tools/*.ts exporting registerXTools(server, ctx), then register it in src/server.ts, docs/tools.md, docs/tools.vi.md, both README tool tables, and add a test under test/. Run npm run build && npm test && npm run smoke before claiming it works.

A writing tool must accept a dry_run parameter defaulting to true and return { dry_run: true, would_send: redact(...) }. The redact() helper keys off field names rather than value shapes, so token format changes do not leak secrets.

stdout is the MCP protocol channel, so a console.log corrupts the message stream for every client. The symptom appears as a client parse failure rather than an error in the server, which is why only console.error is allowed.

credentialFor(path) in src/transport/credential.ts routes by prefix: /api/v1 uses the SB_TOKEN key, /api/auth uses none, and everything else uses the session JWT. The session token must be read per use via ctx.session.token() because it rotates roughly every 15 minutes.

doc.apply only mutates the local document, so humans watching the live editor see nothing happen. PageSession.applyAndPublish applies patches locally and puts the batch on the live-edit wire when the agent has joined a room.

No, src/catalog/*.generated.ts files must never be hand-edited. Regenerate them with WB_REPO=/path/to/web_builder npm run codegen, following the separate sbuilder-codegen skill.