Cursor MCP
Same runner as the CLI. Staging credentials stay in your environment, not in this config.
1. Build the binary
cd drawer-two && make build
Use the absolute path to bin/drawertwo below (note the hyphen: drawer-two, not drawertwo).
2. Cursor config
Settings → MCP, or edit your MCP JSON. Example:
{
"mcpServers": {
"drawertwo": {
"command": "/home/andrew/drawer-two/bin/drawertwo",
"args": ["mcp"],
"env": {
"DRAWERTWO_SCENARIOS_ROOT": "/home/andrew/drawer-two/scenarios",
"DRAWERTWO_PROFILE": "/home/andrew/drawer-two/.drawertwo/staging.yaml"
}
}
}
}
For fixture runs, DRAWERTWO_PROFILE is optional. For staging mode, set DRAWERTWO_STAGING_BASE_URL and DRAWERTWO_STAGING_BEARER in the MCP env block or your shell.
3. Tools
| Tool | Purpose |
|---|---|
list_scenarios | Story cards and scenario IDs |
validate_staging_profile | Env check; optional reachability ping |
create_run | mode: fixture or staging; fixture_variant: safe | leak | not_sure |
get_run_status | Status for a run_id |
get_run_report | Verdict and pack paths |
Example fixture run
{
"scenario_id": "module-a-two-hands",
"mode": "fixture",
"fixture_variant": "leak"
}
If the base URL does not look like staging or localhost, tool responses may include a WARNING. Use authorized staging only.