
MCP Virtual Computer
io.github.flujo-app由 GitHub 帳號 flujo-app 發布v0.2.11更新於 Oct 25, 2026
A persistent Docker or Fly computer with a Three.js interface and optional live Xfce desktop.
概覽
為助理提供一台持久的 Docker 或 Fly.io 虛擬電腦,可執行終端指令、讀寫檔案,並可選擇檢視與操作真實的 Xfce 桌面。
- 可以做什麼
- 在設定好的 Docker 容器或 Fly Machine 中執行 shell 指令
- 依 /workspace 相對路徑或絕對路徑讀取、寫入與編輯 UTF-8 文字檔
- 在 MCP App 或外部瀏覽器中開啟 Three.js 電腦檢視
- 啟用真實桌面後:擷取螢幕 PNG 或無障礙樹,並進行點擊、輸入與捲動
- 列出、切換、移動、最大化、還原、最小化與關閉 Xfce 視窗
- 可選擇向模型揭露執行狀態以及網路、桌面切換工具
- 適用情境
- 適合需要一台持久沙箱機器來執行指令、管理檔案並操作圖形桌面的情境,可在本機以 Docker 執行,也可作為重啟後仍保留的 Fly.io 永久 Machine 執行。
- 執行需求
- 以 uvx 從 PyPI 套件啟動的本機程序;預設 docker 後端需要 Docker Desktop(Windows 上可自動安裝,可能需要 WSL 2 與管理員授權),fly 後端需要 flyctl 與 Fly.io 帳號。清單要求 COMPUTER_ID(預設 agent-workstation);可選 FLY_API_TOKEN 或已快取的 flyctl 登入,以及 FLY_ORG、FLY_APP_NAME、FLY_REGION 覆寫項。僅限桌面端。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 MCP Virtual Computer,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
MCP Virtual Computer
[image]A VM for your agent. And for you.
- click the mug to switch between a virtual desktop or a real one
- unplug the network cable and cut network access
- use the computer screen like a normal screen
- copy and paste text between the host browser and the Xfce desktop
- model can use terminal, create/read/edit files, see the screen, click, type
- little fun thing: if either you or the llm types text, you see that on the keyboard; if one uses the cursor, you see the mouse move on the table.
- automatically installs Docker Desktop on Windows for local mode, or flyctl for Fly mode
MCP client example
Local Docker (default)
COMPUTER_ID defaults to agent-workstation when omitted. Set it explicitly to
keep using a named computer or to create a separate one. On a fresh Windows PC,
setup prepares WSL 2 before installing Docker Desktop. Approve the Windows
administrator prompt if shown; if a restart is required, restart Windows, reopen
your MCP client, and retry. See Windows first-use validation.
Fly.io Machine
On a fresh machine, start the MCP once, run the exact flyctl auth login command shown by its error, and restart the MCP client
What it exposes
terminal_execute— run a command in the configured Docker container or Fly Machine.read_file— read a UTF-8 text file relative to/workspaceor by absolute path.write_file— atomically write a UTF-8 text file.edit_file— replace one exact text match, or all matches when requested.computer_ui— open or attach the Three.js computer view. Its result includes both the MCP Appresource_uriand a real loopbackurl/dashboard_urlthat opens in an external browser, including for stdio clients.
DESKTOP_ENVIRONMENT defaults to true. With the real desktop enabled it
additionally exposes:
look_at_screen— return the current PNG framebuffer, AT-SPI snapshot, or both.click,type, andscroll— interact by AT-SPI element reference or coordinates.list_windowsandswitch_window— enumerate and activate real Xfce windows.move_window,maximize_window,restore_window,minimize_window, andclose_window— control a selected window by ID, title, or class.computer://screen/current.png— current live framebuffer resource.computer://screen/accessibility.json— Playwright-like AT-SPI tree with element refs, roles, names, actions, focus state, and screen bounds.
The MCP App can always call runtime_status, set_network_access, and set_desktop_environment. Set EXPOSE_LIFECYCLE_TOOLS=true to additionally expose those lifecycle controls to the model; they remain model-hidden by default.
Architecture
[image]Demo: FLUJO
[image]Demo: Claude Desktop
[image]Demo: Goose
[image]Permanent Fly Machine
Fly mode builds the bundled Xfce image with Fly's remote builder and deploys it as one permanent Machine. The root filesystem and /workspace survive MCP restarts, and the Three.js screen uses the same noVNC desktop through Fly's HTTPS/WebSocket proxy.
This is the Xfce framebuffer returned by look_at_screen from a deployed Fly Machine. The same live desktop appears on the rendered computer after computer_ui connects to VNC:
[Xfce desktop running on a permanent Fly Machine]
No app name, region, CPU size, memory size, Docker installation, or VNC configuration is required.
The package's MCP Registry declaration, including the docker and fly backend choices, is in server.json. See Fly setup for the complete first-run and authentication flow.
On first use, virtual-computer finds fly/flyctl or downloads the current official release to ~/.fly/bin. It uses a cached fly auth login session or FLY_API_TOKEN, selects the personal organization when available, creates and remembers a generated app, lets Fly choose the closest placement, and defaults to one shared CPU with 1 GB RAM.
Authentication is the only unavoidable account step. On a fresh machine, start the MCP once, run the exact flyctl auth login command shown by its error, and restart the MCP client. The first computer call can take several minutes while Fly remotely builds Xfce. Later starts attach to the same Machine.
Optional overrides remain available as FLY_ORG, FLY_APP_NAME, FLY_REGION, FLY_API_TOKEN, and the --fly-* flags. Set AUTO_INSTALL_FLYCTL=false to require a preinstalled CLI. Deleting or factory-resetting the computer destroys its persistent Fly root filesystem; ordinary MCP shutdown leaves the permanent Machine running. Stop or delete it from Fly when you no longer want it to incur usage.
License and origin
MIT licensed. This project is a persistent-computer fork of Kilntainers with Docker and Fly backends.
來源:README.md,提交 3bd3895
工具
0版本歷史
1- v0.2.11最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
