# VS Code

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

Source: https://namera.ai/docs/mcp/clients/vscode

Connect Namera to agent chat in Visual Studio Code.

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.

## Add Namera [#add-namera]

In your workspace, create or edit `.vscode/mcp.json`:

```json
{
  "servers": {
    "namera": {
      "type": "stdio",
      "command": "namera",
      "args": ["mcp", "serve", "--profile", "vscode"]
    }
  }
}
```

VS Code uses **`servers`**, not `mcpServers`, in this file. Use the editor's
**Start** control above the server entry and approve server trust when prompted.
See [VS Code's MCP configuration](https://code.visualstudio.com/docs/agents/reference/mcp-configuration).

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).

## Authorize [#authorize]

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

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.

If you use a remote workspace, confirm where VS Code launches the server.
Namera must have its installation, keyring, and browser-login access in that
environment. Start with a local workspace if those are unavailable remotely.

## Use Namera [#use-namera]

Open agent chat and enable Namera's tools in the tools picker. MCP access may be
restricted by your organization's VS Code policies.

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 vscode
```

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.