Installation

Nova is installed as a Windows application. After installation, the license screen appears before agent and MCP features are useful.

The MCP connection is local by default. Claude Code and Codex use it to call Nova tools while you keep browser actions, approvals, and agent status visible in Nova.

For a normal setup, install Nova first, activate the license, and only then connect external agent clients through MCP. This keeps account activation, browser approvals, and agent access in one visible place.

In short

• Run the Nova installer, then start Nova from the installed application.
• Enter the email address and license key from your Nova account or license email.
• Keep Nova open while an external agent uses the MCP connection.
• Treat the MCP token as a secret and never commit it to a repository.

Installation and license

1. Run the installer Start the downloaded Nova installer and complete the Windows setup. If Windows shows a security prompt, continue only when the file came from the expected Nova download source.
2. Start Nova Open Nova Browser after installation. On the first start, wait until the browser surface and settings are ready.
3. Enter license data Use the email address and license key assigned to your account. Nova checks whether this build may be used with that license.
4. Prepare agents Open the AI agent settings and connect the providers you want to use. Claude can use an API key or CLI setup; Codex uses its Codex account login.

When this matters

This page is most relevant when Nova is installed on a new device, reactivated after an update or reinstall, or when Claude Code or Codex should see Nova tools again.

MCP connection

MCP is the local bridge between Nova and external agent clients. Nova publishes a localhost endpoint and a bearer token for the running app. Use the values shown in Nova or in the local discovery file instead of hardcoding port or token.

Discovery file

%LOCALAPPDATA%\NovaBrowser\mcp.json contains the current endpoint and bearer token.

Endpoint

Usually looks like http://127.0.0.1:<port>/mcp and changes when Nova chooses another port.

Token

Required for HTTP clients. Regenerate it in Nova if it was shared by mistake.

Scope

Local by default. Remote access should only be enabled deliberately and with a clear security reason.

MCP client setup

There are three setup paths: let Nova write the client configuration, let Claude Code or Codex write their own configuration, or edit the files manually when you need full control.

{
  "mcpServers": {
    "novabrowser": {
      "type": "http",
      "url": "<endpoint from Nova>",
      "authorizationType": "none",
      "headers": {
        "Authorization": "Bearer <token from Nova>"
      }
    }
  }
}

claude mcp add-json novabrowser "{\"type\":\"http\",\"url\":\"<endpoint from Nova>\",\"headers\":{\"Authorization\":\"Bearer <token from Nova>\"}}" --scope user
claude mcp get novabrowser

[mcp_servers.novabrowser]
command = "node"
args = ["C:/Path/To/Nova/tools/novabrowser-mcp-stdio-proxy.mjs"]

[mcp_servers.novabrowser]
url = "<endpoint from Nova>"
http_headers = { Authorization = "Bearer <token from Nova>" }