Connect Gainsight to Claude Cowork
Give Claude Cowork governed access to Gainsight’s 20 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Gainsight to Claude Cowork in four steps
Admins approve the server once. Everyone in Claude Cowork 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 Claude Cowork to Runlayer
Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, Gainsight’s 20 tools show up in Claude Cowork’s own tool list.
Claude Cowork 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 Claude Cowork
Gainsight’s approved tools appear in Claude Cowork. Every call is checked against policy and recorded.
Tools
20 Gainsight tools in Claude Cowork
Runlayer policy decides which of these Claude Cowork 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 Claude Cowork
Some controls apply to every client at the gateway. Others depend on what Claude Cowork exposes to Runlayer.
Gateway policy (available)
Every Gainsight call from Claude Cowork passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude Cowork as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.
OTLP telemetry (available)
Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.
Stop a call before it runs (available)
Runlayer can reject a Claude Cowork prompt before Anthropic runs it, which stops the whole request rather than one tool call.
Block output after it runs (available)
Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.
Redact output in place (not available)
Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.
In Claude Cowork
- Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.
Frequently asked questions
Connect more