# Windsurf / Devin Desktop

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

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

Connect Namera to the Cascade agent's local MCP configuration.

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 to Cascade [#add-namera-to-cascade]

This setup is for **Cascade**. The current Windsurf documentation redirects to
Devin Desktop and distinguishes Cascade from the newer Devin Local agent, which
uses a different configuration. See the
[current Cascade MCP documentation](https://docs.devin.ai/desktop/cascade/mcp).

In Cascade's **…** actions menu, open the MCP configuration file. Add:

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

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

Open the file through the app so you edit the configuration used by your installed
version, rather than assuming an older Windsurf directory is still active.

## Authorize [#authorize]

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

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 Namera [#use-namera]

Enable Namera in Cascade's MCP controls and start a new conversation. If tools
are missing, check the server toggle and any organization-level MCP restrictions.

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

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.