Developer · Local MCP server
MCP Virtual Computer
A persistent Docker or Fly computer with a Three.js interface and optional live Xfce desktop.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.flujo-app/mcp-virtual-computer- Version
- 0.2.11
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-09-02
- Updated
- 2026-09-02
- Publisher
- flujo-app (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/flujo-app) · how
- Listed under
- Docker MCP servers
- Website
- github.com/flujo-app/mcp-virtual-computer
- Repository
- github.com/flujo-app/mcp-virtual-computer
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | mcp-virtual-computer | 0.2.11 | stdio |
How to connect MCP Virtual Computer
MCP Virtual Computer runs locally from a Python package published to PyPI: mcp-virtual-computer version 0.2.11. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx mcp-virtual-computer. It reads these environment variables: BACKEND, COMPUTER_ID (required), DESKTOP_ENVIRONMENT, NETWORK_ACCESS, AUTO_INSTALL_DOCKER, AUTO_INSTALL_FLYCTL, FLY_API_TOKEN (secret) and EXPOSE_LIFECYCLE_TOOLS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp-virtual-computer": {
"command": "uvx",
"args": [
"mcp-virtual-computer"
],
"env": {
"BACKEND": "<value>",
"COMPUTER_ID": "<value>",
"DESKTOP_ENVIRONMENT": "<value>",
"NETWORK_ACCESS": "<value>",
"AUTO_INSTALL_DOCKER": "<value>",
"AUTO_INSTALL_FLYCTL": "<value>",
"FLY_API_TOKEN": "<secret>",
"EXPOSE_LIFECYCLE_TOOLS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from flujo-app (GitHub)
| Server | Runs |
|---|---|
| MCP Sandbox Computer VM for AINamed Docker and Fly Machine sandbox computers with an interactive MCP App dashboard. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| MCP Tool FactoryGenerate MCP servers from natural language, OpenAPI specs, or database schemas. | Local · stdio |
| MCP Unifi ApplicationsQueryable UniFi API docs: endpoint search, schemas, code examples. No controller access. | Local · stdio |
| MCP Verify ClaimForce evidence-gated, tiered claim reporting (FACT/INFERENCE/SPECULATION). No-LLM. | Local · stdio |
| MCP Vibe CheckerVibe-check your code - personality types, energy ratings, aesthetic suggestions. | Local · stdio |
| MCP VS CodeA self-hosted VS Code workbench embedded as an interactive MCP App. | Local · stdio |
| MCP Whatsapp CloudMCP server for WhatsApp Cloud API (Meta) - messages, media, and templates via Graph API. | Local · stdio |
| MCP Whoisxmlapi32 WHOIS, DNS, IP, threat intelligence, email, and bulk tools for AI agents via WhoisXML API. | Local · stdio |
| MCP X402 AcceptSelf-hosted MCP proxy that puts an x402 paywall in front of an existing MCP server. | Local · stdio |