Connect Fullstory to Glean
Give Glean governed access to Fullstory’s 30 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Fullstory to Glean in four steps
Admins approve the server once. Everyone in Glean then gets it through the same governed connection.
- 1
Add Fullstory to Runlayer
Fullstory isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Glean to Runlayer
Users add the Runlayer Plugin to Glean by following Runlayer’s setup guide. Glean reaches Fullstory’s 30 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Glean setup guide - 3
Sign in to Fullstory
Sign in the way Fullstory requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Fullstory from Glean
Fullstory’s approved tools appear in Glean. Every call is checked against policy and recorded.
Tools
30 Fullstory tools in Glean
Runlayer policy decides which of these Glean users can call.
Build funnel
Build a Fullstory funnel from a natural-language description.
Build journey
Build a FullStory journey from a natural-language description.
Build metric
Build a Fullstory metric from a natural language description.
Build segment
Build a Fullstory segment from a natural language description.
Compute funnel
Execute a saved funnel and return per-step counts and conversion rates.
Compute journey
Execute a journey and return the computed step-by-step breakdown.
Compute metric
Execute a metric and return the computed result.
Discover groups
Finds the top frustration and error groups across recorded data for the org.
Control
What Runlayer can see and stop in Glean
Some controls apply to every client at the gateway. Others depend on what Glean exposes to Runlayer.
Gateway policy (available)
Every Fullstory call from Glean passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Glean as the client, the tool, and the policy and scanner decisions.
OTLP telemetry (available)
Glean can send supported OpenTelemetry events to Runlayer for observe-only session visibility.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Glean yet, so control happens at the gateway.
In Glean
- Runlayer sees Glean activity through OpenTelemetry traces for monitoring only; enforcement happens at the gateway.
Frequently asked questions
Connect more