Automate safely with Operator, API, and MCP
Schedule reliable work and bring PreFlight evidence into CI and coding tools without opaque production writes.
Once the core operating loop is working, automate the repeatable parts without letting an agent make unreviewed changes. PreFlight provides scheduled tasks, an Operator grounded in workspace evidence, a REST API, and MCP access for compatible development tools. Use these interfaces to bring verified context into the places your team already works.
Schedule recurring work
Open Automations to schedule checks, reports, and response workflows. Give each task a narrow purpose, an owner, and an output channel. For example, run a daily audit summary, watch a critical uptime endpoint, or collect a revenue snapshot after a deployment window.
Review the durable run history before increasing cadence. A task that fails noisily every five minutes is not protection; it is a configuration problem that hides the next real incident.
Use Operator for grounded questions
Operator works from workspace evidence such as health, incidents, reports, deploy history, revenue, and growth data. Ask it to explain what changed, identify the most important unresolved risk, or run an approved check. Read the tools and evidence behind an answer before acting on a recommendation.
Connect the API or MCP server
The REST API is suited to CI, internal dashboards, and scripted reporting. MCP is suited to coding tools that need to inspect PreFlight context or run approved actions. Create an API key in Settings, keep it in a secret manager, use least privilege, and rotate it when a person or integration no longer needs access.
See the dedicated API reference for request authentication, response shapes, and the MCP configuration format.
Keep writes explicit
Use automation to surface evidence and prepare recovery work, not to make opaque production changes. A good workflow can open an issue, notify an owner, or require a human approval before a write. That design keeps PreFlight’s history useful during an incident and makes it clear who changed what, when, and why.