# Flyto Core

Execution engine for AI agents with 482 registered modules and 41 recipes. Runs browser automation, calls APIs, manages files, and interfaces with ROS 2.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 484
- Author: flytohub
- License: Apache-2.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/flytohub/flyto-core
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/mcp/flyto-core

## What it does

Flyto Core connects agents to the Flyto2 execution runtime on Python 3.10+. It bundles 482 modules and 41 predefined workflows for API communication and local file operations. The engine exposes these actions directly through the MCP standard.

Execution history is tracked at every step. Rather than trusting simple status codes, the runtime compares reported evidence against action contracts. This makes inspection straightforward. If a job fails, runs can rely on checkpoints and replay.

Hardware control works through a separate ROS 2 adapter, currently developed alongside TurtleBot3. Physical robot movement will not execute without trusted host confirmation. Browser workflows require Playwright and Chromium installed locally.

## Requirements
- Needs: Python and uv (commands run via uvx)
- Works with: Playwright

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add flyto-core -- uvx flyto-core
```
uvx runs the command named after the package; if the README names another one, use uvx --from flyto-core <command>

### Codex

**Platform CLI**
```bash
codex mcp add flyto-core -- uvx flyto-core
```
uvx runs the command named after the package; if the README names another one, use uvx --from flyto-core <command>

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "flyto-core": {
            "command": "uvx",
            "args": [
                "flyto-core"
            ]
        }
    }
}
```
uvx runs the command named after the package; if the README names another one, use uvx --from flyto-core <command>

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "flyto-core": {
            "type": "stdio",
            "command": "uvx",
            "args": [
                "flyto-core"
            ]
        }
    }
}
```
uvx runs the command named after the package; if the README names another one, use uvx --from flyto-core <command>

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add flyto-core uvx flyto-core
```
uvx runs the command named after the package; if the README names another one, use uvx --from flyto-core <command>

## When to use it
- Automate browser scraping workflows with Chromium
- Execute multi-step automation routines from YAML files
- Dispatch commands to ROS 2 hardware adapters
- Verify tool execution outputs against step contracts

## Example prompts
- Run the competitor-intel recipe for https://github.com/pricing using flyto
- Take a screenshot of the target site and store the raw data
- Inspect the execution record for the latest workflow run

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 386989
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33918
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81115
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [Codebase Memory](https://affpapa.org/en/nevibecode/mcp/codebase-memory.md) — MCP server · ★ 47392
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43872

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md