Claude Code
Connect Fullstory to Claude Code to query your product data directly from the terminal.
Prerequisites
- StoryAI features enabled for your Fullstory org (see the note below — this is a hard requirement; without it your client will connect but show zero tools).
- Claude Code installed (version 1.0.33 or later)
Fullstory MCP requires StoryAI features to be enabled for your org. If your org has opted out of StoryAI, your MCP client will appear to connect successfully (OAuth completes, the server shows as "connected") but no tools will be available.
An account Admin can verify or change this at Settings > StoryAI Features in Fullstory. If you don't see that page, you don't have the role needed to change it. Ask an Admin in your org.
See FAQ & Troubleshooting if your client is connected but no tools appear.
The Claude connector directory listing is for Claude.ai and the Claude app only—it does not apply to Claude Code. Use the plugin marketplace method below to connect.
Setup
1. Start Claude Code (from terminal)
claude
2. Add the Fullstory marketplace (from Claude Code)
/plugin marketplace add fullstorydev/fullstory-skills
3. Install the plugin (from Claude Code)
/plugin install fullstory@fullstory
Exit Claude Code (using /exit) and start it again. The re-run that command.
4. Reload plugins (from Claude Code)
/reload-plugins
5. Authenticate MCP (from Claude Code)
/mcp
What the plugin includes
| Component | What it does |
|---|---|
| MCP server | Connects Claude Code to your Fullstory data |
general-analysis skill | Guides Claude through a structured analytics workflow: build a segment or metric, compute results, validate them, then investigate sessions |
comparisons skill | Automatically invoked when comparing A vs B — picks the right mechanism (dimensionality vs separate segments) |
session-review skill | Guides Claude through diagnosing a user-reported issue, investigating a bug, or validating UI correctness from a session URL |
idea-generation skill | Guides Claude through finding 3–5 ranked product ideas the team hasn't considered, with user counts against a baseline and session replay evidence |
session-context agent | Reviews individual sessions in an isolated context so session data doesn't bloat your main conversation |
See Skills for details on each. Use the analytics skill with /fullstory:general-analysis.
Allow all Fullstory tools
By default, Claude Code asks for approval the first time it calls each Fullstory tool. Choosing Yes, and don't ask again saves a rule for that one tool, so you're asked again whenever Fullstory adds a new tool or Claude uses one it hasn't called before.
To approve every Fullstory tool at once, including tools added later, add an allow rule for the whole server:
- Run
/mcpand note the name of the Fullstory server. For the plugin, it'splugin:fullstory:fullstory. If you added the server yourself, it's the name you gave it, such asfullstory. - Run
/permissionsand add an Allow rule for the server, with no tool name:
| How you connected | Rule |
|---|---|
| Plugin | mcp__plugin_fullstory_fullstory |
Server you added yourself, named fullstory | mcp__fullstory |
You can also add the rule to the permissions.allow list in your Claude Code settings file (~/.claude/settings.json for all projects, or .claude/settings.json in a project):
{
"permissions": {
"allow": ["mcp__plugin_fullstory_fullstory"]
}
}
Telling Claude in the chat to stop asking has no effect. Claude Code enforces approvals itself, so only an allow rule removes the prompt. See Claude Code permissions for details on rule syntax.
Using the tools
Once connected, ask questions about your product data in natural language:
- "What are the top frustrations on our product right now?"
- "Build a segment of users who rage clicked on the payment page and summarize 3 sessions for me."
- "What's causing the most drop-off in our checkout funnel, and can you show me what those sessions look like?"
See Example Workflows for more patterns.