A persistent Docker or Fly computer with a Three.js interface and optional live Xfce desktop.
Connect Runs on your machine
claude mcp add mcp-virtual-computer -e BACKEND=<BACKEND> -e COMPUTER_ID=<COMPUTER_ID> -e DESKTOP_ENVIRONMENT=<DESKTOP_ENVIRONMENT> -e NETWORK_ACCESS=<NETWORK_ACCESS> -e AUTO_INSTALL_DOCKER=<AUTO_INSTALL_DOCKER> -e AUTO_INSTALL_FLYCTL=<AUTO_INSTALL_FLYCTL> -e FLY_API_TOKEN=<FLY_API_TOKEN> -e EXPOSE_LIFECYCLE_TOOLS=<EXPOSE_LIFECYCLE_TOOLS> -- uvx mcp-virtual-computer==0.2.11
{
"mcpServers": {
"mcp-virtual-computer": {
"command": "uvx",
"args": [
"mcp-virtual-computer==0.2.11"
],
"env": {
"BACKEND": "<BACKEND>",
"COMPUTER_ID": "<COMPUTER_ID>",
"DESKTOP_ENVIRONMENT": "<DESKTOP_ENVIRONMENT>",
"NETWORK_ACCESS": "<NETWORK_ACCESS>",
"AUTO_INSTALL_DOCKER": "<AUTO_INSTALL_DOCKER>",
"AUTO_INSTALL_FLYCTL": "<AUTO_INSTALL_FLYCTL>",
"FLY_API_TOKEN": "<FLY_API_TOKEN>",
"EXPOSE_LIFECYCLE_TOOLS": "<EXPOSE_LIFECYCLE_TOOLS>"
}
}
}
}
{
"mcpServers": {
"mcp-virtual-computer": {
"command": "uvx",
"args": [
"mcp-virtual-computer==0.2.11"
],
"env": {
"BACKEND": "<BACKEND>",
"COMPUTER_ID": "<COMPUTER_ID>",
"DESKTOP_ENVIRONMENT": "<DESKTOP_ENVIRONMENT>",
"NETWORK_ACCESS": "<NETWORK_ACCESS>",
"AUTO_INSTALL_DOCKER": "<AUTO_INSTALL_DOCKER>",
"AUTO_INSTALL_FLYCTL": "<AUTO_INSTALL_FLYCTL>",
"FLY_API_TOKEN": "<FLY_API_TOKEN>",
"EXPOSE_LIFECYCLE_TOOLS": "<EXPOSE_LIFECYCLE_TOOLS>"
}
}
}
}
{
"servers": {
"mcp-virtual-computer": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-virtual-computer==0.2.11"
],
"env": {
"BACKEND": "<BACKEND>",
"COMPUTER_ID": "<COMPUTER_ID>",
"DESKTOP_ENVIRONMENT": "<DESKTOP_ENVIRONMENT>",
"NETWORK_ACCESS": "<NETWORK_ACCESS>",
"AUTO_INSTALL_DOCKER": "<AUTO_INSTALL_DOCKER>",
"AUTO_INSTALL_FLYCTL": "<AUTO_INSTALL_FLYCTL>",
"FLY_API_TOKEN": "<FLY_API_TOKEN>",
"EXPOSE_LIFECYCLE_TOOLS": "<EXPOSE_LIFECYCLE_TOOLS>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
BACKENDOptional | Computer provider. Use docker for a local container or fly for a permanent Fly Machine. |
COMPUTER_IDRequired | Stable identity of the one persistent computer. |
DESKTOP_ENVIRONMENTOptional | Start the real Xfce desktop instead of the virtual desktop. |
NETWORK_ACCESSOptional | Allow outbound network access from the computer. |
AUTO_INSTALL_DOCKEROptional | On Windows, install and start Docker Desktop lazily when needed. |
AUTO_INSTALL_FLYCTLOptional | Download flyctl into the user profile when it is missing. |
FLY_API_TOKENOptional, secret | Optional Fly API token. A cached flyctl login is also supported. |
EXPOSE_LIFECYCLE_TOOLSOptional | Also expose runtime status and network/desktop switching tools to the model. The MCP App can always use them. |
Details
| Package | [email protected] (PYPI, stdio) |
| First published | 2 Sep 2026 |
| Last updated | 2 Sep 2026 |
| Registry name | io.github.flujo-app/mcp-virtual-computer |
More cloud and devops servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
