Gemini CLI

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 Gemini CLI installed, add this to ~/.gemini/settings.json for your user, or .gemini/settings.json for the current project:

{
  "mcpServers": {
    "namera": {
      "command": "namera",
      "args": ["mcp", "serve", "--profile", "gemini"],
      "trust": false
    }
  }
}

trust: false keeps tool approval prompts instead of trusting all calls from the server. See Gemini CLI's MCP setup.

Merge this entry into your existing configuration without removing other servers or settings. If namera cannot be found, use its absolute executable path.

AuthorizeCopy Anchor Link

namera mcp login --profile gemini
namera mcp status --profile gemini

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 a new Gemini CLI session and run /mcp to inspect the connected servers and available tools. If Namera is excluded by your MCP settings, enable it before testing the connection.

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 gemini

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.