.codex-plugin/plugin.json

{
  "author": {
    "name": "Fullstory"
  },
  "description": "See what actually happened behind every number.\n\nFullstory MCP gives ChatGPT and Codex both halves of product investigation: analytics to size a problem and session replay to see why it happened. Ask where checkout is leaking, why a metric moved, or how to reproduce a bug. It discovers your pages and elements, computes the metric or funnel, and opens the sessions behind the drop. Every answer links to Fullstory, so you can check the work in one click.\n\nFullstory shows what users experienced - including silent failures that never threw an error - so \"conversion dropped 12%\" becomes \"the coupon field fails 5x more for logged-out users.\"\n\nBecause every answer links to the proof, you can give ChatGPT or Codex a standing job. Set up a scheduled task once, and it reports back with the sessions attached: an hourly watch for silent failures, automatic bug scoping on new tickets, or a Monday ranking of the fixes that would recover the most users.\n\nWhat ChatGPT and Codex can do:\n\n(1) Map a session, then zoom to the moment. Read a compact timeline first, then jump to the timestamp where it broke to pull the screenshot and page DOM from before and after - keeping context light.\n\n(2) Review sessions at scale. Because sessions load as compact structured data, read dozens of replays in one run and surface why users gave up.\n\n(3) Build segments, metrics, and funnels in your own words. Discover your pages, named elements, and events so questions map to your product.\n\n(4) Compute on demand. Run counts, rates, trends, funnels, journeys, and friction breakdowns by device, browser, geography, or user property.\n\nFullstory autocaptures clicks, page views, console and network errors, and frustration signals (rage and dead clicks), so many questions need no instrumentation at all.",
  "interface": {
    "capabilities": [],
    "category": "Data & Analytics",
    "defaultPrompt": [
      "Every hour, find checkout sessions with frustration but no logged error, and flag anything new with a session link.",
      "Find a session with a console error this week. Show me the screen where it broke, then count who else hit it.",
      "Find the page with the most rage clicks this week. Open 3 sessions and show me the screen where users got stuck."
    ],
    "developerName": "Fullstory",
    "displayName": "Fullstory",
    "longDescription": "See what actually happened behind every number.\n\nFullstory MCP gives ChatGPT and Codex both halves of product investigation: analytics to size a problem and session replay to see why it happened. Ask where checkout is leaking, why a metric moved, or how to reproduce a bug. It discovers your pages and elements, computes the metric or funnel, and opens the sessions behind the drop. Every answer links to Fullstory, so you can check the work in one click.\n\nFullstory shows what users experienced - including silent failures that never threw an error - so \"conversion dropped 12%\" becomes \"the coupon field fails 5x more for logged-out users.\"\n\nBecause every answer links to the proof, you can give ChatGPT or Codex a standing job. Set up a scheduled task once, and it reports back with the sessions attached: an hourly watch for silent failures, automatic bug scoping on new tickets, or a Monday ranking of the fixes that would recover the most users.\n\nWhat ChatGPT and Codex can do:\n\n(1) Map a session, then zoom to the moment. Read a compact timeline first, then jump to the timestamp where it broke to pull the screenshot and page DOM from before and after - keeping context light.\n\n(2) Review sessions at scale. Because sessions load as compact structured data, read dozens of replays in one run and surface why users gave up.\n\n(3) Build segments, metrics, and funnels in your own words. Discover your pages, named elements, and events so questions map to your product.\n\n(4) Compute on demand. Run counts, rates, trends, funnels, journeys, and friction breakdowns by device, browser, geography, or user property.\n\nFullstory autocaptures clicks, page views, console and network errors, and frustration signals (rage and dead clicks), so many questions need no instrumentation at all.",
    "privacyPolicyURL": "https://www.fullstory.com/legal/privacy-policy/",
    "shortDescription": "Product analytics for agents.",
    "supportURL": "https://www.fullstory.com/contact/",
    "termsOfServiceURL": "https://www.fullstory.com/legal/terms-and-conditions/",
    "websiteURL": "https://www.fullstory.com/",
    "logo": "./assets/logo.png",
    "composerIcon": "./assets/logo.png"
  },
  "name": "app-6a9a1ebb11fc81919ef2aa7231b9b068",
  "skills": "./skills",
  "mcpServers": "./.mcp.json",
  "version": "3.1.0",
  "apps": "./.app.json"
}