MCP ConfigsMay 14, 2026·2 min read

flyto-core — Replayable Agent Execution Engine

flyto-core is an engine with traced, replayable steps and MCP-native modules; verified 270★ and includes 32+ recipes to start.

Agent ready

This asset can be read and installed directly by agents

TokRepo exposes a universal CLI command, install contract, metadata JSON, adapter-aware plan, and raw content links so agents can judge fit, risk, and next actions.

Native · 94/100Policy: allow
Agent surface
Any MCP/CLI agent
Kind
Mcp
Install
Pip
Trust
Trust: Established
Entrypoint
flyto recipe competitor-intel --url https://github.com/pricing
Universal CLI install command
npx tokrepo install c2e51f85-f03b-5c92-afaa-f028973d5aa4
Intro

flyto-core is an engine with traced, replayable steps and MCP-native modules; verified 270★ and includes 32+ recipes to start.

Best for: Teams who need step-by-step traces, retries-from-step, and repeatable automation (browser, file, queues)

Works with: Python 3.x; optional Playwright for browser recipes; README shows CLI + MCP server install options

Setup time: 8-18 minutes

Key facts (verified)

  • GitHub: 270 stars · 48 forks · pushed 2026-05-13.
  • License: Apache-2.0 · owner avatar + repo URL verified via GitHub API.
  • README-backed entrypoint: flyto recipe competitor-intel --url https://github.com/pricing.

Main

  • Model automations as explicit steps so you can trace timing, capture artifacts, and replay only the failing segment.

  • Prefer recipes for onboarding: run a built-in recipe before authoring custom pipelines, and keep success criteria explicit.

  • Persist artifacts as contracts: save screenshots/reports deterministically so runs can be reviewed like CI logs.

Source-backed notes

  • README quickstart shows pip install flyto-core[browser] && playwright install chromium then flyto recipe ....
  • README shows replaying from a specific step: flyto replay --from-step 8.
  • Repo description mentions 412 modules and MCP-native execution with triggers/queue/versioning/metering (verified).

FAQ

  • Is this just a set of scripts?: No — it’s an engine with tracing and replay, not ad-hoc shell scripts.
  • Do I need Playwright?: Only for browser recipes; core engine can run non-browser steps too.
  • How do I keep runs reproducible?: Pin versions, keep inputs explicit, and persist artifacts + traces per run.
🙏

Source & Thanks

Source: https://github.com/flytohub/flyto-core > License: Apache-2.0 > GitHub stars: 270 · forks: 48

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets