Fullstory MCP Server

The Sentry-FullStory integration creates a link from the Sentry Error to the FullStory replay. It also creates a link from the FullStory event to the Sentry error. That is what the fullstory mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

The @sentry/fullstory integration seamlessly integrates the Sentry and FullStory platforms. When you look at a browser error in Sentry, you will see a link to the FullStory session replay at that exact moment in time. When you are watching a FullStory replay and your user experiences an error, you will see a link that will take you to that error in Sentry.

The tools it exposes

The server publishes 1 tool. What each one is for:

• Browser — import { FullStory, init } from '@fullstory/browser'; // v1 import: // import * as FullStory from '@fullstory/browser';

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Fullstory's toolset — Browser — is a fair guide to whether it matches your workflow. It is maintained by sentry-bot; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Fullstory's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.