To connect Claude to AI Activate, follow Anthropic's instructions for adding a custom connector, and use the Nasuni details in this guide when Anthropic's steps ask for them. Anthropic's article is the authoritative source for Claude's steps and plan requirements, which change as Claude changes. A custom connector works in Claude on the web, Claude Desktop, and Cowork.
Anthropic's instructions: Get started with custom connectors using remote MCP
Before you start
At least one volume is activated and has MCP access turned on. For more information, see Enable MCP Access and Connect your AI tool.
Have your account's MCP endpoint, copied from the Portal under AI Activate → MCP Server. For more information, see Get your MCP endpoint.
Know your organization's company name, which you enter when you sign in through Nasuni Portal single sign-on.
Assign the people who plan to use AI Activate to the Nasuni connection in your identity provider (Okta or Microsoft Entra ID).
Your Claude plan supports custom connectors. On Team and Enterprise plans, an Owner, or another role that Anthropic's article lists, adds the connector for your organization.
Nasuni details for Claude
Use these values when Anthropic's steps ask for them.
Anthropic's step | What to enter or choose |
|---|---|
Name | A name your users will recognize, for example, Nasuni AI Activate. |
Remote MCP server URL | Your account's MCP endpoint from the Portal. |
Authentication settings Claude detected | Keep the OAuth settings that Claude detects. |
Authentication | A sign-in option, not No sign in. AI Activate requires each person to sign in. |
OAuth client | Register automatically. AI Activate supports dynamic client registration, so you do not need your own OAuth client, client ID, or client secret. |
Request headers | Leave empty. AI Activate does not use API keys or other fixed credentials. |
Sign-in prompt | Sign in through Nasuni Portal single sign-on with your company name and your own account. |
Nasuni hosts the endpoint on the public internet, so the private network and IP allowlisting steps in Anthropic's article do not apply.
On Team and Enterprise plans, the Owner adds the connector once, and each member then connects to it and signs in with their own Nasuni account. AI Activate returns results based on the permissions of the person who signs in, so two people can get different results for the same question.
To use AI Activate in a conversation, turn the connector on for that conversation, as described in Anthropic's article.
Connect Claude Code
If you sign in to Claude Code with your Claude account and have already connected AI Activate in Claude, the connector is available in Claude Code automatically. Run /mcp in Claude Code to check.
To add AI Activate to Claude Code directly instead, run this command, replacing <your-mcp-endpoint> with your account's MCP endpoint:
claude mcp add --transport http nasuni-ai-activate <your-mcp-endpoint>Then run /mcp in a Claude Code session, or run claude mcp login nasuni-ai-activate, and sign in through Nasuni Portal single sign-on. Claude Code registers itself automatically, so you do not need a client ID or client secret. Claude Code connects from your computer, so your network must allow HTTPS connections to your MCP endpoint.
Anthropic's instructions: Connect Claude Code to tools via MCP
Things to know
Each tool call Claude makes to AI Activate counts as one Activate Query, and a single question can trigger several calls. Claude's Research feature can call connectors many times for one request without asking for approval. For more information, see Monitor Your Usage.
For sign-in problems or missing results, see Troubleshooting.