MCP Virtual Computer MCP Server

MCP Virtual Computer is an MCP integration. A persistent Docker or Fly computer with a Three.js interface and optional live Xfce desktop.

Packages and local setup

The published pypi package is mcp-virtual-computer, version 0.2.11. Its declared MCP transport is stdio.

The package declares BACKEND: Computer provider. Use docker for a local container or fly for a permanent Fly Machine.; COMPUTER_ID (required): Stable identity of the one persistent computer.; DESKTOP_ENVIRONMENT: Start the real Xfce desktop instead of the virtual desktop.; NETWORK_ACCESS: Allow outbound network access from the computer.; AUTO_INSTALL_DOCKER: On Windows, install and start Docker Desktop lazily when needed.; AUTO_INSTALL_FLYCTL: Download flyctl into the user profile when it is missing.; FLY_API_TOKEN: Optional Fly API token. A cached flyctl login is also supported.; EXPOSE_LIFECYCLE_TOOLS: Also expose runtime status and network/desktop switching tools to the model. The MCP App can always use them..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.2.11 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.