npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

mcp-tunnel

v1.0.0

Published

MCP server for accessing VM command line with web tunneling

Downloads

9

Readme

MCP Tunnel

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

Features

  • Execute shell commands on a VM through MCP
  • Web-based terminal interface for VM interaction
  • Automatic tunneling to make the VM accessible from anywhere
  • WebSocket-based real-time communication

Prerequisites

  • Node.js (v18 or newer)

Installation and Usage

Running with npx (no installation)

npx mcp-tunnel

Global Installation

npm install -g mcp-tunnel
mcp-tunnel

Local Development

# Clone repository
git clone [repository-url]
cd mcp-tunnel

# Install dependencies
npm install

Development

Run the development server with hot-reloading for both backend and frontend:

npm run dev

Building

Build both the frontend and backend for production:

npm run build-all

Usage

  1. Start the MCP server:
# Start with automatic tunneling
npm start

# Start without automatic tunneling
npm start -- --no-tunnel

This will build the project and start the server. By default, a tunnel will be created automatically. Use the --no-tunnel flag to disable automatic tunneling.

  1. The server will start and provide output on stderr (to avoid interfering with MCP communication on stdout)

  2. Use MCP to interact with the server using the following tools:

Available MCP Tools

  • execute_command: Run a shell command on the VM
    • Parameters: { "command": "your shell command" }
  • start_tunnel: Create a web tunnel to access the VM interface
    • Parameters: { "port": 8080, "subdomain": "optional-subdomain" }

Web Interface

After starting the tunnel, you can access the web-based terminal interface at the URL provided by the tunnel. This interface allows you to:

  • Execute commands directly in the VM
  • See command outputs in real-time
  • Interact with the VM from any device with web access

Environment Variables

Create a .env file to configure the server:

# Server configuration
PORT=8080

# Localtunnel configuration
LOCALTUNNEL_SUBDOMAIN=your-preferred-subdomain

Security Considerations

This tool provides direct access to your VM's command line. Consider these security practices:

  • Use strong authentication mechanisms before exposing the tunnel
  • Limit the commands that can be executed through proper validation
  • Consider running in a restricted environment
  • Do not expose sensitive information through the tunnel