Claude Code

Install Namera and complete account setup on the machine that will run the client. Make sure its process can find both namera and Node.js.

Add NameraCopy Anchor Link

With Claude Code installed:

claude mcp add --transport stdio --scope user namera -- namera mcp serve --profile claude-code

User scope makes the registration available across your projects. To limit it to the current project instead, use --scope local. The -- separates Claude's options from Namera's launch command. See Claude Code's MCP documentation.

AuthorizeCopy Anchor Link

namera mcp login --profile claude-code
namera mcp status --profile claude-code

Approve the connection in your browser and select the active session keys it may use. Run these commands as the same OS user that runs the client. Namera saves the connection in your OS keyring; no API key belongs in the client config.

Use NameraCopy Anchor Link

Start Claude Code and run /mcp to check the connection. If you added the server during an existing session, restart that session before testing.

Ask in a new conversation:

Use Namera to list my accounts and session keys. Summarize their networks and permissions. Do not submit a transaction or sign a message.

Allow the read tools if prompted. If Namera requests browser authorization, complete it and retry the read request. An empty result means no resources were returned for this connection; do not ask the agent to invent account details.

Keep tool confirmations enabled for execution and signing where supported. See Permissions and Limits before granting broader access.

DisconnectCopy Anchor Link

namera mcp logout --profile claude-code

Also remove or disable the namera server in the client to stop it launching. Logout revokes the MCP connection without deleting imported keys. If revocation fails, revoke the connection in the dashboard as instructed by the error.