For an open-source MCP gateway with explicit Claude Code setup instructions, Docker MCP Gateway is the best-documented starting point in the available sources. It can centralize MCP server configuration, organize servers into profiles, and let you manage tool access from a gateway connection. If you specifically want a self-hosted HTTP endpoint, R0Wi’s MCP Gateway documents a Docker Compose deployment and a Claude Code connection path. Neither project’s documentation alone is an independent security or performance assessment.
What an MCP gateway adds to Claude Code
Without a gateway, a client such as Claude Code connects to MCP servers through its configured server entries. A gateway can put a shared layer between the client and several servers: one client-facing connection can route requests to configured servers, while the gateway centralizes configuration and, depending on the implementation, credentials and access controls.
Docker describes its gateway as managing server lifecycle, credentials, access control, routing, and authentication. Its implementation uses profiles to group servers and documents controls for enabling or disabling individual tools. These are project-documented capabilities, not a guarantee that every deployment is secure by default.
Which open-source options document Claude Code setup?
Two projects in the available sources provide especially clear, direct setup instructions for Claude Code. This is a focused comparison, not a comprehensive ranking of every open-source MCP gateway.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →| Gateway | Documented Claude Code connection | Deployment and transport | Documented controls | What to verify |
|---|---|---|---|---|
| Docker MCP Gateway | docker mcp client connect claude-code --profile dev-tools --global; Docker’s setup guide uses claude mcp list to check the connection. |
Docker CLI plugin. The repository documents stdio operation and a streaming transport option; Docker Desktop’s MCP Toolkit can run it in the background. | Profiles, server lifecycle and routing, credentials and OAuth flows, and per-tool enable/disable controls. | Prerequisites and available features can vary by Docker version and environment. Docker’s invite-only AI Governance gateway offering is distinct from its open-source CLI gateway. |
| R0Wi MCP Gateway | claude mcp add --transport http gateway https://mcp.example.com/mcp; the repository also describes browser-based authorization. |
Self-hosted Docker Compose deployment with an HTTP MCP endpoint. The project suggests a reverse proxy for TLS. | The project describes login and consent, OAuth backends, and encrypted SQLite token storage. | These are project-maintainer claims. Review the source, configuration, release activity, and security posture before using it in a sensitive environment. |
Docker MCP Gateway
Docker’s CLI gateway is a natural first option if you want to manage multiple servers through profiles and prefer a project with a documented Claude Code workflow. Docker’s repository covers adding servers from catalog, OCI, registry, or local-file references, as well as enabling or disabling tools within a profile.
The documented desktop path lists Docker Desktop 4.59 or later with the MCP Toolkit enabled. The README also says the CLI can run independently, so do not assume the desktop prerequisite applies to every deployment. Requirements are subject to change; check the current Docker MCP Gateway README and release notes before setup.
R0Wi MCP Gateway
R0Wi is the alternative to examine when you want to host an HTTP-facing gateway yourself. Its README describes a Compose deployment, a configurable public URL, user and backend settings, an encryption key, and a browser login and consent flow. It also documents a Claude Code HTTP connection command. These details describe the project’s intended setup; they do not independently establish its security or reliability.
Connect and verify Docker MCP Gateway
- Choose a profile. Create or select a profile containing the MCP servers you intend Claude Code to use. Docker’s README describes adding servers from supported catalog, OCI, registry, or local-file references and managing individual tool availability within a profile.
- Connect Claude Code. From a shell, run the documented example, replacing the profile name if yours differs:
docker mcp client connect claude-code --profile dev-tools --global. Docker’s README also describesCLAUDE_CONFIG_DIRfor using a separate Claude Code configuration directory. - Check the connection. Run
claude mcp list. Docker’s getting-started guide says to confirm thatMCP_DOCKERappears as connected. - Test an actual tool. Submit a Claude Code prompt that exercises one of the MCP servers in the profile. A listed connection confirms setup visibility; a real tool call checks that the selected server is usable.
Docker documents both docker mcp gateway run for stdio and an example using --transport streaming. These are gateway operation modes in the repository documentation; choose according to the client and deployment path you configure.
Recommended Free Tools
For Docker’s step-by-step desktop setup, see Get started with Docker MCP Toolkit. For gateway behavior and the CLI, consult the MCP Gateway documentation.
Deploy R0Wi as an HTTP gateway
- Prepare its configuration. The project README instructs operators to copy a sample YAML configuration and set values including the public URL, users, backends, and encryption key.
- Start the service. Use the Docker Compose deployment described in the project README.
- Protect the public endpoint. The project advises putting the endpoint behind a reverse proxy for TLS, or otherwise configuring exposure intentionally.
- Add it in Claude Code. Replace the example host with your configured gateway address:
claude mcp add --transport http gateway https://mcp.example.com/mcp. - Complete authorization. The README describes a browser login and consent flow, along with OAuth backend connections.
See the R0Wi MCP Gateway README for its configuration and deployment details. The sample command’s host is illustrative; use the address actually configured for your instance.
Choose based on deployment and access needs
- Choose Docker when profiles, tool-level controls, and Docker’s documented Claude Code integration fit your workflow, and you want to manage gateway operation through Docker’s CLI or desktop tooling.
- Investigate R0Wi when you specifically need a self-hosted HTTP endpoint and are prepared to operate its Compose deployment, configure endpoint protection, and assess the project yourself.
- Compare the operational burden. Account for hosting and updating the gateway, downstream server images, credentials, authentication, and the endpoint exposed to Claude Code. A gateway centralizes configuration, but it also becomes part of the system you must maintain.
Security checks before connecting tools
A gateway is not automatically secure because its documentation describes security features. Before relying on one, verify how the configuration handles credentials, which tools are exposed, how downstream servers are isolated, what authentication protects the client-facing endpoint, how TLS is provided, and who is responsible for patching the gateway and server images.
Docker documents container-based server operation, credential handling through Docker Desktop secrets features, and controls over tools. R0Wi documents authentication and token-storage mechanisms. Treat both sets of statements as descriptions from the respective projects, not as security certifications or independent audits. The sources cited here establish no performance benchmark, security audit result, or comprehensive comparison across all open-source gateways.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
