> For the complete documentation index, see [llms.txt](https://docs.nansen.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nansen.ai/mcp/connectors/grok-bot.md).

# Grok Bot

Ask Grok Bot to add Nansen as a custom MCP connector, then sign in with your Nansen account. No API key needed.

Connect Nansen to Grok Bot by pasting a setup prompt into a chat. Grok Bot adds Nansen as a personal custom connector and gives you a card to sign in with your Nansen account.

Grok Bot is set up differently from [Grok](https://docs.nansen.ai/mcp/connectors/grok.md) on grok.com. You do not use the **New Connector** dialog, and the sign-in goes through Grok Bot's own connector service.

### What you need

A Grok Bot account and a Nansen account. Sign in with the Nansen account whose API credits you want to use.

{% hint style="info" %}
Data-tool calls spend your [Nansen API credits](https://docs.nansen.ai/getting-started/credits.md), not your Grok Bot subscription, and are subject to [rate limits](https://docs.nansen.ai/getting-started/rate-limits.md). One request can trigger several calls. Data tools read data; feedback submission saves a report. Nansen cannot trade, sign transactions, or move assets.
{% endhint %}

### Connect Nansen

You only give Grok Bot a name and the server URL. Grok Bot registers itself with Nansen's sign-in automatically, so leave the custom OAuth client ID, client secret and headers empty.

1. Open Grok Bot and start a chat.
2. Copy the entire prompt below and send it to Grok Bot.

{% code overflow="wrap" %}

```
Add a personal custom MCP connector named "Nansen" with server URL https://mcp.nansen.ai/ra/connector-curated/mcp.

Leave the custom OAuth client ID, client secret and headers empty so it uses the server's normal OAuth sign-in.

Then show me the card to sign in to Nansen so I can approve access myself. Do not ask me to paste a password, API key, authorization code, or token into this chat.

After sign-in, list the available tools. Do not run any data queries yet.
```

{% endcode %}

3. Click **Authenticate** on the card Grok Bot shows. Your browser opens Nansen's sign-in page titled **Connect Nansen to Cursor (Grok Bot)**. Grok Bot's connectors run on Cursor's connector service, so Cursor is named here. The page also notes that sign-in returns to a program on your computer at `localhost:8787`. That program is the Grok Bot app, and the note is expected.
4. Sign in with your Nansen account and click **Allow** to approve access to data and product feedback (`nansen:read`). Return to Grok Bot.
5. Confirm Grok Bot lists the [curated tools](https://docs.nansen.ai/mcp/connectors.md#curated-tools), including `general_search` and `token_info`.

You can also find the connector later in **Connect apps** under **Your plugins**, and click **Authenticate** there.

### Verify your connection

Send this in the same chat:

> Use the Nansen connector to search for the token ETH with general\_search. Run only that search, show the returned data, and report any tool error. Do not look up an address or domain, or run follow-up tools.

`general_search` costs **0 credits**. See [credits per call](https://docs.nansen.ai/mcp/connectors.md#credits-per-call).

Check that Grok Bot actually calls Nansen and returns a tool result without an authentication or tool error. A general answer about ETH or a list of tools does not verify the connection. Search results can change; do not expect a fixed result count.

### Try a research prompt

Once the verification succeeds, type `@` in a chat to attach Nansen, then ask:

* "Use Nansen to find Wintermute."
* "Use Nansen to get token information for USDC on Ethereum."

Connected apps are account-wide in Grok Bot, so every Bot on your account can use Nansen. Grok Bot connects to the same server offering [curated tools](https://docs.nansen.ai/mcp/connectors.md#curated-tools) as ChatGPT, Claude, Grok, and Muse. For tools outside this set, use [Manually connecting to Nansen MCP](https://docs.nansen.ai/mcp/connecting.md) with another MCP client.

### Troubleshooting

| Problem                                                          | What to do                                                                                                                                                        |
| ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Grok Bot asks for an API key, client ID, client secret or header | Ask it to leave them empty and use the server's normal OAuth sign-in. This connector does not need any of them.                                                   |
| Sign-in page shows **Something went wrong**                      | Send the **Request ID** shown on the page to Nansen support.                                                                                                      |
| You click **Allow** but Grok Bot never finishes connecting       | Make sure the Grok Bot app is open on the same computer as the browser, then click **Authenticate** again.                                                        |
| The connector shows **Disabled by team admin**                   | Your team's connector policy blocks it. Ask a team admin to allow it.                                                                                             |
| Sign-in is requested again, or access is denied                  | Click **Authenticate** again and sign in with the intended Nansen account.                                                                                        |
| Grok Bot lists tools but answers without calling Nansen          | Attach Nansen with `@`, ask it to use the Nansen connector, and repeat the verification step.                                                                     |
| Insufficient credits                                             | Check the signed-in account's balance at [Nansen API](https://app.nansen.ai/api?tab=api).                                                                         |
| Rate limit reached                                               | Wait and follow the error's retry guidance.                                                                                                                       |
| Tool error with a request ID                                     | Save the request ID, error text, time, and prompt for Nansen support. Do not share passwords, tokens, authorization codes, or screenshots containing credentials. |

To disconnect, open **Connect apps**, find Nansen under **Your plugins**, and remove it.

Feedback preference reads, submissions and receipt reads cost zero credits. Tool availability depends on the client catalog and permissions. See [product feedback](https://docs.nansen.ai/mcp/connectors.md#product-feedback).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nansen.ai/mcp/connectors/grok-bot.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
