Every MCP workspace, organized.
Save project folders, tunnel IDs, runtime keys, ports, and launch settings per profile. Switch contexts without rebuilding your setup every time.
A polished desktop control center for MCP profiles, secure tunnels, validation, live status, and recovery — so connecting ChatGPT to local tools feels like a product, not a terminal ritual.
/home/dev/projects/mirinserena start-mcp-servertunnel_6a85••••80bc6PASS profile_load mirin-mcp-local.yaml
PASS runtime_api_key secured
PASS tunnel_id configured
INFO secure tunnel connected
AI client session active
Stop keeping setup commands, terminal windows, tunnel IDs, and connection state in your head. Put the operational layer where it belongs: behind a clear, dependable interface.
$ set CONTROL_PLANE_API_KEY=••••
$ tunnel-client doctor --profile...
$ serena start-mcp-server...
$ tunnel-client run...
error: connection interrupted
Everything needed to configure, validate, connect, observe, and recover local MCP sessions — without turning your desktop into a wall of terminals.
Save project folders, tunnel IDs, runtime keys, ports, and launch settings per profile. Switch contexts without rebuilding your setup every time.
Validate configuration, keys, tunnel reachability, MCP targets, and runtime dependencies with clear pass/fail states before starting a session.
Launch your local MCP server through an OpenAI Secure MCP Tunnel without exposing a raw local service directly to the public internet.
Follow streaming logs and state transitions across Ready, Connected, AI Active, and Standby so you always know what the agent is doing.
Detect interrupted tunnel or MCP processes and recover quickly, reducing the need to babysit command-line windows during long AI coding sessions.
Run from the system tray, surface meaningful status notifications, and manage multiple active profiles from one focused control surface.
Tunnel Manager coordinates the pieces that usually live across scripts and terminals, while your source code and local MCP tools stay on your machine.
Select a saved profileProject, runtime key, tunnel ID, and MCP target load together.
Validate the complete chainSee exactly what passes and what needs attention before startup.
Start and observeLaunch the MCP process and tunnel, then monitor live activity from one UI.
Controls enable and disable with the current process state. Validation remains visible. Running actions cannot be started twice. The UI tells you what the system can do right now.
Tunnel Manager is designed around the secure tunnel workflow rather than opening a raw local MCP endpoint to the internet. Sensitive runtime values stay in the desktop control layer while the tunnel provides the bridge.
Secure tunnel pathUse OpenAI Secure MCP Tunnels instead of public raw ports.
Runtime key handlingKeep platform credentials associated with the profile that needs them.
Local process visibilitySee exactly which local target is configured and running.
The current desktop workflow centers on Windows development environments, with the product architecture evolving toward broader desktop coverage.
WindowsPrimary desktop target
AvailablemacOSCross-platform roadmap
PlannedLinuxCross-platform roadmap
PlannedThe manager keeps setup, validation, startup, and runtime state in one flow so the first connection is understandable and repeatable.
Choose the local project folder and save the MCP target, tunnel ID, runtime key, and launch settings together.
Run Doctor before startup to verify the profile, credentials, tunnel configuration, MCP target, and local runtime.
Launch the MCP process and secure tunnel from one state-aware control surface.
Add the generated connector in ChatGPT, then watch the manager surface Connected, AI Active, and Standby states.
Keep the runtime close to the code and let Tunnel Manager coordinate the connection layer around it.
Clear expectations around local access, profiles, validation, and platform support.
No. The intended workflow uses an OpenAI Secure MCP Tunnel instead of publishing a raw local MCP port publicly.
Yes. Profiles are designed to keep project-specific folders, tunnel settings, keys, ports, and launch commands together so you can switch contexts quickly.
The failed check remains visible and start actions can stay unavailable until the required configuration is ready. This keeps the UI aligned with the real runtime state.
Windows is the current desktop target. macOS and Linux are shown as roadmap targets and should not be treated as released builds yet.
Spend less time managing tunnels and terminals. Spend more time letting AI work with the tools and projects on your machine.