Offers tools for managing Docker containers, including running, stopping, inspecting, and viewing logs.
Provides Git operations such as cloning repositories, committing changes, and viewing diffs.
Enables sending and searching emails through Gmail.
Integrates with Google services including Gmail and Google Calendar for sending emails and managing events.
Allows interaction with Notion API for creating, updating, and querying pages and databases.
Provides integration with OpenAI's API for AI-powered text generation and completion.
Offers caching capabilities using Redis, including set, get, delete, and clear operations.
Enables sending messages and interacting with Slack workspaces.
Enables sending messages and interacting with Telegram bots.
Say you want to check a website, grab screenshots, collect some data, and save a report.
Run this:
pip install "flyto-core[browser]"
playwright install chromium
flyto recipe competitor-intel --url https://github.com/pricingThat's a real workflow. No agent prompt needed. It opens a browser, runs the steps, and saves the results.
Want to poke around?
flyto recipes # see the built-in workflows
flyto modules # browse the tools
flyto run your-workflow.yaml # run your ownThere are 482 registered modules and 41 built-in recipes in the current Core inventory. Browser stuff, APIs, files, data, tests, and plenty more. Use what you need.
Related MCP server: context-crystal
We're already connecting Flyto2 to a real TurtleBot3 using ROS 2.
The robot runs its normal ROS 2 / Nav2 stack. A separate adapter talks to it. Flyto2 handles the software steps and their execution records.
No custom Flyto2 firmware on the robot. No motor drivers crammed into this repo.
This isn't a claim that every robot is plug-and-play. The current combined setup still needs its full end-to-end hardware sign-off. But the ROS 2 adapter and real-robot development are already here.
This is flyto-core, the Python execution engine behind Flyto2.
You can call it from Python, run YAML workflows, use its local HTTP API, or hook it into an AI client through MCP.
pip install flyto-core
python -m core.mcp_serverYour agent gets access to Core's tools. Moving a physical device still requires a trusted host to approve the action.
Different device software stack? Different pack. That's how ROS 2 and other integrations stay separate without turning Core into a giant pile of device drivers.
This part matters.
When a workflow runs, Flyto2 keeps a record of each step. If something fails, you can inspect the run and use checkpoints or replay where it's safe to do so.
And if a tool says “done”? Core can check the evidence it reports against the action's contract. It doesn't just throw away the trail once the command returns.
That's it. Run something, see what happened, build the next thing.
Website · Documentation · PyPI · YouTube · Issues
Flyto2 is the product. flyto-core is the Python package. Licensed under Apache 2.0. Security reports: GitHub advisories.
This server cannot be deployed
Hosted runtime for persistent agent teams, durable workflows, memory, schedules, and goals.
AI-native programming language and toolchain for accountable, verifiable agent-driven development.
Deterministic reasoning stack for AI agents: simulate, decide & compute, plus cross-domain tools.
Pre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof.
