Flyto2 Runtime

io.github.flytohubPublished by GitHub account flytohubv1.0.8Updated Oct 24, 2026

Self-hosted MCP runtime for ChatGPT to edit files, run commands, and test local projects.

VerifiedStreamable HTTPWeb executableFiles & StorageDeveloper Tools

Overview

AI-generated overview

A self-hosted MCP runtime that lets ChatGPT read and edit files, run commands, tests, and Git inside approved local project folders.

What you can do
Flyto2 Runtime runs on your own machine and exposes MCP over an HTTPS endpoint so a connected assistant can work inside approved workspace roots. It can read and edit project files, run terminal commands, tests, builds, package scripts, and Git, and keep long-running processes alive. It also reports what changed, supports durable task recovery and MCP event callbacks, and can optionally hand work to local coding agents or connect to Flyto2 Cloud.
When to use it
Use it when you want an assistant to actually modify and test a local codebase instead of pasting code and errors back and forth. It suits iterative coding, running builds and tests, and long-running commands that should survive a dropped connection.
Requirements
A local machine running the runtime, with Node.js 22.19 or newer and below 27 for source installs; packaged macOS and Windows downloads bundle Node.js and cloudflared. A public HTTPS URL reaching the local runtime is needed, either a free Cloudflare quick tunnel or your own fixed HTTPS URL, reverse proxy, Tailscale Funnel, or ngrok domain. Remote MCP access uses OAuth.
Before you install
The runtime can edit files, run shell commands, and use Git on your machine, so a connected client should be treated as a trusted coding partner. Access is limited to workspace roots you approve, but shell execution is not a full OS sandbox. Keep the Owner credential, tunnel credentials, and auth.json private. A quick trycloudflare.com URL changes on restart, so use a fixed hostname if you need a stable address.

Installation

In SourceWeft

  1. Open Flyto2 Runtime in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.8LatestSep 23, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.