Publish the bundled McpNet Gateway through a public HTTPS endpoint without entering a host or port.
- Open the MCP Gateway page, sign up if needed, and download the Localtonet client for Windows, Linux, macOS, or Docker. McpNet Gateway is bundled and starts automatically on port 5050.
- Install and open Localtonet, then log in with the token from User Token. The bundled gateway never runs in Dev mode; set or change its admin token in Localtonet's Settings.
- Before exposing the gateway, scope each client's bearer token with
AllowedServerIdsorAllowedGroupIds. Leaving both empty grants access to every upstream server. - On the MCP Gateway page or under My Tunnels → MCP Gateway, configure:
- Process Type: Use Random SubDomain for testing, or a fixed subdomain if supported by your plan.
- Auth Token: Use Default Token for one machine. For multiple servers, select a client-specific token from User Token.
- Server: Select the region closest to your AI agents.
- Domain: Keep
localto.net, or choose a custom domain already added through DNS Manager.
Click Create, then click the green Start button.
- Configure the MCP client with the public endpoint and its client bearer token:
https://your-gateway.localto.net/mcp Authorization: Bearer YOUR_CLIENT_TOKEN
First-call timeout
If an upstream server uses npx, its first package download can take 60–120 seconds. McpNet has a 120-second per-server timeout, and the tool list updates on the next background refresh about 60 seconds later. Retry once before troubleshooting the tunnel.
