Claude Desktop
Configure Namera as a local server in the Claude desktop app.
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 Namera
In Claude Desktop, open Settings → Developer → Edit Config. Add Namera to
claude_desktop_config.json:
{
"mcpServers": {
"namera": {
"command": "namera",
"args": ["mcp", "serve", "--profile", "claude-desktop"]
}
}
}Merge this entry into your existing configuration without removing other servers
or settings. If namera cannot be found, use its
absolute executable path.
Use the desktop app's local-server configuration, not a remote connector URL. See the official local-server setup for the configuration location on your OS.
Authorize
namera mcp login --profile claude-desktop
namera mcp status --profile claude-desktopApprove 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 Namera
Fully quit and reopen Claude Desktop after saving the config. Check that Namera appears among the available local tools.
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.
Disconnect
namera mcp logout --profile claude-desktopAlso 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.