Skip to main content
Book a demo

Connect Gainsight to GitHub Copilot CLI

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

Book a demo GitHub Copilot CLI setup guide

Set up

Add Gainsight to GitHub Copilot CLI in four steps

Admins approve the server once. Everyone in GitHub Copilot CLI 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 GitHub Copilot CLI to Runlayer

    Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Gainsight’s 20 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    GitHub Copilot CLI 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 GitHub Copilot CLI

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

Tools

20 Gainsight tools in GitHub Copilot CLI

Runlayer policy decides which of these GitHub Copilot 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.

See all 20 Gainsight tools

Control

What Runlayer can see and stop in GitHub Copilot CLI

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, GitHub Copilot 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 or permission request before GitHub Copilot CLI runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.

In GitHub Copilot CLI

  • When a tool fails, Runlayer records the error but cannot replace it.

Frequently asked questions

Connect more

Find another combination