Use ScenarioDeck with MCP

Coding agents can follow reproduction steps, but those steps often omit the role, route, form values, and supporting API behavior that make a bug reproducible. ScenarioDeck gives an agent a State Card as authoritative local context.

State Card ID
→ agent inspects or opens it through MCP
→ supported surrounding requests stay replayed
→ selected dependency can route to Local
→ agent changes code
→ reopen the same State Card
→ compare the safe result

Configure your MCP client

In Desktop Settings, choose Copy MCP config. Add the copied local stdio configuration to a compatible coding-agent client. The server is local: it does not upload State Cards, Auth Bindings, or application traffic.

The CLI can print the same safe configuration:

scenariodeck mcp config

Authentication boundary

MCP can report a Persona requirement or a safe auth status. It cannot read, export, or create raw Auth Binding values. If a Clean Session needs re-authentication, a human must complete the permitted local flow before the agent opens that state.

MCP makes a state repeatable; it does not promise autonomous root-cause analysis or universal reproduction.