zenf-mcp — Model Context Protocol Integration & Orchestration Engine

Operating Invariants

1. Short-Circuit on Connected State:
   • When the zenfd MCP server is verified as already configured and valid (the configuration file exists and the zenfd entry points to a valid, existing binary):
     • Emit a concise status report confirming the connected state.
     • Halt the turn immediately. Strictly forbid any additional file modifications, command executions, or redundant actions.
2. Zero-Touch Without Affirmative Human Review & Confirmation:
   • If the zenfd MCP server is not yet connected or has an invalid/missing configuration:
     • Strictly forbid running setup commands or overwriting user configuration files automatically.
     • Display the exact CLI command (e.g. apps/daemon/bin/zenfd mcp setup --client agy), target configuration file path, and proposed JSON preview for Human Review & Confirmation.
     • Begin execution only AFTER receiving explicit, affirmative user confirmation.
3. SSOT Alignment:
   • The MCP server connects directly to the SQLite WAL database (~/.zenforge/state.db) via stdio transport as the durable Single Source of Truth (SSOT).

Domain Rubric