Connect Gainsight to VS Code
Give VS Code governed access to Gainsight’s 20 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Gainsight to VS Code in four steps
Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.
- 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
Connect VS Code to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Gainsight’s 20 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).
VS Code setup guide - 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
Use Gainsight from VS Code
Gainsight’s approved tools appear in VS Code. Every call is checked against policy and recorded.
Tools
20 Gainsight tools in VS Code
Runlayer policy decides which of these VS Code 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.
Control
What Runlayer can see and stop in VS Code
Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.
Gateway policy (available)
Every Gainsight call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, VS Code 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 VS Code runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before VS Code’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.
Frequently asked questions
Connect more