> 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/muse.md). # Muse Ask Muse to set up a Nansen custom connector, then sign in with your Nansen account. No API key needed. Connect Nansen to Muse by pasting a setup prompt into a conversation. Muse configures a custom connector and guides you through Nansen sign-in. This uses Muse's [custom connector support](https://www.meta.com/help/artificial-intelligence/1687253048996149/). ### What you need A Muse account with custom connector access and a Nansen account. Sign in with the Nansen account whose API credits you want to use. {% hint style="info" %} Tool calls spend your [Nansen API credits](/getting-started/credits.md), not your Muse subscription, and are subject to [rate limits](/getting-started/rate-limits.md). One request can trigger several calls. Nansen is read-only and cannot trade, sign transactions, or move assets. {% endhint %} ### Connect Nansen Muse handles the OAuth configuration. You do not need to create an OAuth client or enter these settings manually. No manual Resource setting is needed for this Muse setup. Use the Muse settings below when connecting through Muse. 1. Open [Muse](https://muse.ai/) and start a conversation. 2. Copy the entire prompt below and send it to Muse. {% code overflow="wrap" %} ``` Set up a custom connector named "Nansen" using these settings: MCP server URL: https://mcp.nansen.ai/ra/connector-curated/mcp Transport: Streamable HTTP Authentication: OAuth authorization code with PKCE S256 Client secret: none, leave empty Token endpoint authentication method: none Authorization endpoint: https://idp.nansen.ai/authorize Token endpoint: https://idp.nansen.ai/token Scope: nansen:read Redirect URI: https://agent.meta.ai/api/hatch/oauth/callback Use Muse's registered OAuth client for Nansen, with client_id=muse. Start OAuth and give me the sign-in link so I can sign in to Nansen and approve access myself. Store credentials in your Secure Credentials Store. Do not ask me to paste a password, API key, authorization code, or token into this conversation. After sign-in, discover and list the available tools. Do not run any data queries yet. A tool list alone does not prove that queries work. ``` {% endcode %} 3. Open the sign-in link Muse provides. Sign in on Nansen's site and approve read-only access. Return to Muse to finish connecting. 4. Confirm Muse lists the [12 curated tools](/mcp/connectors.md#curated-tools), including `general_search` and `token_info`. ### Verify your connection Send this in the same conversation: > Use the production 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. A token search with `general_search` costs **0 credits**. Address labeling and `.eth` or `.sol` name resolution cost **500 credits**, so keep this check to the token name `ETH`. See [credits per call](/mcp/connectors.md#credits-per-call). Check that Muse 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, you can ask: * "Use Nansen to find Wintermute." * "Use Nansen to get token information for USDC on Ethereum." Muse uses the same [12 curated tools](/mcp/connectors.md#curated-tools) as ChatGPT, Claude, and Grok. For tools outside this set, use [Manually connecting to Nansen MCP](/mcp/connecting.md) with another MCP client. ### Troubleshooting | Problem | What to do | | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Muse asks for an API key or client secret | Ask it to use the OAuth settings in the setup prompt. This connector does not need either. | | Invalid client or redirect URI | Ask Muse to use its registered OAuth client for Nansen, with `client_id=muse`, and the redirect URI in the prompt. If Muse uses a different callback, contact Nansen support with the callback URL only, without query parameters or credentials. | | Sign-in is requested again, or access is denied | Ask Muse to reconnect Nansen and sign in with the intended account. | | Muse lists tools but answers without calling Nansen | Ask it to use the production 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 Muse's **Settings → Connectors** and disconnect Nansen. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.nansen.ai/mcp/connectors/muse.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.