Option A: connect an MCP client
Mirrors hosts an MCP server that exposes the full product surface — build, explore, query, and eval mirrors from Claude Code, Cursor, VS Code, ChatGPT, Codex, and any other MCP client. Sign-in happens in the browser on first use; no API key needed./mcp → mirrors → Authenticate and ask your client to build a mirror from your traces. See MCP server for every client, one-click installs, and headless setups.
Option B: add the collector
Get an API key
Sign in at runmirrors.com and mint a workspace API key (
mk_live_…) under Settings → API keys.Add two lines to your agent
Install the collector and initialize it before your agent runs. It auto-instruments LangChain/LangGraph, Anthropic, and OpenAI, and ships traces in the background — non-blocking, and it never raises into your app.Run your agent normally — traces start streaming. Details per language: Python, TypeScript, Go.
Build a mirror
From the dashboard (Ingest → Build), or from the CLI:Mirrors turns the traces into a schema, a seeded database, and tool bindings — a runnable copy of your agent’s world, scored per tool for fidelity.
Replay and query it
Gate merges in CI
In Quickstart → CI eval gate, connect the GitHub App and bind your repo to a mirror and an eval set. Every PR that touches your agent replays the eval set and reports a Mirrors eval gate status check you can make required. See CI gate.
Next steps
How it works
Fidelity scoring, deterministic seeding, business context, and evals.
CI gate
Block regressions at the pull request, Vercel-style.
