MCP Catalogs
Homeflyto-core screenshot

flyto-core

by flytohub·270·Score 51

An MCP server for AI agent automation with 412 modules, execution tracing, replay functionality, and built-in recipes.

browser-automationdeveloper-toolsweb-scraping
48
Forks
3
Open issues
this month
Last commit
2d ago
Indexed

Overview

flyto-core is an open-source execution engine for AI agents that provides a comprehensive set of tools through MCP. It offers 412 modules across 78 categories including browser automation, API calls, file operations, and data processing. The system features execution tracing, replay functionality from any step, and evidence snapshots. Users can create workflows using YAML configuration files with over 30 built-in recipes available for common automation tasks. The server can be used as an MCP server, HTTP API, Python API, or CLI tool, making it versatile for different integration needs.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:Competitive intelligence gathering through automated web scraping and performance monitoring
you:Automated testing of web applications with screenshot capture and performance metrics
you:Data extraction and transformation workflows across various web sources and APIs
you:How is flyto-core different from Playwright?
you:Can I use flyto-core without MCP?

When to choose this

Choose flyto-core when you need comprehensive browser automation with full traceability and replay capabilities, especially when working with complex multi-step workflows involving browser interaction, API calls, and file operations.

When NOT to choose this

Avoid flyto-core if you need simple, one-off browser interactions without the overhead of a full automation engine, or if you require native mobile app automation (flyto-core focuses on web browsers).

Tools this server exposes

12 tools extracted from the README
  • string.reverse

    Reverse the characters in a string

  • browser.launch

    Launch a browser instance

  • browser.goto

    Navigate to a URL in the browser

  • browser.evaluate

    Execute JavaScript code in the browser

  • browser.screenshot

    Take a screenshot of the current page

  • browser.viewport

    Set the browser viewport size

  • browser.performance

    Get browser performance metrics

  • browser.close

    Close the browser instance

  • file.write

    Write content to a file

  • file.read

    Read content from a file

  • array.filter

    Filter an array based on a condition

  • api.call

    Make an API request to a web service

Comparable tools

playwrightseleniumscrapyzapier

Installation

Install

pip install flyto-core            # Core engine + CLI + MCP server
pip install flyto-core[browser]   # + browser automation (Playwright)
playwright install chromium        # one-time browser setup

MCP Configuration

Add to your MCP config:

{
  "mcpServers": {
    "flyto-core": {
      "command": "python",
      "args": ["-m", "core.mcp_server"]
    }
  }
}

Or via Claude CLI:

claude mcp add flyto-core -- python -m core.mcp_server

FAQ

How is flyto-core different from Playwright?
Flyto-core wraps Playwright with execution tracing, replay functionality, and over 400 additional modules for different task types. It provides a more structured workflow approach where each step can be traced and replayed independently.
Can I use flyto-core without MCP?
Yes, flyto-core can be used as a CLI tool, HTTP API, or Python API independently of MCP. MCP is just one integration method.

On Hacker News

Recent discussion from the developer community.

Compare flyto-core with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.