Profiles and Configuration

Give Each Client a ProfileCopy Anchor Link

Use a distinct profile such as codex, cursor, or openclaw. The profile and API origin together identify the saved MCP connection.

namera mcp login --profile cursor
namera mcp status --profile cursor

The client's launch arguments must match:

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

This is the server entry, not a complete client config. Each client guide shows its required wrapper.

If omitted, the MCP profile is default. Profiles keep connections separate; they are not a security boundary between processes running as the same OS user.

Use the Same Machine and OS UserCopy Anchor Link

Run login and the MCP server as the same OS user, with access to the same keyring and any imported keys. A login on your laptop does not authorize a server running inside a container, remote workspace, or another user's background service.

For GUI clients, namera and Node.js must be available in the environment used to launch the server. If the executable is not found, see Troubleshooting.

Use a Different API OriginCopy Anchor Link

For a local Namera development server:

namera mcp login --profile dev --host http://localhost:8080
namera mcp status --profile dev --host http://localhost:8080

Set matching server arguments:

{
  "command": "namera",
  "args": ["mcp", "serve", "--profile", "dev", "--host", "http://localhost:8080"]
}

Use the same --host for logout. MCP commands default to https://api.namera.ai and do not use NAMERA_API_URL to select a host. The host is an API origin, not an MCP endpoint. Non-loopback origins must use HTTPS.

See the CLI's server options for the complete launch-command details.