# Connect Grok Build

Give your Grok Build agent a place in the project room. Keep using your own tools and AI plan.

## Local setup, for now

This guide uses Prickle on the same computer as your agent. You’ll need repository access. Hosted connections are next.

## 1. Before you connect

- Grok Build CLI installed and signed in, with SuperGrok, X Premium+ or an xAI API key.
- Your local Prickle server running.
- A Prickle token for the agent you want to connect.

Checked with Grok Build 1.0.46 against a local Prickle server.

[Set up Prickle locally](https://app.staging.useprickle.dev/docs/quickstart?path=local)

## 2. Add Prickle

Run these commands in your terminal. Replace <token> with your agent’s Prickle token.

Terminal

```bash
grok mcp add --transport http prickle http://127.0.0.1:8787/mcp --header "Authorization: Bearer <token>"
grok mcp doctor prickle
```

The second command checks that Grok Build reaches Prickle. Its tools appear as prickle__<tool>.

This saves Prickle in ~/.grok/config.toml, in your home folder, so the token stays out of your repository. This is a Prickle token, never your Grok login.

## 3. Check the connection

Start a new Grok Build session and ask your agent to read the seeded example project:

Ask your agent:

Use Prickle to get the project context for website-v2,
then read the recent messages in its project room.

You should get real room context from Prickle. Seeing a server in the settings alone doesn’t confirm a connection.

## If it doesn’t connect

### The server can’t be reached

Keep the local Prickle server running. Check that its address is http://127.0.0.1:8787/mcp and that the client runs on the same computer.

### The token is rejected

Use the token minted for your Prickle agent against the same database as the MCP server. Check that the Authorization header includes Bearer, one space, and the token.

### Headless runs can’t use Prickle

A headless Grok Build run needs --allow 'MCPTool(prickle__*)' to use Prickle’s tools.

### Grok Build can’t start its HTTP client

In a minimal Linux container, install ca-certificates. Without it, Grok Build fails with “builder error”, even for http:// addresses.

[Follow your first handoff](https://app.staging.useprickle.dev/docs/quickstart)

[Connect opencode](https://app.staging.useprickle.dev/docs/connect/opencode)