fullstory-claude-plugin

Talk to your product data.
Ask Claude anything about your users — drop-offs, rage clicks, conversion funnels — and get answers backed by real sessions.

Install · What it does · Skills · Prerequisites · Troubleshooting

Quick Install

One command in Claude Code:

/plugin marketplace add reatlat/fullstory-claude-plugin
/plugin install fullstory-reatlat@fullstory-marketplace

Also works in Cursor (Marketplace panel, same URL) and VS Code Copilot (Chat: Install Plugin from Source).

No local server. No API keys to juggle. OAuth handles auth — you sign in once and it just works.

Claude Desktop (manual setup)

Claude Desktop doesn't support the plugin marketplace — you get the MCP tools but not the skills/agents. Add this to claude_desktop_config.json:

{
  "mcpServers": {
    "fullstory": {
      "type": "http",
      "url": "https://api.fullstory.com/mcp/fullstory"
    }
  }
}

Config file locations: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS), %APPDATA%\Claude\claude_desktop_config.json (Windows). Restart Claude Desktop after editing.

What It Does

Fullstory records every session on your site. This plugin lets Claude read that data.

Before: Export CSV → pivot table → screenshot → Slack → someone asks "but why?" → repeat.

After: Type a question. Get an answer.

It doesn't just answer "how many." It answers "why" — by reading the actual sessions behind the numbers.

See a real conversation → — 10 skills, one investigation, zero SQL.

Skills

Forty-four skills ship with the plugin. Claude loads the right one automatically based on what you ask.

Analytics & Measurement

Investigation & Debugging

Operations & Maintenance

Agents (isolated context workers)

Prerequisites

1. Fullstory account with MCP Beta access
2. StoryAI features enabled — an org admin toggles this in Settings > Account Management > StoryAI Features
3. Claude Code, Cursor, or VS Code Copilot

Without StoryAI enabled, the server connects but exposes zero tools. If you see "connected but no tools," that's the fix.

How It Works

You  →  Claude Code  →  Fullstory MCP Server (api.fullstory.com)  →  Your Fullstory Data
                         ↑ OAuth, no local process

The plugin wires up three things:

The MCP server exposes tools like build_metric, compute_metric, get_sessions, session_open, session_view, session_diff — you don't memorize these. You ask questions. Claude picks the tools.

OAuth Scopes

The OAuth flow requests read-only access to your Fullstory org. No write scopes — the plugin queries and analyzes, never modifies.

All scopes are read-only. Fullstory MCP does not expose write scopes — segments and metrics created during a session return a link for manual saving in the Fullstory UI.

Troubleshooting

Full FAQ: developer.fullstory.com/mcp/faq

Star History

If this is useful, star the repo — it helps other teams discover it.

License

MIT © Alex Zappa

Skill content adapted from fullstorydev/fullstory-skills (MIT).

📝 Blog post: how we built 44 skills · 📋 MCP registry submission guide · 💬 Example conversation

_{Not affiliated with Fullstory. Fullstory is a trademark of Fullstory, Inc.}