> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/integrations/ai-tools/cursor-integrations/individual-plan.md).

# Individual plan

Integrate Cursor (Individual Plan)

Cursor's Individual plan doesn't expose a team usage API, so Hivel uses **local hook scripts** that run on each developer's machine to report usage events back to Hivel.

### **Prerequisite - Get Setup Files from Hivel:**

1. Log in to your Hivel account.
2. In the left sidebar, click **Settings** → **Integrations** tab.
3. Find the **Cursor** card and click **Connect**.
4. Download the four setup files provided:
   * `capture-event.ps1`
   * `capture.sh`
   * `config.json`
   * `hooks.json`

### **Add Files to Your Repository:**

1. Open your repo in an IDE and create `.cursor/hooks/` if it doesn't exist.
2. Place the downloaded files in these locations:
   * `capture-event.ps1`, `capture.sh`, `config.json` → inside `.cursor/hooks/`
   * `hooks.json` → directly inside `.cursor/` (not in `hooks/`)

### **Verify Configuration:**

1. Open `config.json` and confirm:
   * `org_id` is filled in (this attributes events to your organization)
   * `collector_url` is pre-filled by Hivel (leave it as-is)

### **Deploy to Your Team:**

1. Commit and push these files to your repo.
2. Each developer whose machine should be tracked must clone or pull the updated repo to get the `.cursor/` folder locally. Cursor only picks up hooks that exist on each machine.

### **Result:**

```
your-repo/
└── .cursor/
    ├── hooks/
    │   ├── capture-event.ps1
    │   ├── capture.sh
    │   └── config.json
    └── hooks.json
```

#### **To continue setting up your integrations** → [Back to Integrations](/integrations.md)