---
title: "MCP guide: install in Cursor"
description: Add the OneHazel MCP server to Cursor with one mcp.json file in your home folder, switch it on, and paste the one line that starts the integration.
---

# Install in Cursor

<!-- GENERATED by scripts/docs/generate-mcp-guides.ts from scripts/docs/mcp-guides/templates/install/cursor.md. Do not edit by hand. -->

::: tip What you need before you start
- Cursor installed and open.
- A key with the Connect scope, `mcp_connect_enabled`. Only **Connect casino** > **Integrate with AI** > **Create integration key** makes one. The **API Keys** page lists it with the label `mcp-connect`. The MCP switch on the **API Keys** page is a different setting and cannot add this scope.
- That key copied, from step 1 of [Install](/connect/mcp/install).
:::

Cursor is the one agent where your key sits in a settings file. That file is `~/.cursor/mcp.json`, in your home folder. It is outside your casino's code folder, so it is never committed or shared with your code. Never type the key into a `.cursor/mcp.json` inside your casino's code folder. A project file is safe only with the no-key form at the end of this page.

## Step 1. Open the Cursor settings file in your home folder

The Cursor documentation says: "Create `~/.cursor/mcp.json` in your home directory for tools available everywhere."

On a Mac, in Terminal:

```bash
mkdir -p ~/.cursor && touch ~/.cursor/mcp.json && open -e ~/.cursor/mcp.json
```

On Linux, in a terminal:

```bash
mkdir -p ~/.cursor && nano ~/.cursor/mcp.json
```

On Windows, in PowerShell:

```powershell
New-Item -ItemType Directory -Force "$HOME\.cursor" | Out-Null; notepad "$HOME\.cursor\mcp.json"
```

::: info What you should see
A text editor with the file open. It may be empty, or hold servers you already use.
:::

## Step 2. Paste the OneHazel entry and save

If the file is empty, paste this. Put your key in place of `oh_live_your_key_here`, then save:

```json
{
  "mcpServers": {
    "onehazel": {
      "type": "http",
      "url": "https://api.onehazel.com/mcp-server",
      "headers": {
        "Authorization": "Bearer oh_live_your_key_here"
      }
    }
  }
}
```

If the file already has a `"mcpServers"` section, add only the `"onehazel": { ... }` part inside it. Put a comma between it and the server before it. A file with two `"mcpServers"` sections does not load.

The **Cursor** tab on **Integrate with AI** shows this file with your key already filled in. You can paste that instead.

::: info What you should see
The file holds one `"mcpServers"` section, with `"onehazel"` inside it.
:::

## Step 3. Restart Cursor and switch the server on

Quit Cursor and open it again. The Cursor documentation says, for custom servers: "update your local files and restart Cursor." Then open Cursor's settings and make sure the `onehazel` server's toggle is on.

::: info What you should see
`onehazel` in Cursor's server list, switched on, with tools whose names start with `connect_`.
:::

## Step 4. Paste the one line

Open your casino's code folder in Cursor. Open a new Agent chat and paste exactly:

```text
Connect my casino to OneHazel. Start with connect_status and follow next_step.
```

::: info What you should see
The agent calls `connect_status` and reports one line per module. Continue with [the journey](/connect/mcp/journey).
:::

## For engineers: no key in any file

Cursor can read the key from the environment instead. The Cursor documentation says: "Cursor resolves variables in these fields: `command`, `args`, `env`, `url`, and `headers`." Replace the `Authorization` line with this:

```json
"Authorization": "Bearer ${env:ONEHAZEL_API_KEY}"
```

Cursor then needs `ONEHAZEL_API_KEY` set where it starts. On a Mac, Cursor opened from the Dock does not see variables set in Terminal. If the server fails with this form, go back to step 2.