Zed

Install Namera and complete account setup on the machine that will run the client. Make sure its process can find both namera and Node.js.

Add NameraCopy Anchor Link

Open Zed's settings JSON and add a context_servers entry:

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

Merge this entry into your existing configuration without removing other servers or settings. If namera cannot be found, use its absolute executable path.

Zed calls these context servers. Use context_servers, not mcpServers. See Zed's MCP documentation.

AuthorizeCopy Anchor Link

namera mcp login --profile zed
namera mcp status --profile zed

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.

Use NameraCopy Anchor Link

Open Settings → AI → MCP Servers and check that Namera is active. In the Agent Panel, select a profile that includes its tools. Keep the tool permission policy on confirmation rather than allowing every tool automatically.

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 before granting broader access.

DisconnectCopy Anchor Link

namera mcp logout --profile zed

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.