Kiro

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

In the Kiro IDE command palette, run Kiro: Open user MCP config (JSON) for all workspaces, or Kiro: Open workspace MCP config (JSON) for the current workspace. Add this to the file it opens:

{
  "mcpServers": {
    "namera": {
      "command": "namera",
      "args": ["mcp", "serve", "--profile", "kiro"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

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

IDE configs live at ~/.kiro/settings/mcp.json or .kiro/settings/mcp.json. Save the file to reconnect servers. Keep autoApprove empty so this entry does not automatically approve tools. See Kiro's MCP configuration.

AuthorizeCopy Anchor Link

namera mcp login --profile kiro
namera mcp status --profile kiro

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

Enable MCP support in Kiro's settings if it is disabled. Check the Namera server in the MCP panel, then open a new chat with the agent.

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 kiro

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.