Back to MCP Servers
🧩

MCP Virtual Computer

API key required

A persistent Docker or Fly computer with a Three.js interface and optional live Xfce desktop.

To add MCP Virtual Computer to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 8 environment variables, listed below.

CloudDevTools

Install

uvx mcp-virtual-computer@0.2.11

Environment variables

BACKENDSet in your MCP config
COMPUTER_IDSet in your MCP config
DESKTOP_ENVIRONMENTSet in your MCP config
NETWORK_ACCESSSet in your MCP config
AUTO_INSTALL_DOCKERSet in your MCP config
AUTO_INSTALL_FLYCTLSet in your MCP config
FLY_API_TOKENSet in your MCP config
EXPOSE_LIFECYCLE_TOOLSSet in your MCP config

Install with your client

Terminal
claude mcp add mcp-virtual-computer --env BACKEND=<YOUR_BACKEND> --env COMPUTER_ID=<YOUR_COMPUTER_ID> --env DESKTOP_ENVIRONMENT=<YOUR_DESKTOP_ENVIRONMENT> --env NETWORK_ACCESS=<YOUR_NETWORK_ACCESS> --env AUTO_INSTALL_DOCKER=<YOUR_AUTO_INSTALL_DOCKER> --env AUTO_INSTALL_FLYCTL=<YOUR_AUTO_INSTALL_FLYCTL> --env FLY_API_TOKEN=<YOUR_FLY_API_TOKEN> --env EXPOSE_LIFECYCLE_TOOLS=<YOUR_EXPOSE_LIFECYCLE_TOOLS> -- uvx mcp-virtual-computer@0.2.11

Run this in a terminal to add the server to Claude Code.

What this does

MCP Virtual Computer exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

BACKEND
COMPUTER_ID
DESKTOP_ENVIRONMENT
NETWORK_ACCESS
AUTO_INSTALL_DOCKER
AUTO_INSTALL_FLYCTL
FLY_API_TOKEN
EXPOSE_LIFECYCLE_TOOLS

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Frequently asked questions

How do I install MCP Virtual Computer?

Run the Claude Code command in the install section to add MCP Virtual Computer to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with MCP Virtual Computer?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to MCP Virtual Computer as well.

Does MCP Virtual Computer need an API key?

Yes. Before it can run, set these environment variables: BACKEND, COMPUTER_ID, DESKTOP_ENVIRONMENT, NETWORK_ACCESS, AUTO_INSTALL_DOCKER, AUTO_INSTALL_FLYCTL, FLY_API_TOKEN, EXPOSE_LIFECYCLE_TOOLS. They go in the env block of your MCP config.

Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.

Is this your MCP server?

Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.

Listed on clauderules.net

Add this badge to your README

Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.

Markdown
[![Listed on clauderules.net](https://clauderules.net/api/badge/io-github-flujo-app-mcp-virtual-computer)](https://clauderules.net/mcp/io-github-flujo-app-mcp-virtual-computer)
HTML
<a href="https://clauderules.net/mcp/io-github-flujo-app-mcp-virtual-computer" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-flujo-app-mcp-virtual-computer" alt="Listed on clauderules.net" /></a>