Expose a local MCP server over HTTPS

tunnel.to gives an MCP server running locally a public HTTPS endpoint so remote AI agents and applications can reach it without inbound port forwarding.

Build and debug the MCP server on your own machine while tunnel.to provides the public path back to it.

tunnelto 3000
Install the client Read the quick start
Public HTTPS
No inbound ports
No firewall rules
Anonymous tunnels

Local MCP development without deployment

A remote MCP client cannot connect to http://localhost:3000 on your computer because localhost refers to the machine running that client. A reverse tunnel gives the client a public route back to your development server.

Remote AI client
https://<generated-host>.tunnel.to
tunnel.to outbound connection
http://localhost:3000
Local MCP server

Your server, logs, debugger, code, and development environment stay local.

Use tunnel.to for MCP when you need to

  • Develop and debug an MCP server locally
  • Connect a remote agent to a development MCP server
  • Test an HTTP-based MCP transport
  • Demo an MCP tool without deploying it
  • Give a temporary remote environment access to a local MCP endpoint

Start temporary, keep it if needed

Try it

localhost → anonymous public URL

Keep it

localhost → persistent tunnel.to hostname

Own it

localhost → custom domain + access controls

Secure the public endpoint

A public MCP endpoint is reachable from the internet. Use application authentication or tunnel access controls for tools that should not be publicly callable, and avoid placing secrets in URLs.

Protect a tunnel with authentication Use a custom domain

Related guides

Read the tunnel.to documentationProtect a tunnelReserve a persistent hostnameTest webhooks on localhost

Frequently asked questions

Can I expose an MCP server running on localhost?

Yes, if it uses an HTTP transport supported by a standard HTTPS reverse tunnel.

Do I need to deploy my MCP server first?

No. It can continue running locally while tunnel.to provides the public endpoint.

Does every MCP server use SSE?

No. MCP transport behavior depends on the server and client. Current implementations commonly use Streamable HTTP; older implementations may use an HTTP-and-SSE transport.

Should a public MCP endpoint require authentication?

Use authentication or application-level access controls whenever the endpoint should not be callable by anyone on the internet.

The shortest path from localhost to public HTTPS.

Start anonymously. Add a stable hostname or custom domain when you need one.

Install tunnelto