Everything else follows from the trace: because each step's result is recorded, resuming at step eight is instant for the first seven and re-runs only what broke. That matters most on the jobs that are slow at one point and cheap everywhere else — a page load, a screenshot, a Web Vitals capture — which is exactly what the browser modules do.
A local execution engine with an MCP server: YAML recipes composed from registry-backed modules, executed deterministically, with a trace of every step.
- 480 registry-backed modules across 88 catalog categories — browser automation, HTTP and API calls, data transforms, files, crypto, verification, triggers and queue modules
- Browser work end to end: launch, goto, evaluate, screenshot, viewport changes, Web Vitals capture and close, each step timed
- Replay from a chosen step — earlier steps come back instantly from the trace, and only the failing one re-executes
- Packaged recipes you can run by name with parameters, plus your own YAML
- Evidence capture: screenshots, metrics and a JSON report saved alongside the run
- An HTTP surface with the MCP endpoint at POST /mcp, returning an Mcp-Session-Id on initialization
Python 3.10 or higher. pip install flyto-core gets the engine, CLI and MCP server; the browser extra plus playwright install chromium adds browser automation. The published package is flyto-core, registered as io.github.flytohub/flyto-core with stdio transport. The MCP HTTP route uses bearer auth.
One command — pip install flyto-core