get_connection_info
Get the CLI command and config file needed to manually create a tunnel, avoiding subprocess spawning. Use when the MCP server cannot spawn processes or the tunnel must outlive the server.
Instructions
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.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| group | No | Load-balancing pool name (http/tcp only) | |
| token | No | API token. Optional if RUSTUNNEL_TOKEN is set. | |
| region | No | Region ID (e.g. 'eu', 'us', 'ap'). Omit to auto-select. | |
| secret | No | Shared secret for P2P (protocol='p2p') | |
| protocol | Yes | Tunnel type | |
| group_key | No | Shared secret for the load-balancing group | |
| peer_name | No | P2P publisher mode: publish under this name | |
| subdomain | No | Custom subdomain (HTTP only) | |
| local_host | No | Local hostname to forward to (default 'localhost') | |
| local_port | Yes | Local port the service is listening on | |
| peer_target | No | P2P subscriber mode: connect to this name | |
| health_check | No | Optional client-side health probe. The client probes the local service and reports health so the server routes around a sick backend. Only meaningful for load-balanced tunnels (group set). |