Connect Gainsight to Codex
Give Codex governed access to Gainsight’s 20 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Gainsight to Codex in four steps
Admins approve the server once. Everyone in Codex 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 Codex to Runlayer
Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Gainsight’s 20 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).
Codex 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 Codex
Gainsight’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
20 Gainsight tools in Codex
Runlayer policy decides which of these Codex 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 Codex
Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.
Gateway policy (available)
Every Gainsight call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Codex 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 Codex runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Codex’s model sees it.
Redact output in place (not available)
Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
Frequently asked questions
Connect more