For the complete documentation index, see llms.txt. This page is also available as Markdown.

Claude Tag (Slack)

Connect Nansen to Claude Tag to ask for onchain data in Slack. Sign in with a Nansen account through OAuth.

Before you connect

  • Admin access to your organization's Claude Tag settings.

  • A dedicated Nansen account with API credits for shared-channel requests.

  • A Slack channel where you can test the connection.

Whose credits are used? Requests made through the bundle use the connected Nansen account and consume that account's API credits. Confirm the account and its billing owner before connecting. Use a dedicated organization account for shared channels. Personal connectors apply in DMs and, where enabled and permitted, to a member's own channel tasks.

1. Choose an access bundle

Open Claude Tag settings. Select your test channel under Claude Tag's access, then create or attach an Access bundle for that channel.

Check inherited connections before testing. A bundle attached at Default Slack applies across workspaces and channels. Confirm that requests use the account connected to your test bundle.

2. Connect Nansen with OAuth

  1. Open the bundle's Credentials tab and click Connect beside Custom tool.

  2. Set Credential type to MCP Connector.

  3. Choose your organization's Nansen provider if it is already available. Otherwise, select Add custom connector..., enter the URL below, and click Verify connector.

  4. Enter a connection name, click the provider's Sign in button, and authorize the dedicated Nansen account.

The organization connector should use Sign in now and Use Claude's published identity. No manually entered OAuth client ID or client secret is needed for this setup.

Claude Tag MCP Connector form showing the Nansen server and OAuth sign-in button
Provider discovery before sign-in. Provider names vary by organization. This example shows Slack Default; use your test channel's bundle for the pilot.

The form shows the MCP server the connection can reach. Review that URL and the Nansen account before approving access.

3. Enable the MCP plugin

For a custom remote MCP server, Anthropic documents a plugin plus a credential. Have your administrator add a plugin whose .mcp.json declares the MCP URL above, then enable it in the same bundle's Plugins tab. A .mcp.json in a repository Claude clones is not loaded on its own.

Plugin setup and the combined plugin/OAuth flow still need validation in Claude Tag. A connector directory listing alone does not establish that this step is unnecessary.

4. Try a request in Slack

Invite Claude to the channel if needed:

Start a new thread so it picks up the plugin, then ask:

@Claude, use Nansen to look up USDC on Ethereum. Tell me which tool you used and report any authentication or credit error.

Check that the request used the intended Nansen account and its API credits before enabling the connection in more channels. If it fails, check the bundle's channel scope, plugin, connection status and account credit balance.

Last updated

Was this helpful?