Validation: `mcp-flowgate check`

The open-source platform validates your gateway config, workflows, skills, and scripts at load time with mcp-flowgate check. It exits 0 if everything resolves; 1 otherwise. Run it before you start the gateway to catch config issues before any workflow runs.

mcp-flowgate check --config gateway.yaml

check confirms that skill and script verbs are in their closed enums, every subject starts with a blessed root, every skills: ref resolves, the script executor’s subject resolves into the workflow snapshot, blackboard slots line up with output: mappings, and every state is reachable. See Validation rules V1–V23 for the full list of checks.

The pre-flight doctor battery

The open agentic runtime (flowgate TUI, in the mcp-flowgate-tui crate) ships a richer pre-flight doctor — one that probes provider API keys, re-checks models.yaml bindings against each provider’s live /v1/models catalog, resolves each delegate: state through the resolver, and verifies external script file:// URIs before a workflow walk.

The open platform still load-validates everything structural via mcp-flowgate check; doctor adds the runtime/credential pre-flight that only matters when the agentic runtime is about to spawn sub-agents.

See also

• models.yaml — the affinity/tier model-binding config.
• Validation rules — what mcp-flowgate check catches at config load.