OpenClaw
Connect Namera to agents running through your OpenClaw Gateway.
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.
For OpenClaw, that machine is the Gateway host, which may be different from the device where you send messages. Its OS user needs access to Namera's keyring and any imported keys. A container without a usable keyring is not sufficient.
Add Namera
In the Control UI, open Settings → MCP → Add server. Enter:
| Field | Value |
|---|---|
| Name | namera |
| Transport | Stdio |
| Command | namera |
| Arguments | mcp, serve, --profile, openclaw |
Save the server. If the form accepts one command line, enter
namera mcp serve --profile openclaw. Server definitions live under mcp.servers;
do not paste another client's mcpServers wrapper into OpenClaw's config.
See OpenClaw's MCP setup.
Authorize
On the Gateway host, as the user that runs it:
namera mcp login --profile openclaw
namera mcp status --profile openclawApprove 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.
Browser approval must reach the login process's loopback callback. If the Gateway runs on a remote host without browser access, resolve that environment requirement before using Namera; authorizing only on your laptop will not connect it.
Use Namera
Check server discovery on the Gateway host:
openclaw mcp doctor namera --probeMake Namera available to the intended agent and session through OpenClaw's tool policy. Connecting a server does not bypass those controls. Start with a private conversation, not a shared channel whose participants should not control the account.
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 openclawAlso 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.