Environment variables

Reality Harness MCP (Levels 1 and 2)

Variable	Required for live mode	Description
`CONQUOREUM_CONVEX_URL`	Yes	The shared Conquoreum API endpoint — `https://api.conquoreum.com`. Public configuration, not a secret.
`CONQUOREUM_API_TOKEN`	Yes	Your `cqk_` key. For `reality_harness_submit_outcome`, the key must also carry `rhp:outcome`. User-specific — never commit, never log.
`REALITY_REPORT_DIR`	No	Absolute path under your home directory where `reality_harness_write_report` writes notes. Falls back to a default location if unset or invalid.

If either required variable is unset, the MCP runs in mock mode — every tool is still callable, but nothing reaches Conquoreum.

Variable	Required	Default	Notes
`VISION_CONVEX_URL`	Yes	—	The shared Conquoreum endpoint (same one used above).
`VISION_API_TOKEN`	Yes	—	A `cqk_` key with the `obsidian:sync` scope.
`VISION_VAULT_PATH`	Yes	—	Absolute path to your Obsidian vault root.
`VISION_STATE_PATH`	No	`<cwd>/vision-harness-state.json`	Where the bridge tracks what it’s already synced.
`VISION_CONFIG_PATH`	No	`<cwd>/vision-harness.config.json`	Your allowlist + poll interval.
`VISION_POLL_SEC`	No	`20`	How often `watch` mode polls (minimum 5).

Never hardcode a token in a script or commit it to a repo. Read it from a local .env file or your MCP client’s own env configuration at runtime.