Skip to main content
Book a demo

Connect Fullstory to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

Add Fullstory to Cline CLI in four steps

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

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Fullstory’s 30 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI 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 Cline CLI

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

Tools

30 Fullstory tools in Cline CLI

Runlayer policy decides which of these Cline CLI 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 Cline CLI

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

  • Gateway policy (available)

    Every Fullstory call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cline 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 before Cline CLI runs it.

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination