Documentación offline Docker main
/ ó ⌘K
por @raupulus

Get started with Docker MCP Toolkit

main Documentación oficial Licencia Apache-2.0Descargado el 2026-09-15 Bundle .md (6.1 MB) ↓

En esta página

{{< summary-bar feature_name="Docker MCP Toolkit" >}}

[!NOTE] This page describes the MCP Toolkit interface in Docker Desktop 4.62 and later. Earlier versions have a different UI. Upgrade to follow these instructions exactly.

The Docker MCP Toolkit makes it easy to set up, manage, and run containerized Model Context Protocol (MCP) servers in profiles, and connect them to AI agents. It provides secure defaults and support for a growing ecosystem of LLM-based clients. This page shows you how to get started quickly with the Docker MCP Toolkit.

Setup#

Before you begin, make sure you meet the following requirements to get started with Docker MCP Toolkit.

  1. Download and install the latest version of Docker Desktop.
  2. Open the Docker Desktop settings and select Beta features.
  3. Select Enable Docker MCP Toolkit.
  4. Select Apply.

The Learning center in Docker Desktop provides walkthroughs and resources to help you get started with Docker products and features. On the MCP Toolkit page, the Get started walkthrough guides you through installing an MCP server, connecting a client, and testing your setup.

Alternatively, follow the step-by-step instructions on this page:

Once configured, your AI applications can use all the servers in your profile.

[!TIP] Prefer working from the terminal? See Use MCP Toolkit from the CLI for instructions on using the docker mcp commands.

Create a profile#

Profiles organize your MCP servers into collections. Create a profile for your work:

[!NOTE] If you're upgrading from a previous version of MCP Toolkit, your existing server configurations are already in a default profile. You can continue using the default profile or create new profiles for different projects.

  1. In Docker Desktop, select MCP Toolkit and select the Profiles tab.
  2. Select Create profile.
  3. Enter a name for your profile (e.g., "Frontend development").
  4. Optionally, add servers and clients now, or add them later.
  5. Select Create.

Your new profile appears in the profiles list.

Add MCP servers#

  1. In Docker Desktop, select MCP Toolkit and select the Catalog tab.
  2. Browse the catalog and select the servers you want to add.
  3. Select the Add to button and choose whether you want to add the servers to an existing profile, or create a new profile.

If a server requires configuration, a Configuration Required badge appears next to the server's name. You must complete the mandatory configuration before you can use the server.

You've now successfully added MCP servers to your profile. Next, connect an MCP client to use the servers in your profile.

Connect clients#

To connect a client to MCP Toolkit:

  1. In Docker Desktop, select MCP Toolkit and select the Clients tab.
  2. Find your application in the list.
  3. Select Connect to configure the client.

If your client isn't listed, you can connect the MCP Toolkit manually over stdio by configuring your client to run the gateway with your profile:

docker mcp gateway run --profile my_profile

For example, if your client uses a JSON file to configure MCP servers, you may add an entry like:

```json {title="Example configuration" { "servers": { "MCP_DOCKER": { "command": "docker", "args": ["mcp", "gateway", "run", "--profile", "my_profile"], "type": "stdio" } } }

Consult the documentation of the application you're using for instructions on
how to set up MCP servers manually.

## Verify connections

Refer to the relevant section for instructions on how to verify that your setup
is working:

- [Claude Code](#claude-code)
- [Claude Desktop](#claude-desktop)
- [OpenAI Codex](#codex)
- [Continue](#continue)
- [Cursor](#cursor)
- [Gemini](#gemini)
- [Goose](#goose)
- [LM Studio](#lm-studio)
- [OpenCode](#opencode)
- [Sema4.ai](#sema4)
- [Visual Studio Code](#vscode)
- [Zed](#zed)
- [Mistral Vibe](#mistral-vibe)

### Claude Code

If you configured the MCP Toolkit for a specific project, navigate to the
relevant project directory. Then run `claude mcp list`. The output should show
`MCP_DOCKER` with a "connected" status:

```console
$ claude mcp list
Checking MCP server health...

MCP_DOCKER: docker mcp gateway run - ✓ Connected

Test the connection by submitting a prompt that invokes one of your installed MCP servers:

$ claude "{{% param test_prompt %}}"

Claude Desktop#

Restart Claude Desktop and check the Search and tools menu in the chat input. You should see the MCP_DOCKER server listed and enabled:

Claude Desktop

Test the connection by submitting a prompt that invokes one of your installed MCP servers:

{{% param test_prompt %}}

Codex#

Run codex mcp list to view active MCP servers and their statuses. The MCP_DOCKER server should appear in the list with an "enabled" status:

$ codex mcp list
Name        Command  Args             Env  Cwd  Status   Auth
MCP_DOCKER  docker   mcp gateway run  -    -    enabled  Unsupported

Test the connection by submitting a prompt that invokes one of your installed MCP servers:

$ codex "{{% param test_prompt %}}"

Continue#

Launch the Continue terminal UI by running cn. Use the /mcp command to view active MCP servers and their statuses. The MCP_DOCKER server should appear in the list with a "connected" status:

   MCP Servers

   ➤ 🟢 MCP_DOCKER (🔧75 📝3)
     🔄 Restart all servers
     ⏹️ Stop all servers
     🔍 Explore MCP Servers
     Back

   ↑/↓ to navigate, Enter to select, Esc to go back

Test the connection by submitting a prompt that invokes one of your installed MCP servers:

$ cn "{{% param test_prompt %}}"

Cursor#

Open Cursor. If you configured the MCP Toolkit for a specific project, open the relevant project directory. Then navigate to Cursor Settings > Tools & MCP. You should see MCP_DOCKER under Installed MCP Servers:

Cursor

Test the connection by submitting a prompt that invokes one of your installed MCP servers:

{{% param test_prompt %}}

Gemini#

Run gemini mcp list to view active MCP servers and their statuses. The MCP_DOCKER should appear in the list with a "connected" status.

$ gemini mcp list
Configured MCP servers:

✓ MCP_DOCKER: docker mcp gateway run (stdio) - Connected

Test the connection by submitting a prompt that invokes one of your installed MCP servers:

$ gemini "{{% param test_prompt %}}"

Goose#

{{< tabs >}} {{< tab name="Desktop app" >}}

Open the Goose desktop application and select Extensions in the sidebar. Under Enabled Extensions, you should see an extension named Mcpdocker:

Goose desktop app

{{< /tab >}} {{< tab name="CLI" >}}

Run goose info -v and look for an entry named mcpdocker under extensions. The status should show enabled: true:

$ goose info -v
…
    mcpdocker:
      args:
      - mcp
      - gateway
      - run
      available_tools: []
      bundled: null
      cmd: docker
      description: The Docker MCP Toolkit allows for easy configuration and consumption of MCP servers from the Docker MCP Catalog
      enabled: true
      env_keys: []
      envs: {}
      name: mcpdocker
      timeout: 300
      type: stdio

{{< /tab >}} {{< /tabs >}}

Test the connection by submitting a prompt that invokes one of your installed MCP servers:

{{% param "test_prompt" %}}

LM Studio#

Restart LM Studio and start a new chat. Open the integrations menu and look for an entry named mcp/mcp-docker. Use the toggle to enable the server:

LM Studio

Test the connection by submitting a prompt that invokes one of your installed MCP servers:

{{% param "test_prompt" %}}

OpenCode#

The OpenCode configuration file (at ~/.config/opencode/opencode.json by default) contains the setup for MCP Toolkit:

{
  "mcp": {
    "MCP_DOCKER": {
      "type": "local",
      "command": ["docker", "mcp", "gateway", "run"],
      "enabled": true
    }
  },
  "$schema": "https://opencode.ai/config.json"
}

Test the connection by submitting a prompt that invokes one of your installed MCP servers:

$ opencode "{{% param "test_prompt" %}}"

Sema4.ai Studio#

In Sema4.ai Studio, select Actions in the sidebar, then select the MCP Servers tab. You should see Docker MCP Toolkit in the list:

Docker MCP Toolkit in Sema4.ai Studio

To use MCP Toolkit with Sema4.ai, add it as an agent action. Find the agent you want to connect to the MCP Toolkit and open the agent editor. Select Add Action, enable Docker MCP Toolkit in the list, then save your agent:

Editing an agent in Sema4.ai Studio

Test the connection by submitting a prompt that invokes one of your installed MCP servers:

{{% param test_prompt %}}

Visual Studio Code#

Open Visual Studio Code. If you configured the MCP Toolkit for a specific project, open the relevant project directory. Then open the Extensions pane. You should see the MCP_DOCKER server listed under installed MCP servers.

MCP_DOCKER installed in Visual Studio Code

Test the connection by submitting a prompt that invokes one of your installed MCP servers:

{{% param test_prompt %}}

Zed#

Launch Zed and open agent settings:

Opening Zed agent settings from command palette

Ensure that MCP_DOCKER is listed and enabled in the MCP Servers section:

MCP_DOCKER in Zed's agent settings

Test the connection by submitting a prompt that invokes one of your installed MCP servers:

{{% param test_prompt %}}

Mistral Vibe#

Mistral Vibe uses a TOML configuration file at ~/.vibe/config.toml. Add the MCP Toolkit as a stdio MCP server in the [[mcp_servers]] section:

{{< tabs >}} {{< tab name="Linux" >}}

[[mcp_servers]]
name = "MCP_DOCKER"
transport = "stdio"
command = ["docker"]
args = ["mcp", "gateway", "run", "--profile", "my_profile"]
startup_timeout_sec = 60
disabled = false

{{< /tab >}} {{< tab name="macOS" >}}

[[mcp_servers]]
name = "MCP_DOCKER"
transport = "stdio"
command = ["docker"]
args = ["mcp", "gateway", "run", "--profile", "my_profile"]
startup_timeout_sec = 60
disabled = false

{{< /tab >}} {{< tab name="Windows" >}}

On Windows, the Docker installation path (C:\Program Files\Docker\...) contains a space. Use a list for command with the full path to docker.exe, and add PROGRAMFILES and PROGRAMDATA environment variables that the MCP Python SDK doesn't inherit by default:

[[mcp_servers]]
name = "MCP_DOCKER"
transport = "stdio"
command = ["C:/Program Files/Docker/Docker/resources/bin/docker.exe"]
args = ["mcp", "gateway", "run", "--profile", "my_profile"]
env = { PROGRAMFILES = "C:\\Program Files", PROGRAMDATA = "C:\\ProgramData" }
startup_timeout_sec = 60
disabled = false

{{< /tab >}} {{< /tabs >}}

The startup_timeout_sec = 60 is recommended because the Docker MCP Gateway takes approximately 15-25 seconds to start. The default timeout is 10 seconds, which isn't enough for the gateway to initialize.

Restart Vibe. In a Vibe CLI session, run /mcp to view active MCP servers. The MCP_DOCKER server should appear in the list:

$ vibe
> /mcp

Test the connection by submitting a prompt that invokes one of your installed MCP servers:

$ vibe "{{% param test_prompt %}}"

Further reading#