MCP Tunnel

Name: MCP Tunnel
Author: leomercier

@leomercier

Repository

About MCP Tunnel

MCP server for accessing VM command line with web tunneling

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-tunnel": {
      "command": "npx",
      "args": [
        "mcp-cli"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Tunnel?

MCP Tunnel is a simple MCP server that allows accessing the command line of a VM machine. When started, it tunnels the host to the web so the VM can be accessed via the Model Context Protocol.

How to use MCP Tunnel?

Install globally with npm install -g mcp-cli and run mcp-cli, or run directly with npx mcp-cli. After starting, use the MCP tools execute_command and start_tunnel to send commands and create web tunnels. Optionally pass --no-tunnel to disable automatic tunneling.

Key features of MCP Tunnel

Execute shell commands on a VM through MCP
Web-based terminal interface for VM interaction
Automatic tunneling for remote accessibility
WebSocket-based real‑time communication

Use cases of MCP Tunnel

Remotely run shell commands on a virtual machine
Access a VM’s command line from any device with a web browser
Develop and test scripts via a web terminal interface
Expose a local VM temporarily over the internet

FAQ from MCP Tunnel

What are the prerequisites for MCP Tunnel?

Node.js version 18 or newer is required.

How can I start MCP Tunnel without automatic tunneling?

Add the --no-tunnel flag when starting, e.g., mcp-cli --no-tunnel or npm start -- --no-tunnel.

What MCP tools are available?

Two tools: execute_command (runs a shell command) and start_tunnel (creates a web tunnel with optional port and subdomain parameters).

How do I access the web interface?

After starting the tunnel, visit the URL provided by the tunnel service; the interface allows executing commands and seeing output in real time.

Is authentication or transport security mentioned?

The README does not specify authentication or transport security; it advises using strong auth mechanisms and limiting commands before exposing the tunnel.