Replay and Fixtures

Create immutable replay records from completed runs and share deterministic fixtures across teams.

Why this exists

Teams need the exact failing payloads to debug regressions quickly. Replay records preserve normalized run outputs and point to a stable artifact key.

When to use this vs DIY script

Use FakeMCP replay when you want deterministic fixtures linked to run metadata and shareable IDs. Use DIY scripts when you only need temporary local logs.

Create replay from a run

export BASE_URL="https://fakemcp.com"
export PROJECT_TOKEN="replace_me"
export RUN_ID="run_replace_me"

curl -sS -X POST "$BASE_URL/v1/replays" \
  -H "Content-Type: application/json" \
  -H "X-Project-Token: $PROJECT_TOKEN" \
  -d "{
    \"runId\": \"${RUN_ID}\"
  }"

Response fields:

• id: replay identifier
• runId: source run
• fixtureR2Key: immutable object key
• shareSlug: short share token
• fixtureUrl: populated when PUBLIC_R2_BASE_URL is configured

Read replay metadata

export REPLAY_ID="replay_replace_me"
curl -sS "$BASE_URL/v1/replays/${REPLAY_ID}" \
  -H "X-Project-Token: $PROJECT_TOKEN"

Suggested team workflow

1. CI creates a run and fails on assertion errors.
2. CI creates a replay when failures occur.
3. Incident ticket stores runId + replayId for deterministic debugging.