Connect Tunnel

Connect Tunnel is the customer-run agent that powers OpenAI's Secure MCP Tunnel.

  • Network Services
  • Tools & Utilities
Connect Tunnel is the customer-run agent that powers OpenAI's Secure MCP Tunnel. It connects a private or localhost MCP (Model Context Protocol) server to ChatGPT, Codex, the Responses API, and AgentKit through an OpenAI-hosted tunnel endpoint while keeping the server off the public internet. It is aimed at teams with an MCP server on a laptop, VM, or Kubernetes cluster that cannot open a new inbound firewall rule or public endpoint, and runs as an operator-visible daemon exposing health, readiness, metrics, and UI endpoints.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

67/100 Good

Maintained
100last commit 2 days ago
Popular
56650 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
304 GB minimum RAM
Security check
84no serious findings, 1 minor, tests
GitHub stars
650
Open issues
6
Last commit
2026-11-19
Latest release
v0.0.21
License
Apache-2.0
Activity
declining

Checked yesterday - source: GitHub (openai/tunnel-client)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 4 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install required tools first Before starting, install the tools the setup expects, including Redpanda, Python 3 (a common scripting tool), jq (a helper for working with JSON), and the rpk connect command (the Redpanda CLI command used for Connect). If any of these are missing, later setup commands can fail. source
  • Keep Docker running for startup If you start services with Docker Compose (a tool that launches several containers from one file), check that Docker is installed and running first. If Docker is not running, the command will not start the containers needed for the setup. source

Fetched 49 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need to open a new inbound firewall rule or public endpoint for my MCP server?

No; it is intended for cases where security will not approve a new inbound firewall rule or public endpoint, using an OpenAI-hosted tunnel endpoint to keep the MCP server off the public internet.

How do I verify the tunnel client is healthy before connecting a consumer?

The daemon exposes /healthz, /readyz, /metrics, and /ui endpoints for operator checks before a connector or API call depends on it.

Can I test it without running a separate MCP server?

Yes; with a runtime API key and tunnel ID you can run the built-in server_info, echo, and uppercase tools without a separate MCP server.

Do supporting client upgrades require configuration changes?

No; supporting clients work with existing services immediately, and corrections are enabled separately after client release.

Answers sourced from github.com

Community

Collected 49 days ago - public community threads