Skip to main content
Book a demo

Connect Gainsight to Cursor

Give Cursor governed access to Gainsight’s 20 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cursor setup guide

Set up

Add Gainsight to Cursor in four steps

Admins approve the server once. Everyone in Cursor then gets it through the same governed connection.

  1. 1

    Add Gainsight to Runlayer

    Gainsight isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Cursor to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Gainsight’s 20 tools show up in Cursor’s own tool list.

    Cursor setup guide
  3. 3

    Sign in to Gainsight

    Sign in the way Gainsight requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Gainsight from Cursor

    Gainsight’s approved tools appear in Cursor. Every call is checked against policy and recorded.

Tools

20 Gainsight tools in Cursor

Runlayer policy decides which of these Cursor users can call.

  • Ask scorecard

    Fetch comprehensive scorecard data for one or more companies and/or relationships.

  • Ask staircase

    ASK Staircase compiles insights from a customer's own communications — emails, meetings, calls, support tickets, escalations, and Slack conversations.

  • Create timeline activity

    Creates a new Gainsight Timeline activity.

  • List fetch cta

    Fetch CTAs (Calls to Action) from Gainsight's Cockpit.

  • Fetch customer contacts

    Fetch contact records (people on the customer side of a company or relationship).

  • Fetch report data

    Fetch rows from a Gainsight report — optionally with on-the-fly modifications — without ever loading the full report config into your context.

  • Fetch success plan list

    Fetch Success Plans from Gainsight.

  • Fetch timeline activity list

    Fetch Timeline Activities from Gainsight using the Query API with full field control.

See all 20 Gainsight tools

Control

What Runlayer can see and stop in Cursor

Some controls apply to every client at the gateway. Others depend on what Cursor exposes to Runlayer.

  • Gateway policy (available)

    Every Gainsight call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cursor as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Cursor’s model sees it.

  • Redact output in place (not available)

    Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination