Skip to main content
Book a demo

Connect Fullstory to OpenCode

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

Book a demo OpenCode setup guide

Set up

Add Fullstory to OpenCode in four steps

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

    Users add the Runlayer Plugin to OpenCode by hand using Runlayer’s generic MCP steps. OpenCode reaches Fullstory’s 30 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    OpenCode 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 OpenCode

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

Tools

30 Fullstory tools in OpenCode

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

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, OpenCode as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

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

Frequently asked questions

Connect more

Find another combination