# Grok

> Connect MCP Bond once for Grok chat and Grok Build.

Connect Valency once to your Grok account for Grok chat and Grok Build. The direct MCP option below covers Grok Build sessions using a separate login, API key, or proxy.

## Quick setup

Follow the current, tested steps on [the Grok setup page](https://docs.valency.io/guides/xai/). The sections below cover additional cases and troubleshooting.

## Using it in Grok Build

Restart an open Grok Build session so it loads the account connector, then check `/mcps` and ask it to call Valency's `list_sources` tool. If Valency does not appear, make sure Grok Build uses the same Grok account as the browser.

If Grok Build cannot load that account connector, use the **direct MCP connection** prompt in the setup section. To add it yourself instead, check `/mcps` and run `grok mcp list` first. If `valency` is already configured, do not add it again. Otherwise run:

```bash
grok mcp add --transport http valency https://mcp.valency.io/
```

Start or restart Grok Build. Open `/mcps` and select `valency`. If it is disabled, press <kbd>Space</kbd> to enable it, then press <kbd>i</kbd> to sign in if needed. Ask Grok Build to call `list_sources`.

## Organization accounts

Grok Business and Enterprise may require an administrator to provision custom MCP connectors. If **Custom** is unavailable under **New Connector**, ask your Grok administrator.

## Troubleshooting

If Grok chat cannot see the tool, confirm Valency is connected in Grok Plugins, then try a new chat. A returned source list from `list_sources` confirms the connection; a listed connector alone does not.

See [Troubleshooting](https://docs.valency.io/help/troubleshooting.md) for other connection issues or [report an issue](https://docs.valency.io/help/reporting-issues.md).