Skip to main content
Book a demo

Connect Fullstory to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

Add Fullstory to GitHub Copilot in four steps

Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.

  1. 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. 2

    Connect GitHub Copilot to Runlayer

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Fullstory’s 30 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 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. 4

    Use Fullstory from GitHub Copilot

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

Tools

30 Fullstory tools in GitHub Copilot

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

See all 30 Fullstory tools

Control

What Runlayer can see and stop in GitHub Copilot

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

  • Gateway policy (available)

    Every Fullstory call from GitHub Copilot 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 as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination