Cursor setup

One command scaffolds config, local MCP, and an agent rule:

npx prodverdict init --stack nextjs-stripe --mcp --cursor-rule

Creates:

File	Purpose
prodverdict.yml	Contracts
.cursor/mcp.json	Local MCP server
.cursor/rules/prodverdict-agent.mdc	Agent guidance

Remote MCP (no billing secrets in cloud)

npx prodverdict init --remote-mcp --project-id your-project-uuid

Merges remote server entry into .cursor/mcp.json.

Agent workflow

1. doctor --format agent — verify credentials
2. check all --format agent — run contracts before PR
3. Fix findings from nextSteps in agent JSON
4. Re-run until verdict: pass

Prompts (MCP)

Ask the agent to use MCP prompts:

• setup_prodverdict — init workflow
• verify_before_pr — pre-merge checklist

Fixture mode for development

No API keys while building billing features:

npx prodverdict check access --fixtures \
  --fixtures-dir examples/nextjs-stripe/scenarios/fail-revenue-leak

See Fixture demos.