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 Toolkit
Agent Toolkit · Community
Agent ready

Safe staging for this asset

This asset is staged first. The copied prompt tells the agent to inspect the staged files and ask before activating scripts, MCP config, or global config.

Stage only · 17/100Policy: stage
Agent surface
Any MCP/CLI agent
Kind
Mcp Config
Install
Stage only
Trust
Trust: Established
Entrypoint
Asset
Safe staging command
npx -y tokrepo@latest install c2e51f85-f03b-5c92-afaa-f028973d5aa4 --target codex

Stages files first; activation requires review of the staged README and plan.

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

Hister — Self-Hosted Search Engine (MCP-ready)

Hister is a privacy-focused self-hosted search engine that full-text indexes visited sites locally, with optional semantic search and MCP agent access.

MCP Configs
MCP Hub

Frappe Assistant Core — MCP Bridge for ERPNext

Frappe Assistant Core connects MCP-ready LLMs to ERPNext via OAuth and audit logging (per README). Verified 223★; pushed 2026-05-14.

MCP Configs
MCP Hub

Solace Agent Mesh — Event-Driven Agent-to-Agent Messaging

Solace Agent Mesh provides event-driven messaging for multi-agent systems so tools and agents coordinate through durable topics with replayable event logs.

Skills
Agent Toolkit

Claude Code Agent: DOTNET Core Expert

Use when building .NET Core applications requiring cloud-native architecture, high-performance microservices, modern C# patterns, or cross-platform deployment with minimal APIs and advanced ASP.NET Core features. Specifically:\\n\\n<example>\\nContext: Buil...

Skills
TokRepo精选
◈Home🔍Search👤Me