rustunnel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUSTUNNEL_TOKEN | No | rustunnel API token (rustunnel.com → Dashboard → API Keys). Optional at startup — the server boots and lists tools without it; tool calls need it. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_tunnelA | Open a tunnel to a locally running service and get a public URL. Use this when the user or task needs a public URL for a service running locally — webhook testing, sharing a dev server, or letting another agent or device reach localhost. Spawns the rustunnel CLI as a subprocess — the tunnel stays open until close_tunnel is called or the MCP server exits. Modes:
The token may be omitted if RUSTUNNEL_TOKEN is configured. |
| list_tunnelsA | List all tunnels currently open on this server. Returns the public URL, protocol, and traffic count for each active tunnel. Use this when you need to check whether a tunnel is still running, recover the public URL of an existing tunnel, or find a tunnel_id to pass to close_tunnel. |
| close_tunnelA | Force-close a specific tunnel by its ID. The public URL stops working immediately. Use this when a tunnel is no longer needed or public access must be revoked right away — e.g. after a webhook test or demo finishes. Use list_tunnels to find the tunnel_id. |
| get_connection_infoA | Get the CLI command (and, for load-balanced tunnels, a config file) needed to create a tunnel manually — without spawning anything. Use this when the MCP server cannot spawn subprocesses (e.g. cloud sandbox), when the tunnel must outlive the MCP server, or when you prefer to run the client yourself. Accepts the same arguments as create_tunnel. |
| list_regionsA | List available tunnel server regions with their IDs, names, and locations. Use this when you need to pick a specific |
| get_tunnel_historyA | Retrieve the history of past tunnels, including their duration and which token opened them. Use this when auditing past tunnel activity or debugging why a tunnel dropped or is no longer listed by list_tunnels. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/joaoh82/rustunnel'
If you have feedback or need assistance with the MCP directory API, please join our Discord server