# Other Clients

> Documentation index: [llms.txt](https://namera.ai/llms.txt).

Source: https://namera.ai/docs/mcp/clients/other-clients

Connect any client that can launch a local stdio MCP server.

Install [Namera](https://namera.ai/docs/mcp/installation) and complete
[account setup](https://namera.ai/docs/mcp/getting-started#prepare-your-account) on the machine
that will run the client. Make sure its process can find both `namera` and Node.js.

## Check Local Server Support [#check-local-server-support]

Your client must support **stdio** servers with a command and arguments. If it
only accepts a remote URL, it cannot connect directly to the current Namera MCP
server. Do not use the Namera API address as an MCP endpoint.

## Configure the Server [#configure-the-server]

Use these values in your client's local-server settings:

| Field     | Value                                |
| --------- | ------------------------------------ |
| Name      | `namera`                             |
| Transport | stdio                                |
| Command   | `namera`                             |
| Arguments | `mcp`, `serve`, `--profile`, `agent` |

For clients that use a `mcpServers` JSON object:

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

The wrapper and config location depend on the client. VS Code, Zed, and OpenCode
use different formats; follow their [specific guides](https://namera.ai/docs/mcp/clients).

Merge this entry into your existing configuration without removing other servers
or settings. If `namera` cannot be found, use its
[absolute executable path](https://namera.ai/docs/mcp/troubleshooting#the-client-cannot-find-namera).

The client starts and stops the process. Do not run a second server manually,
background the command, or redirect its stdout: stdio carries the MCP protocol.

## Authorize [#authorize]

```sh
namera mcp login --profile agent
namera mcp status --profile agent
```

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.

Choose a different profile for each additional client and use it consistently
in the launch, login, status, and logout commands.

## Use Namera [#use-namera]

Restart the client's server connection and check that its tools are available.

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](https://namera.ai/docs/mcp/permissions) before granting broader access.

## Disconnect [#disconnect]

```sh
namera mcp logout --profile agent
```

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.