mcptunnels
Give a local MCP server a public URL with one command.
mcptunnels is a developer tools tool built by terragohan. It's best for Developers working with MCP servers and Teams needing to demo local MCP servers. Pricing is free.
Pricing
free
Audience
Developers working with MCP servers
Platforms
Community
0%
About mcptunnels
mcptunnels provides anonymous, ephemeral, and OAuth 2.1-protected tunnels for local MCP servers, allowing them to be exposed publicly with a single command without requiring accounts or signup.
mcptunnels is a command-line tool designed to expose local MCP (Model Context Protocol) servers to the public internet. It simplifies the process by requiring only one command to generate a public URL, eliminating the need for accounts, signups, or complex configurations. The service emphasizes anonymity and ephemerality, with tunnels expiring after 24 hours and being deleted server-side immediately upon process termination (Ctrl-C).
By default, mcptunnels secures public endpoints with OAuth 2.1, generating a password via the CLI. This security feature is designed to be automatically discovered by clients like ChatGPT, Claude, and Cursor. For use cases requiring open access, an `--no-auth` option is available. The tool also offers a self-hostable relay (`tunneld`) for users who prefer to manage their own infrastructure, though a hosted relay at `tunnel.mcptunnels.xyz` is provided by default.
Unlike generic tunneling solutions such as ngrok or cloudflared, mcptunnels is specifically tailored for MCP servers. It handles stdio to Streamable HTTP bridging, which is crucial for many MCP server setups, a feature not typically offered by generic tunnels. This makes it particularly useful for connecting AI clients to local servers, demonstrating servers to teammates without deployment, or testing servers during development. The project is currently in v1, with a roadmap including permanent tunnels to address user growth beyond ephemeral needs.
Key Features
Pricing
freemcptunnels is a free tool. The hosted relay at tunnel.mcptunnels.xyz is provided by default, and users can also self-host their own tunneld.
Who is it for?
Best for
- Quickly exposing a local MCP server to the internet
- Connecting AI clients to local development environments
- Demonstrating MCP server functionality without deployment
- Testing MCP servers against real clients during development
- Users prioritizing anonymity and ephemerality for public access
Not ideal for
- Exposing private data or critical production servers due to throwaway nature and relay operator transit
- Users requiring permanent, stable URLs (currently, but planned for future)
- Generic TCP/HTTP tunneling (while possible, it's optimized for MCP)
Integrations
Community Discussion
No discussions yet. Be the first to share your experience!