Connect Other MCP Clients

Configure the CommandCopy Anchor Link

Install the CLI on the machine that will run the MCP process. Configure these fields in your client's stdio server settings:

• Name: namera
• Command: namera
• Arguments: ["mcp", "serve", "--profile", "agent"]

Clients using an mcpServers JSON configuration commonly accept:

{
  "mcpServers": {
    "namera": {
      "command": "namera",
      "args": ["mcp", "serve", "--profile", "agent"]
    }
  }
}

The outer configuration format depends on your client. If it cannot find the executable, use the absolute installed path in command. Keep stdout reserved for MCP; do not add shell banners or wrappers that print there.

AuthorizeCopy Anchor Link

namera mcp login --profile agent
namera mcp status --profile agent

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

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

Use the same OS user, profile, and API host in both the client configuration and login command. For a custom deployment, append --host and its origin to the configured argument list and every MCP management command.

Use the ToolsCopy Anchor Link

Namera exposes account and session-key reads, transaction simulation and execution, status and history reads, signing, and signature verification. Start with a read to confirm the intended organization and grants.

The first authenticated tool call can start browser consent automatically. Approve it, then retry the tool. Login credentials survive client restarts; imported signing keys must also be available on that machine.

Diagnose a ConnectionCopy Anchor Link

If status says login-required, sign in again. If the client cannot launch Namera, check its PATH and Node.js version. If tools are denied, review the connection's scopes and session-key permissions. Do not treat a lost execution response as permission to repeat the transfer.

See mcp serve for supported protocol versions, host requirements, and the gas ceiling.

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.