Grok

Full steps: connect.md · Quickstart.

The Grok harness lives in valorbrain-harness/grok: a contract markdown and an example mcp.example.toml. Nothing of our tenant is in that repo.

Token

npx -y @valorbrain/cli@latest init --agent --agent-caller grok --json

Use the mcp_token (vbm_…); MCP accepts only vbm_. With an account, create the token under Settings → MCP tokens.

Hosted MCP via stdio

# ~/.grok/config.toml
[mcp_servers.valorbrain]
command = "npx"
args = ["-y", "@valorbrain/cli", "mcp"]

npx -y @valorbrain/cli mcp uses the token saved by init; to pass a different one, append "--token", "<vbm_…>" to args or set VALORBRAIN_MCP_TOKEN. The old example with @valorbrain/connect as the command is wrong: @valorbrain/connect is the installer, not the server.

Contract and install

Full install through the installer (MCP server, rules and hooks):

npx -y @valorbrain/connect@latest --token <vbm_…> --harness grok

Or install just the contract from a clone of the harness repo:

./install.sh grok

install.sh in that repo is per-harness (grok, zcode, …). It writes the contract block into ~/.grok/AGENTS.md and warns when config.toml has no mcp_servers.valorbrain entry yet. It does not call a valorbrain setup CLI, because that CLI command is not published.

Verify

Call memory_prepare. To keep the account beyond 30 days, the human runs npx -y @valorbrain/cli init --email <email>.