namera mcp login

Authorize an MCP connection through browser consent.

UsageCopy Anchor Link

namera mcp login --profile default

OutputCopy Anchor Link

OK MCP connected to Namera
-> Profile: default
-> Server: https://api.namera.ai

Permissions
-> View wallets, session keys, and transaction history
-> Send transactions and sign with authorized session keys
-> Stay connected

Example output uses fixture accounts and hashes, captured with the CLI's output formatters. Plain-text output is shown without terminal colors; your values and relative expiry dates will differ.

With --output json:

{
  "profile": "default",
  "apiOrigin": "https://api.namera.ai",
  "status": "connected",
  "scopes": ["mcp:read", "mcp:execute", "offline_access"]
}

OptionsCopy Anchor Link

--profileCopy Anchor Link

• Type: string
• Default: default

Choose the MCP connection name. This is separate from ordinary CLI profiles, whose default is personal. Use the same name for serve, login, status, and logout.

--hostCopy Anchor Link

• Type: absolute API URL
• Default: https://api.namera.ai

Choose the API origin for this MCP connection. The origin and profile together identify its saved credentials. Use HTTPS, or a loopback HTTP origin for local development. NAMERA_API_URL does not override this option on MCP commands.

The command also accepts global options: --output pretty|json, --quiet, and --help.

This is separate from namera login. Approve only the session keys and MCP permissions the agent needs. Credentials persist in the OS keyring. If the browser cannot open, follow the printed URL. Imported signing keys must be available to the OS user running the MCP process.

ErrorsCopy Anchor Link

Failures exit nonzero and are written to stderr. With --output json, inspect error.code and error.nextStep. See Output and Errors.