MCP server

The Backstory MCP server speaks Streamable HTTP at https://api.backstory.io/mcp and authenticates with a scoped API token. Create a token with the mcp scope under Organization → API tokens. PHI organizations can disable the server or restrict it to non-PHI projects.

Tools

Tool	What it returns
list_recent_issues	Open issue clusters ranked by impact, with counts and releases
get_session_transcript	The Semantic Transcript for a session (masked, cited)
get_session_summary	The automatic summary artifact when one exists
get_error_context	Symbolicated stack, request, and surrounding steps for an error
get_repro_steps	Repro steps and the generated Playwright test (creates a deep analysis if none is cached)
get_dom_snapshot_at	The reconstructed DOM at a moment, as sanitized HTML
get_request_details	Request metadata, timing, and linked backend trace
search_sessions	Natural-language search over sessions
get_issue_cluster	Cluster detail with samples and the AI explanation

Client configuration

Claude Code (~/.claude/settings.json or project .mcp.json):

{
  "mcpServers": {
    "backstory": {
      "type": "http",
      "url": "https://api.backstory.io/mcp",
      "headers": { "Authorization": "Bearer backstory_…" }
    }
  }
}

Cursor and other clients accept the same URL and header.

Example

“Fix the upload 413 issue from Backstory.”

The agent calls list_recent_issues, picks the cluster, calls get_repro_steps and get_error_context, edits upload.ts, runs the generated test, and opens a PR. Every tool response includes citations back to replay moments so a human can verify.

Status

The MCP server ships with the AI phase. Tokens with the mcp scope can be created now; the endpoint returns 503 until the feature is enabled for your organization.