namera mcp status

Read the locally saved MCP connection state.

UsageCopy Anchor Link

namera mcp status --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.

Status ValuesCopy Anchor Link

• connected: a saved credential has not expired.
• refresh-required: the token has expired and a refresh token is saved.
• login-required: no usable saved connection is available.

This checks local state. It does not make an API request or prove server-side authorization remains valid. scopes lists saved scopes, which may remain present even when a new login is needed.

ErrorsCopy Anchor Link

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