> 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.md).

# Grok

Connect the OAuth-protected Nansen MCP surface in Grok as a custom connector. No API key.

Connect Nansen to Grok to use curated data tools for token and wallet analysis. Sign in with your Nansen account through OAuth. No API key is needed.

### What you need

A Nansen account and a Grok account. Data-tool calls use your Nansen account's API [credits](/getting-started/credits.md) and [rate limits](/getting-started/rate-limits.md).

### Connect Nansen in Grok

1. Open [grok.com/connectors](https://grok.com/connectors). Grok opens **Plugins** on the **Connectors** tab.
2. Click **New**, then **Connector**. In the **New Connector** dialog, choose **Custom**.

   ![Select Custom in the New Connector dialog](https://3666025612-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHE8GKwbmDRKKCMC7hnip%2Fuploads%2Fgit-blob-a36882072e1cebe94116b8be5a5277600bd2d86d%2Fgrok-new-connector.png?alt=media)
3. Enter **Nansen** in **Name** and paste this **Server URL**:

   ```
   https://mcp.nansen.ai/ra/connector-curated/mcp
   ```

   ![Enter Nansen and the production MCP server URL](https://3666025612-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHE8GKwbmDRKKCMC7hnip%2Fuploads%2Fgit-blob-6329da316c730e9c9eb457de7b90422d7c363132%2Fgrok-server-url.png?alt=media)
4. Click **Add Connector**. A sign-in window opens and shows **Connect Nansen to Grok**, with data and product-feedback access (`nansen:read`).
5. Sign in with your Nansen account and click **Allow**. The window closes. You do not enter a client ID, client secret, or scope: Grok registers itself with Nansen's OAuth sign-in automatically.
6. Back in Grok, open **Nansen** under **Connected**. Click **See more** and confirm the [curated tools](/mcp/connectors.md#curated-tools) needed for your task are enabled.
7. Start a chat, type `@Nansen` and pick the connector, then try:

   > Use Nansen's token\_info tool to look up USDC on Ethereum. Show the tool result.

Grok, [ChatGPT](/mcp/connectors/chatgpt.md), and [Claude](/mcp/connectors/claude.md) connect to the same server offering [curated tools](/mcp/connectors.md#curated-tools) and [credit costs](/mcp/connectors.md#credits-per-call).

### Grok Business and Enterprise

For **Grok Business** and **Enterprise**, a team admin provisions the connector in the cloud console before members of the organization can connect their Nansen accounts.

1. Sign in at [console.x.ai](https://console.x.ai), select your team, and open **Grok Business → Connectors**.
2. Click **+ Add Connector**, then select **Other**.
3. Enter `https://mcp.nansen.ai/ra/connector-curated/mcp` and complete any required authentication.
4. After the admin provisions it, members connect their own Nansen accounts on [grok.com/connectors](https://grok.com/connectors).

Adding and removing connectors requires Team Read-Write permissions, typically granted to team admins. If the custom-connector option is missing, ask a team admin to provision it.

### Manage access

The connector uses the Nansen account you selected during sign-in. To sign in again, open the connector and click **Reauthenticate**. To remove it from Grok, click **Disconnect**.

### Rate limits

See [Nansen API rate limits](/getting-started/rate-limits.md).

### Errors and what to do

This surface fails closed. A failed tool call returns a **safe failure message that includes a request ID**. Give that request ID to support. The message does not expose tokens, API keys, account IDs, or internal details.

| What you see                                                                                   | What it means                                                        | What to do                                                                                                |
| ---------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| Sign-in / authorize prompt again                                                               | Missing, expired, or invalid OAuth session                           | Complete consent again with the same Nansen account                                                       |
| Scope / permission denied                                                                      | The session lacks `nansen:read`                                      | Open the connector, click **Reauthenticate**, and approve access again                                    |
| Sign-in window shows **Something went wrong**                                                  | Nansen's sign-in rejected the request                                | Send the **Request ID** shown on the page to support                                                      |
| Grok stays on "Complete authentication in the popup window"                                    | The sign-in window was closed before it finished                     | Click **Cancel**, then add the connector again                                                            |
| Rate limit / try again later                                                                   | Your Nansen plan's request cap was hit                               | Wait, then retry. Honor any retry hint Grok shows                                                         |
| Insufficient credits                                                                           | The signed-in account cannot pay for the tool                        | Add credits or upgrade at [app.nansen.ai](https://app.nansen.ai/account/switch-plans)                     |
| Failed tool call with a request ID                                                             | The tool ran and returned a safe error                               | Copy the request ID and send it to support. Do not send tokens or screenshots of secrets                  |
| Missing tools or names that do not match the [curated tools](/mcp/connectors.md#curated-tools) | Wrong URL, incomplete discovery, or client catalog/permission limits | Confirm the URL is `https://mcp.nansen.ai/ra/connector-curated/mcp`, then check discovery and permissions |
| Tools listed but no data                                                                       | OAuth did not complete, or the account has no remaining credits      | Re-run consent, then check [usage](https://app.nansen.ai/api?tab=usage-analytics)                         |

If a data-tool call fails, keep the **request ID** and follow its retry guidance. For feedback, also preserve the original submission ID and report; do not retry `feedback_not_enabled`. Do not paste API keys or bearer tokens into the chat.

### Need more tools?

Grok connects only through OAuth and the curated tools. For the [full tool catalog](/mcp/connecting/tools.md), connect another MCP client to `https://mcp.nansen.ai/ra/mcp` with a `NANSEN-API-KEY` header. See [Manually connecting to Nansen MCP](/mcp/connecting.md).

Feedback preference reads, submissions and receipt reads cost zero credits. Tool availability depends on the client catalog and permissions. See [product feedback](/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.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.
