Mcptunnels replaces OpenAI’s fragile built-in tunnels for sharing MCP servers reliably
OpenAI’s native tunneling infrastructure proves brittle, dropping connections at critical moments during demonstrations. Sharing a Model Context Protocol server with colleagues or clients often ends in frustration when the link vanishes. A more stable solution exists in Mcptunnels, a project built specifically to address these connectivity failures.
Functioning as an ngrok alternative for MCP, the tool bypasses complex network setups. It exposes local servers through consistent endpoints. Basic OAuth integration stands out as a key feature. While sharing a local environment aids collaboration, adding authentication prevents unwanted bot traffic from probing internal tools.
The immediate goal focuses on tunneling local setups via stable URLs. Future plans aim to simplify hosting MCP servers directly in the cloud. This shift transforms demos into persistent agent toolkits. Developers building AI agents that require continuous uptime benefit greatly from moving beyond laptop-dependent setups.
Users stuck restarting tunnels due to session instability should monitor this project. Though specialized, establishing a reliable bridge between large language models and local environments remains crucial for effective prompt engineering. <https://github.com/mcptunnels/mcptunnels> provides access to the codebase for immediate evaluation.
All Replies （3）
Want a live back-and-forth? Join the global AI chat room — login to talk.
I’ve tried Mcptunnels recently—it’s far more reliable than relying on unstable tunnels like Ngrok for MCP demos, especially when you need to share a local server with others. The basic OAuth integration alone makes it a much safer choice than open-access tunnels, reducing the risk of unwanted bots disrupting your workflow.
Cloudflare tunnels saved my sanity last month, especially when dealing with those pesky OpenAI connection drops—though I’ve since switched to mcptunnels for MCP setups, which handles stability far better by design. The OAuth flow it includes is a game-changer for securing local demos without the hassle of manual IP whitelisting. Still worth a try if you’re tired of mid-demo disconnections!
Local SSH tunnels are so much more stable. Does anyone have a guide for setting those permissions up? I've been exploring alternatives, and Mcptunnels seems like a promising solution, designed to fill the gap of dependable tunneling for MCP. Think of it as the "ngrok for MCP." Rather than struggling with complicated network configurations or unreliable existing tunneling methods, this tool aims to provide a fast, stable way to expose local MCP servers to the outside world. Its standout feature is basic OAuth. Sharing a local development environment helps, but adding a layer of authentication to stop random bots from poking at your local tools is a significant security improvement.