Connect / Cursor

Connect Cursor to Telara

Once Telara is approved in Cursor Marketplace, an engineer can install it from the Marketplace and sign in once to work across authorized repositories, tickets, and docs without leaving the editor.

client_type: cursor

The endpoint

Streamable HTTPhttps://api.telara.dev/v1/mcp

AuthOAuth 2.1 + PKCE with dynamic client registration

Connect it yourself

The public path is Marketplace installation followed by Telara sign-in. Marketplace review is in progress; do not substitute a hand-authored server configuration for the public deployment path.

In Cursor Marketplace, select Telara and choose Install when the listing is available.

Choose Connect and sign in when Telara opens the authorization page. OAuth 2.1 with PKCE completes without an API key, MCP URL, client secret, or tenant setup.

Confirm Telara’s tools appear in Cursor, then ask something only your authorized company data can answer and verify the Telara audit event.

Rolling it out centrally

A private team marketplace is an available customer-specific distribution route while global Marketplace review is pending. It can provide the same one-click employee connection, but it is not a substitute for the public listing.

A Cursor team marketplace administrator provisions Telara for the customer organization.

Employees install Telara from their team marketplace and complete their own Telara sign-in; Telara enforces organization policy per request.

Before you commit to this

Installation does not broaden employee access

Marketplace or team-marketplace installation only makes the connector available. Every Telara tool request remains subject to the employee’s organization membership and the relevant access and action policy.

Confirm it actually worked

The client's “connected” badge reports a successful handshake, not a tool call. Ask Cursor something answerable only from your indexed Telara data, then read GET /v1/mcp/audit/log and look for a row with client_type=cursor.

An answer with no matching audit row means the assistant replied from its own knowledge and never called Telara — a routing problem in the tool descriptions, not a broken connection. Every transport check will still look green.

Support, privacy, and reviewer testing

The complete OAuth and platform-review guide defines the governed 21-tool contract, the reviewer test flow, and the safe test action for platforms that permit writes.

For setup or reviewer access, contact support@telara.dev. For privacy requests, contact privacy@telara.dev. Telara's Privacy Policy and Terms of Service apply to every connection.

Comparing platforms? See connection paths for what each one needs. Looking instead to let Telara readthis platform's usage and spend? That is the opposite direction — see the connector catalog.