Individual plan: On-Prem

Integrate Cursor (Individual Plan, On-Prem)

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. For on-prem deployments, data is sent to your own self-hosted collector instead of Hivel's hosted endpoint.

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/)

Configure for On-Prem:

1. Open config.json and update:

   • org_id: Set to "1" (on-prem value; leave as-is)

   • collector_url: Change to your on-prem VM's IP address (required)

2. Confirm both fields are correctly filled before proceeding.

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