Codex
Connect Codex to Namera with a local MCP server.
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
With Codex CLI installed, register the server:
codex mcp add namera -- namera mcp serve --profile codexAlternatively, add this to ~/.codex/config.toml. Use one method, not both:
[mcp_servers.namera]
command = "namera"
args = ["mcp", "serve", "--profile", "codex"]Codex uses this configuration for its local clients. In the IDE extension, you can also add a STDIO server through MCP servers in the gear menu. See the official Codex MCP setup.
Authorize
namera mcp login --profile codex
namera mcp status --profile codexApprove 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's login command, not codex mcp login namera: this local server owns
its browser authorization flow.
Use Namera
Start a new Codex session. Run /mcp in the CLI to inspect active servers, or
codex mcp list from your terminal to check the saved registration.
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 codexAlso 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.