Artifacts for Grok Build

Grok Build works in your terminal, so what it makes ends up in a file or a scrollback. thing gives it a publish step: Grok writes the page, calls one tool, and returns a link you can send to someone who will never open the repository.

Already connected? Publish your first artifact

Connect thing to Grok Build

npx -y @unravel-tech/thing@latest login
grok mcp add thing -- npx -y @unravel-tech/thing@latest mcp

Or declare it in ~/.grok/config.toml (add --scope project to the command above to write .grok/config.toml in the repository instead):

[mcp_servers.thing]
command = "npx"
args = ["-y", "@unravel-tech/thing@latest", "mcp"]

Grok also picks up MCP servers already defined in ~/.claude.json, .cursor/mcp.json or a project .mcp.json, so if thing is set up there it may already be connected. Run grok inspect to see which servers loaded, and grok mcp doctor if thing does not appear.

Publish your first artifact

Paste this into Grok Build. It creates a real artifact; no existing file is required.

Your first-publish prompt

Use thing’s whoami tool to confirm my account and team. Create a small self-contained HTML report, let me review it, then call push_artifact with inline content, filename first-thing.html, and name first-thing. Omit visibility to use the workspace default. Return the URL and its visibility.

The agent should return a thing URL. Open it while signed in and confirm the report is there. Check Share before sending it. Personal artifacts open for anyone with the link; to keep a report restricted, push it to a team, where artifacts default to team-only and you can invite people one by one.

For your next report, use the same name to add a version at the same URL.

Something not working?

Check npx --version, then run npx -y @unravel-tech/thing@latest whoami on the machine running your agent. If sign-in is missing, run npx -y @unravel-tech/thing@latest login there and restart the agent. For MCP, confirm thing’s tools appear before asking it to publish. Never put credentials in a prompt or a committed config.

Try the direct terminal command or upgrade an older CLI.

Not using Grok Build for everything?

The same artifacts work from every other agent, and from CI. See artifacts for any coding agent for Claude Code, Aider, Cline, shell tools, and pipelines, and for why a page that outlives the session it came from is worth the extra step of publishing.

Check your published artifacts Choose another setup