Connect Gainsight to Cline CLI
Give Cline CLI governed access to Gainsight’s 20 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Gainsight to Cline CLI in four steps
Admins approve the server once. Everyone in Cline CLI 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 Cline CLI to Runlayer
Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Gainsight’s 20 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Cline CLI 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 Cline CLI
Gainsight’s approved tools appear in Cline CLI. Every call is checked against policy and recorded.
Tools
20 Gainsight tools in Cline CLI
Runlayer policy decides which of these Cline CLI 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 Cline CLI
Some controls apply to every client at the gateway. Others depend on what Cline CLI exposes to Runlayer.
Gateway policy (available)
Every Gainsight call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Cline CLI 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 Cline CLI runs it.
Block output after it runs (not available)
Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.
Redact output in place (not available)
Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.
In Cline CLI
- If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
- This covers the Cline CLI, not the Cline extension for VS Code.
Frequently asked questions
Connect more