AI agent setup

Run this in a terminal. The user scope makes the server available in every project. The single quotes keep ${NEVAZU_WORK_KEY} as written, and Claude Code expands it each time it starts. Check with claude mcp list; the server is loaded after a restart.

claude mcp add-json --scope user nevazu-work '{"type":"http","url":"https://connect.nevazu.com/mcp/BROWSER_ID","headers":{"Authorization":"Bearer ${NEVAZU_WORK_KEY}"}}'

Add this to ~/.codex/config.toml (create the file if it is missing). Codex sends the value of the named variable as the bearer token. The same in one command: codex mcp add nevazu-work --url https://connect.nevazu.com/mcp/BROWSER_ID --bearer-token-env-var NEVAZU_WORK_KEY. Check with codex mcp list; the server is loaded after a restart.

[mcp_servers.nevazu-work]
url = "https://connect.nevazu.com/mcp/BROWSER_ID"
bearer_token_env_var = "NEVAZU_WORK_KEY"
tool_timeout_sec = 90

Merge this into ~/.cursor/mcp.json, keeping any servers already there. Cursor substitutes ${env:NEVAZU_WORK_KEY} when it starts. The server appears in Cursor’s MCP settings, where it may need turning on.

{
  "mcpServers": {
    "nevazu-work": {
      "url": "https://connect.nevazu.com/mcp/BROWSER_ID",
      "headers": {
        "Authorization": "Bearer ${env:NEVAZU_WORK_KEY}"
      }
    }
  }
}

Merge this into the user MCP configuration (the command MCP: Open User Configuration) or into .vscode/mcp.json, keeping the entries already there. The first time the server starts, VS Code asks the user for the key and keeps it in its secret storage; the user pastes the value of NEVAZU_WORK_KEY there.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "nevazu-work-key",
      "description": "Nevazu access key (NEVAZU_WORK_KEY)",
      "password": true
    }
  ],
  "servers": {
    "nevazu-work": {
      "type": "http",
      "url": "https://connect.nevazu.com/mcp/BROWSER_ID",
      "headers": {
        "Authorization": "Bearer ${input:nevazu-work-key}"
      }
    }
  }
}

Merge this into ~/.codeium/windsurf/mcp_config.json, keeping any servers already there, then refresh the MCP servers in Windsurf. Windsurf substitutes ${env:NEVAZU_WORK_KEY}.

{
  "mcpServers": {
    "nevazu-work": {
      "serverUrl": "https://connect.nevazu.com/mcp/BROWSER_ID",
      "headers": {
        "Authorization": "Bearer ${env:NEVAZU_WORK_KEY}"
      }
    }
  }
}

Merge this into ~/.gemini/settings.json, keeping the settings already there. Gemini CLI expands ${NEVAZU_WORK_KEY} from the environment when it loads its settings. Check with /mcp.

{
  "mcpServers": {
    "nevazu-work": {
      "httpUrl": "https://connect.nevazu.com/mcp/BROWSER_ID",
      "headers": {
        "Authorization": "Bearer ${NEVAZU_WORK_KEY}"
      }
    }
  }
}

Merge this into ~/.config/opencode/opencode.json (or opencode.json in a project), keeping the configuration already there. OpenCode substitutes {env:NEVAZU_WORK_KEY} when it loads its configuration; oauth: false stops it from trying to sign in with OAuth.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nevazu-work": {
      "type": "remote",
      "url": "https://connect.nevazu.com/mcp/BROWSER_ID",
      "enabled": true,
      "oauth": false,
      "headers": {
        "Authorization": "Bearer {env:NEVAZU_WORK_KEY}"
      }
    }
  }
}

Any client that speaks MCP over Streamable HTTP connects with the URL and an Authorization header carrying the key. Use the client’s own way of reading an environment variable; if it has none, tell the user where to put the key themselves. The curl command checks the key by listing the tools.

URL: https://connect.nevazu.com/mcp/BROWSER_ID
Header: Authorization: Bearer <the value of NEVAZU_WORK_KEY>

# Check the key (lists the tools):
curl -s https://connect.nevazu.com/mcp/BROWSER_ID -H "Authorization: Bearer $NEVAZU_WORK_KEY" -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Run this in a terminal, then restart Claude Code. In Claude Code, /mcp lists the server as needing authentication: choose it, then Authenticate, and the sign-in opens in the user’s web browser. Claude Code keeps the tokens and renews them.

claude mcp add --transport http --scope user nevazu-work https://connect.nevazu.com/mcp/BROWSER_ID

For Claude on the web, desktop or mobile: in Customize → Connectors, choose + Add, then Add custom connector, give it a name and paste this URL, keep the detected OAuth sign-in, then Add and Connect. The Nevazu page opens to approve it. On a Team or Enterprise plan, an owner adds the connector first under Organization settings → Connectors; members then choose Connect under Customize → Connectors.

https://connect.nevazu.com/mcp/BROWSER_ID

Add this to ~/.codex/config.toml (create the file if it is missing), then run codex mcp login nevazu-work in a terminal: Codex opens the sign-in in the user’s web browser and keeps the tokens. The same server in one command: codex mcp add nevazu-work --url https://connect.nevazu.com/mcp/BROWSER_ID. If Codex says login is not supported, update it.

[mcp_servers.nevazu-work]
url = "https://connect.nevazu.com/mcp/BROWSER_ID"
tool_timeout_sec = 90

# Then sign in from a terminal: codex mcp login nevazu-work

Merge this into ~/.cursor/mcp.json, keeping any servers already there. Cursor’s MCP settings show that the server needs to sign in; choose its button (Connect or Login), and the sign-in opens in the user’s web browser and returns to Cursor.

{
  "mcpServers": {
    "nevazu-work": {
      "url": "https://connect.nevazu.com/mcp/BROWSER_ID"
    }
  }
}

Merge this into the user MCP configuration (the command MCP: Open User Configuration), keeping the entries already there. When the server starts, VS Code asks to allow it to sign in, opens the Nevazu page, and keeps the sign-in under Accounts.

{
  "servers": {
    "nevazu-work": {
      "type": "http",
      "url": "https://connect.nevazu.com/mcp/BROWSER_ID"
    }
  }
}

Merge this into ~/.codeium/windsurf/mcp_config.json, keeping any servers already there, then refresh the MCP servers in Windsurf. Windsurf opens the sign-in when the server first connects; if your version cannot sign in, update Windsurf.

{
  "mcpServers": {
    "nevazu-work": {
      "serverUrl": "https://connect.nevazu.com/mcp/BROWSER_ID"
    }
  }
}

Merge this into ~/.gemini/settings.json, keeping the settings already there. Gemini CLI finds the sign-in when it connects; if it does not start by itself, run /mcp auth nevazu-work.

{
  "mcpServers": {
    "nevazu-work": {
      "httpUrl": "https://connect.nevazu.com/mcp/BROWSER_ID"
    }
  }
}

Merge this into ~/.config/opencode/opencode.json (or opencode.json in a project), keeping the configuration already there. OpenCode starts the sign-in when it connects; opencode mcp auth nevazu-work starts it by hand.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nevazu-work": {
      "type": "remote",
      "url": "https://connect.nevazu.com/mcp/BROWSER_ID",
      "enabled": true
    }
  }
}

Any client that implements MCP authorization (OAuth 2.1 with PKCE) signs in by itself. It finds Nevazu from the 401 response, registers with Dynamic Client Registration or a Client ID Metadata Document, and returns to a local callback (http://127.0.0.1 or localhost, any port), its own app scheme, or claude.ai, chatgpt.com or vscode.dev. In ChatGPT (Plugins → + → Add custom MCP server), enter the browser’s MCP URL as the MCP server URL and choose OAuth.

URL: https://connect.nevazu.com/mcp/BROWSER_ID
No header: the client signs in with OAuth (MCP authorization), which it discovers from the server.