Install the connection
You've minted a token — now hand it to your assistant. It's one command: your Nirvai address (already filled in below) plus the token you copied.
Run the command for your assistant
Replace <YOUR_TOKEN> with the connection token from Settings → Connections.
https://3kt55hmm4ixi5duur67snxkgz40nklgn.lambda-url.us-west-2.on.aws/claude mcp add --transport http nirvai "https://3kt55hmm4ixi5duur67snxkgz40nklgn.lambda-url.us-west-2.on.aws/" --header "Authorization: Bearer <YOUR_TOKEN>"npx add-mcp "https://3kt55hmm4ixi5duur67snxkgz40nklgn.lambda-url.us-west-2.on.aws/" --header "Authorization: Bearer <YOUR_TOKEN>"Replace <YOUR_TOKEN> with the connection token you copied.
That's it — your assistant now sees Nirvai. Ask it "What do I have in Nirvai?" and it will list your agents, databases and connections. The first thing it usually offers is to reconcile what it already knows about you into your shared memory.
In your assistant's prompt, type /nirvai: to see Nirvai's built-in commands — connect, remember, recall, new_agent, activity and more. They're shortcuts that kick off the right steps for you.
Troubleshooting
| Problem | Fix |
|---|---|
The command shows the address as <your-nirvai-backend> | The connection address wasn't set for this docs build. Grab the exact address from Settings → Connections in the app — it's shown next to the install snippet there. |
| "Unauthorized" / the assistant can't see anything | The token is wrong, expired, or was revoked. Mint a fresh one in Settings → Connections and re-run the command. |
| It can read but can't create | The token's scopes are too narrow. Mint a new token with write and create enabled. |
| A review page asks for a password | That's expected — secrets are always entered by you, on Nirvai's secure page. Your assistant can't complete a login for you. |
What's next
See what your agent does in the Activity Feed, or read the MCP documentation for the full picture of what the connection exposes.