Generic setup

Fullstory MCP is in private beta and must be enabled for your Fullstory account before you can connect. If you're interested in being one of the first to try Fullstory MCP, sign up for the waitlist here.

StoryAI features must be enabled

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 → GenAI Features (/settings/genai-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.

Most MCP-compatible clients accept a JSON configuration block. The universal pattern looks like this:

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

Paste this block into your client's MCP configuration file, adjusting the outer structure if your client uses a slightly different schema (for example, "servers" instead of "mcpServers"). On first connection, your client will open a browser window to authorize with Fullstory via OAuth.

This gives you the MCP server and raw tools. For step-by-step instructions for specific clients, see Cursor, Claude, or Claude Code.

Plugin install for Claude Code and Cursor

Claude Code and Cursor users can also install the Fullstory plugin, which sets up the MCP server and adds built-in AI skills for analytics and session investigation workflows. See the Claude Code and Cursor setup pages for details.