---
title: Connect Grok
description: Add looot as a connector in Grok, through the web app, an enterprise admin flow, the CLI, or the xAI API. Not tested by hand yet.
sidebar:
  label: Grok
---

<ClientHeader id="grok" />

:::note
Not tested by hand yet. Steps follow xAI's own docs, linked in Sources below; if a menu has
moved, that page is the reference.
:::

Grok reaches looot through a connector, added from grok.com, an admin console, the Grok CLI, or
the xAI API.

Before you start you need a looot account. The runs you make spend the organization's balance, so
top up before your first paid run. See [Before your first run](/money#before-your-first-run).

## Personal account, browser sign-in

1. Go to grok.com/connectors and click **New Connector**.
2. Choose **Custom**.
3. Enter the MCP server URL, `https://api.looot.ai/mcp`, and complete the sign-in. The browser
   takes you to looot.ai, where you pick the organization and click **Connect**.

## Business and Enterprise accounts

An admin adds the connector first, then members can use it.

1. At console.x.ai, open your team, then **Grok Business**, then **Connectors**.
2. Click **+ Add Connector**, choose **Other**, and enter `https://api.looot.ai/mcp`.
3. This step needs Team Read-Write access.

## Grok CLI

```bash
grok mcp add --transport http looot https://api.looot.ai/mcp
```

The CLI handles OAuth on first use, opening the browser for the looot.ai consent page.

For a header token instead, in CI or a machine with no browser:

```bash
grok mcp add --transport http looot https://api.looot.ai/mcp \
  --header "Authorization: Bearer $LOOOT_TOKEN"
```

## xAI API (Responses API)

The Responses API takes an MCP tool directly in the request body, sent to
`POST https://api.x.ai/v1/responses`:

```json
{
  "type": "mcp",
  "server_url": "https://api.looot.ai/mcp",
  "server_label": "looot",
  "authorization": "<looot token>"
}
```

There is no browser sign-in on this path; xAI's docs say the token is set in the
`authorization` field, sent in the Authorization header, but they don't say whether that field
takes the raw token or a `Bearer <token>` value. Try the raw token first, since the field name
mirrors the token itself; if it fails, try `Bearer <token>`.

## Check it works

Ask Grok to call [`balance`](/mcp-tools/balance) or [`catalog_overview`](/mcp-tools/catalog-overview). Both are free. A working connection answers
with your available balance, or the catalog's categories and job counts.

## What you see when you connect

On the web and CLI paths, the browser opens looot.ai and shows the consent page: which
organization to bill, which scopes to grant and how long to stay connected. See
[The consent page](/connect#the-consent-page). The API path has no consent page: the token you
pass already carries its scopes and organization.

## Sources

- Connectors: [docs.x.ai/grok/connectors](https://docs.x.ai/grok/connectors)
- Connector management (Business/Enterprise): [docs.x.ai/grok/connector-management](https://docs.x.ai/grok/connector-management)
- Grok CLI, MCP servers: [docs.x.ai/build/features/mcp-servers](https://docs.x.ai/build/features/mcp-servers)
- Remote MCP on the API: [docs.x.ai/developers/tools/remote-mcp](https://docs.x.ai/developers/tools/remote-mcp)

<Related />