Skip to main content
The rustunnel Claude Code tunnel plugin gives Claude Code full tunnel management without manual MCP configuration. Install the plugin, enter your token, and start asking Claude to expose local services. The plugin is a thin wrapper over the same MCP server any other MCP-compatible agent (Cursor, Windsurf, Claude Desktop, OpenClaw) can use.

​
How it works

The plugin bundles a skill definition (agent instructions) and an MCP server configuration. When you enable it, Claude Code:
  1. Prompts for your server address and API token (stored securely, entered once)
  2. Starts the rustunnel-mcp MCP server in the background
  3. Makes 6 tunnel management tools available to the agent

​
Installation

​
From the plugin marketplace

​
Manual install from source

Clone the repository and point Claude Code at the plugin directory:
To load it permanently, add it to your Claude Code settings:
During development, use /reload-plugins inside Claude Code to pick up file changes without restarting.

​
Setup

When you enable the plugin, you’ll be prompted for three values:
Get a token at rustunnel.com (hosted) or generate one with openssl rand -hex 32 for self-hosted servers.
These values are persisted by Claude Code — you won’t be asked again until you reconfigure.

​
Reconfiguring

To change your configuration after installation:
Run /reload-plugins after reconfiguring for changes to take effect.
The MCP server will not start until all three values are set. If you see a “Missing required user configuration value” error, run /plugin configure rustunnel to provide the missing values.

​
Prerequisites

The rustunnel CLI must be installed on your machine. The MCP server spawns it as a subprocess when create_tunnel is called.

​
Usage

Once installed, just ask Claude:
“Expose my local server on port 3000.”
“Open an HTTP tunnel to port 8080 with subdomain myapp.”
“Create a TCP tunnel to my PostgreSQL on port 5432.”
“List my active tunnels and close the one on port 3000.”

​
Available tools

See the MCP Server guide for full parameter tables and example responses.

​
Plugin vs manual MCP setup

​
Self-hosted servers

The plugin works with self-hosted rustunnel instances. When prompted for the server address and API URL, enter your own server’s values instead of the hosted defaults. See the Self-Hosting guide for server setup.

​
Security

  • The API token is stored securely by Claude Code (sensitive: true)
  • Tokens are transmitted over HTTPS to the rustunnel server
  • Tunnel subprocesses are cleaned up when the MCP server exits
  • Use --insecure only in local development with self-signed certificates

MCP server

Full reference for the rustunnel-mcp server the plugin wraps, including all tool parameters.

Agent integration

Wire rustunnel into Cursor, Windsurf, Cline, Codex, and other MCP clients.

Self-hosting

Stand up your own rustunnel server to use with the plugin.

rustunnel + Claude Code

Quick-start version of this page with install one-liners and an agent-ready prompt.