Integrations / Cursor

Cursor

Cursor AI coding assistant — Admin + Analytics APIs for per-user spend, AI requests, tab acceptance, and team usage governance.

Basic auth

Spend

AI estate

Actions

What Telara does

Capability matrix

Indexes No Tracks spend Yes Discovers shadow AI Yes Runs actions Yes Real-time events No

Before you connect

Prerequisites

This connector requires a Cursor Team Admin key with admin:* scope, issued from Team Settings → Integrations → API Keys. Personal Cursor Pro accounts do not have access to team usage data.

A Cursor team on a Business or Enterprise plan. Team Admin API Keys do not exist on Pro.

You must have the admin role on that team. The API Keys section is hidden from members.

Vendor setup

Get the credential

Open Team Settings

Create an API key

Click Create API Key. Name it for Telara. Grant the team-admin permission this page lists from the catalog — analytics rejects a member key. Copy the key immediately; Cursor will not show it again.

Paste in Telara

Settings → Integrations → Cursor. Paste the key into the field Telara shows.

In Telara

Connect in Telara

Basic auth

Cursor admin API key. Cursor uses HTTP Basic auth with the API key as the username and an empty password (`curl -u $API_KEY:`). Issue an admin-scoped key from Team Settings → Integrations → API Keys. The key must have `admin:*` scope to access the Analytics + Admin endpoints used by the spend connector.

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for

API key

Spend

What gets measured

Resolution: Per user per day.

Attribution: Matched to people by email.

Vendor history: 30 days of vendor-side history.

ai_requests_chat
requests
ai_requests_agent
requests
ai_requests_composer
requests
ai_requests_cmdk
requests
tab_completions_shown
count
tab_completions_accepted
count
applies_accepted
count
applies_rejected
count
lines_accepted_added
count
lines_accepted_deleted
count
subscription_included_requests
requests
usage_based_requests
requests
byo_api_key_requests
requests
input_tokens
tokens
output_tokens
tokens
cache_read_tokens
tokens
cache_creation_tokens
tokens

AI estate

What gets discovered

Config paths

~/.cursor/mcp.json

Resource kinds

mcp_client_configuration, mcp_server_deployment

Config paths

.cursor/mcp.json

Resource kinds

mcp_client_configuration, mcp_server_deployment

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.