M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
F

Flyto2 Core

Community
Open-source execution engine for AI agents with 468 modules, MCP-native, triggers, queue, versioning, and metering.
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #258 of 438
Stars
★ 484 Very popular
Transport
stdio (local process)
Runtime
Python 3.9+
Credentials
No credential needed
License
Apache-2.0
Last commit
Tools
1
50FMRS · D

Flyto2 Core is a feature-rich open-source execution engine, particularly suited for automation scenarios needing reliable, replayable workflows. Its modular architecture and MCP support make integration easy, but self-hosting requires technical proficiency.

Strongest · Documentation 12/20 Weakest · Reliability 8/20

Reliability
8/20
Security and permissions
8/20
Maintenance
12/20
Documentation
12/20
Setup experience
10/20
Why each score
Reliability 8/20
Evidence: README shows clear installation and usage examples, including an MCP configuration snippet, indicating the server likely starts via stdio. However, only static files are provided; there is no verifiable CI or test results. Therefore, confidence in reliability is limited; happy path plausible, but error handling and edge cases unverified. Deduction: lack of execution evidence, and alignment of tool list with real behavior unconfirmed.
Security and permissions 8/20
Evidence: README mentions hardened HTTP clients and file access, indicating security awareness, and Apache-2.0 license and SECURITY.md presence are positive. But no specific details on credential handling, permissions, or data boundaries; configuration docs may include security settings. Deduction: lack of implementation details, and potential for browser automation and arbitrary code execution, but confirmation mechanisms unverified.
Maintenance 12/20
Evidence: Repository active (479 stars, 1 open issue), version 2.26.12, Apache-2.0 license, and contact emails suggest maintenance. But no commit history, release frequency, or dependency update evidence. Deduction: lack of specific maintenance activity evidence, and only 1 open issue may indicate low issue response, but insufficient information.
Documentation 12/20
Evidence: README provides extensive documentation (architecture, configuration, module catalog, recipe examples), and docs directory exists. But docs may contain marketing language and contradictory numbers (452 vs 468). Deduction: lack of actual verification, and depth of docs unknown; security configuration details may be in separate docs.
Setup experience 10/20
Evidence: README provides simple pip install, MCP config example (stdio), and optional browser extension. But requires extra Playwright browser install, and maybe Python version requirements. Deduction: config block correctness unverified, and manual browser installation, but examples clear.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesWrites / deletes local filesRuns commands or codeUses the networkControls a browser

Best for

  • Developers needing reliable, replayable workflow automation
  • Teams wanting deterministic tools for AI agents
  • Users requiring unified execution engine for browser, API, and file operations

Not for

  • Users looking for a hosted cloud service rather than self-hosting
  • Users needing non-Python language support
  • Users needing simple scripts without advanced replay and evidence features

Required permissions

  • File system read/write (sandboxed path guard)
  • Network requests (guarded HTTP clients)
  • Environment variable reads (93 documented readers)
  • Browser automation via Playwright

Risks and side effects

  • Sandbox path guard may block some file writes
  • Network access may be restricted, affecting external API calls
  • Requires Python environment for MCP server
  • Active development may change features

Setup

Before you start

Runtime：Python 3.9+

FLYTO_TEST_PASSWORD optionalsecret Placeholder login password used in the flyto2-ui-login-smoke recipe example; comes from your own test account, not required.
GITHUB_TOKEN optionalsecret GitHub personal access token used in the github-issue recipe example; set only when using that integration recipe.
Other optional settings (1)
SLACK_URL optional Slack webhook URL used in the scrape-to-slack recipe example; set only when using that integration recipe.
  1. Install Python 3.9+.
  2. Run pip install flyto-core[browser] and playwright install chromium.
  3. Use python -m core.mcp_server or add via MCP config.
claude_desktop_config.json 
{
  "mcpServers": {
    "flyto-core": {
      "command": "python",
      "args": ["-m", "core.mcp_server"]
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "flyto-core": {
      "command": "python",
      "args": [
        "-m",
        "core.mcp_server"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

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

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

Run pip install flyto-core, add the flyto-core entry (python -m core.mcp_server) to your MCP config, restart the client, and confirm the module tools (e.g. browser.launch, browser.screenshot, file.write) appear in the tool list — or run flyto recipe competitor-intel --url https://github.com/pricing to verify the CLI works.

Troubleshooting

  1. Ensure Python 3.9+ is installed
  2. If browser automation fails, check Chromium installation
  3. Verify MCP config command and arguments are correct
  4. Consult configuration reference for security-related environment variables

Things to try

Once connected, you can ask your AI assistant things like:

  • Open https://example.com/pricing, take a desktop and a mobile screenshot, and extract the prices into a JSON report
  • Run the site-audit recipe and give me a full SEO, accessibility, and performance report
  • Scrape the titles and links from https://news.ycombinator.com and export them to CSV
  • Run my price-monitor workflow and, if a step fails, replay from that step only

Tools 1

468 registry-backed modules
468 registry-backed modules across 85 catalog categories including browser, API, data, file, verification, and more.

Use cases

Browser automation and web scraping
API integration and workflow orchestration
Replayable YAML recipe execution
Evidence capture and audit trails

Supported clients

Claude Desktop

Listed from the project's documentation, not tested by this site.

Overview

Flyto2 Core is the open-source execution kernel behind Flyto2, designed for AI agents and workflow automation. It offers a registry-backed module library, MCP-native transport, YAML recipes, evidence capture, replay, triggers, queue, versioning, and metering. It is suitable for browser automation, API integration, web scraping, replayable YAML flows, evidence capture, and deterministic tools that agents can call without generating unreviewed code.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision 795d07e64fab Data synced 2026-10-13 Read the FMRS scoring method