Skip to content
Docker MCP Gateway

Docker MCP Gateway

by Docker
Apache-2.0
Repository Docs
Developer Tools
dockermcp-gatewaycontainerssecurityoauthdevops

Summary

Docker's official CLI plugin that runs MCP servers in isolated containers behind one gateway — secrets management, OAuth flows and a single config every client shares.

Features

  • Runs each MCP server in an isolated Docker container
  • One gateway endpoint shared by every MCP client, so configs cannot drift
  • Secrets held in Docker Desktop's secrets store, not environment variables
  • Built-in OAuth flows for servers that need real authorisation
  • Dynamic discovery of tools, prompts and resources
  • List, inspect and call tools across servers from the CLI
  • Logging and call tracing for what the agent actually invoked

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Docker MCP Gateway" tools will be available.
{
  "mcpServers": {
    "docker-mcp-gateway": {
      "command": "docker",
      "args": [
        "mcp",
        "gateway",
        "run"
      ]
    }
  }
}

Description

Running a handful of MCP servers is fine. Running twenty across four clients is where it falls apart: each server is an npx or uvx process with full user privileges, credentials end up as plaintext environment variables in a config file, and every client keeps its own drifting copy of the list. The Docker MCP Gateway — the docker-mcp CLI plugin that powers the MCP Toolkit in Docker Desktop — is Docker's answer to that.

One gateway, many servers

Each server from the Docker MCP Catalog runs in its own isolated container, with npx and uvx servers granted minimal host privileges. Clients — VS Code, Cursor, Claude Desktop and others — connect to a single gateway rather than to each server, so they all see the same configuration and the same tool list.

Credentials and auth

Secrets are held in Docker Desktop's secrets management instead of environment variables, and the gateway implements OAuth flows for servers that need a real authorisation handshake rather than a static token.

Operations

Tools, prompts and resources are discovered dynamically as servers come up, so adding a server does not mean editing every client's JSON. The CLI can list servers and inspect or call their tools directly, and built-in logging and call tracing make it possible to see what an agent actually invoked.

Works inside Docker Desktop 4.59+ with the MCP Toolkit enabled, or standalone. Written in Go and developed in the open.

Related MCP Servers

MCP: HackerOne

by HackerOne

New

Official read-only MCP server for HackerOne bug bounty reports, programs, and remediation data.

Developer Tools
1 views

MCP: mcp-remote

by Glen Maddern

New

A proxy that lets local-only MCP clients connect to remote servers, handling OAuth and transport differences.

Developer Tools
1 views

MCP: Blender

by Siddharth Ahuja

New

Control Blender from an AI client — build scenes, apply materials, and run Python against the live session.

Developer Tools
2 views

MCP: E2B

by E2B

New

Run AI-generated code safely in an isolated cloud sandbox, with results returned as data rather than text.

Developer Tools
Browse all MCP servers →