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

# Nansen Connectors & MCP

- [Overview](https://docs.nansen.ai/mcp/overview.md): Give AI assistants and agents access to Nansen onchain data. Use a connector, or connect to Nansen MCP manually with an API key.
- [Connectors](https://docs.nansen.ai/mcp/connectors.md): Connect Nansen to ChatGPT, Claude, Grok, or Muse with your Nansen account. OAuth sign-in, no API key, 12 curated read-only tools.
- [ChatGPT](https://docs.nansen.ai/mcp/connectors/chatgpt.md): Install Nansen from the ChatGPT plugin directory. Tool calls spend your Nansen API credits.
- [Claude](https://docs.nansen.ai/mcp/connectors/claude.md): Connect Nansen to Claude with your Nansen account. Sign in through OAuth, no API key. Tool calls spend your Nansen API credits.
- [Claude Tag (Slack)](https://docs.nansen.ai/mcp/connectors/claude-tag.md)
- [Grok](https://docs.nansen.ai/mcp/connectors/grok.md): Connect the OAuth-protected Nansen MCP surface in Grok as a custom connector. No API key.
- [Muse](https://docs.nansen.ai/mcp/connectors/muse.md): Ask Muse to set up a Nansen custom connector, then sign in with your Nansen account. No API key needed.
- [Manually connecting to Nansen MCP](https://docs.nansen.ai/mcp/connecting.md): Connect Claude Desktop, Claude Code, Cursor, or any MCP client to Nansen MCP with an API key and get the full tool catalog.
- [Full tool catalog](https://docs.nansen.ai/mcp/connecting/tools.md): Every tool on the Nansen MCP server, with what it does and what a call costs in API credits.
- [MCP Data Redistribution Guidelines](https://docs.nansen.ai/mcp/redistribution-guidelines.md)


---

# 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.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.