> For the complete documentation index, see [llms.txt](https://docs.nerovasystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nerovasystems.com/mcp-server/connecting.md).

# Connect a client

Any MCP client that supports remote servers over streamable HTTP can connect. Clients that support OAuth sign in with your Nerova account in the browser; clients that only support headers can send an API key instead — see [Authentication and consent](/mcp-server/authentication.md).

The connection URL is the same everywhere:

```
https://api.nerovasystems.com/mcp
```

## Claude

Add a custom connector with the URL above (Settings → Connectors → Add custom connector). Claude discovers the OAuth flow automatically and opens the Nerova consent screen in your browser.

For Claude Code:

```bash
claude mcp add --transport http nerova https://api.nerovasystems.com/mcp
```

## VS Code

Add the server to `.vscode/mcp.json` (or your user configuration):

```json
{
  "servers": {
    "nerova": {
      "type": "http",
      "url": "https://api.nerovasystems.com/mcp"
    }
  }
}
```

VS Code prompts you to authorize the connection on first use.

## Cursor

Add the server to `~/.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "nerova": {
      "url": "https://api.nerovasystems.com/mcp"
    }
  }
}
```

## Clients without OAuth support

Send an organization Live API key (`nrv_live_`) as a bearer token, exactly as on the REST API:

```json
{
  "mcpServers": {
    "nerova": {
      "url": "https://api.nerovasystems.com/mcp",
      "headers": {
        "Authorization": "******"
      }
    }
  }
}
```

`<NEROVA_API_KEY>` is a placeholder. Never paste a real key into documentation, source control, URLs, telemetry, or support messages.

## First run

On the first connection the client walks through sign-in and consent: choose the permission areas the assistant may use. Connections are Live and require an active production entitlement, which your free testing allowance provides. After that, verify the connection by asking the assistant to call `get_status` — it requires no scopes and echoes service availability. `get_context` shows the resolved permissions and environment of the connection.

Manage or revoke connections at any time in the console under **Developers → Connections**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nerovasystems.com/mcp-server/connecting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.