Skip to content

Commit e6a939b

Browse files
committed
mcp: add instructions for verifying client connections
Signed-off-by: David Karlsson <[email protected]>
1 parent f8b70fe commit e6a939b

File tree

13 files changed

+304
-33
lines changed

13 files changed

+304
-33
lines changed

content/manuals/ai/mcp-catalog-and-toolkit/get-started.md

Lines changed: 300 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@ linkTitle: Get started
44
description: Learn how to quickly install and use the MCP Toolkit to set up servers and clients.
55
keywords: Docker MCP Toolkit, MCP server, MCP client, AI agents
66
weight: 10
7+
params:
8+
test_prompt: Use the GitHub MCP server to show me my open pull requests
79
---
810

911
{{< summary-bar feature_name="Docker MCP Toolkit" >}}
@@ -37,10 +39,10 @@ There are multiple ways to get started with Docker MCP Toolkit. You can:
3739
[add a client, and test your setup](#install-an-mcp-client-and-test-your-setup)
3840
with example prompts.
3941

40-
## Install an MCP server
42+
## Install MCP servers
4143

42-
{{< tabs group="release" >}}
43-
{{< tab name="From Docker Desktop">}}
44+
{{< tabs >}}
45+
{{< tab name="Docker Desktop">}}
4446

4547
1. In Docker Desktop, select **MCP Toolkit** and select the **Catalog** tab.
4648
2. Search for the **GitHub Official** server from the catalog and then select the plus icon to add it.
@@ -56,7 +58,7 @@ There are multiple ways to get started with Docker MCP Toolkit. You can:
5658
5. Search for the **Playwright** server from the catalog and add it.
5759

5860
{{< /tab >}}
59-
{{< tab name="From the Docker CLI">}}
61+
{{< tab name="CLI">}}
6062

6163
1. Add the GitHub Official MCP server. Run:
6264

@@ -85,54 +87,320 @@ There are multiple ways to get started with Docker MCP Toolkit. You can:
8587
{{< /tab >}}
8688
{{< /tabs >}}
8789

88-
You’ve now successfully added an MCP server. Next, install an MCP client and test your setup with an example prompt.
90+
You’ve now successfully added an MCP server. Next, connect an MCP client to use
91+
the MCP Toolkit in an AI application.
8992

90-
## Install an MCP client and test your setup
93+
## Connect clients
9194

92-
After you've installed MCP servers, you can add clients to the MCP Toolkit. These clients can interact with the installed MCP servers, turning the MCP Toolkit into a gateway. In the following section, let’s add the Claude Desktop client.
93-
94-
{{< tabs group="release" >}}
95-
{{< tab name="From Docker Desktop">}}
95+
To connect a client to MCP Toolkit:
9696

9797
1. In Docker Desktop, select **MCP Toolkit** and select the **Clients** tab.
98-
2. Find **Claude Desktop** and select **Connect**.
98+
2. Find your application in the list.
99+
3. Select **Connect** to configure the client.
99100

100-
If Claude Desktop isn't installed, select **Download** to install it, then select **Connect**.
101+
If your client isn't listed, you can connect the MCP Toolkit manually over
102+
`stdio` by configuring your client to run the following command:
101103

102-
3. Restart Claude Desktop if it's running, and it can now access all the servers in the MCP Toolkit.
103-
4. Open Claude Desktop and run a test by submitting the following prompt:
104+
```plaintext
105+
docker mcp gateway run
106+
```
104107

105-
```text
106-
Take a screenshot of the header element on docs.docker.com
107-
```
108+
For example, if your client uses a JSON file to configure MCP servers, you may
109+
add an entry like:
108110

109-
Claude prompts you for permissions and shares a screenshot of the header element from the Docker documentation page.
111+
```json {title="Example configuration"
112+
{
113+
"servers": {
114+
"MCP_DOCKER": {
115+
"command": "docker",
116+
"args": ["mcp", "gateway", "run"],
117+
"type": "stdio"
118+
}
119+
}
120+
}
121+
```
110122

111-
![Screenshot showing the header of Docker docs.](./images/claude-desktop-example.png)
123+
Consult the documentation of the application you're using for instructions on
124+
how to set up MCP servers manually.
112125

113-
{{< /tab >}}
114-
{{< tab name="From the Docker CLI">}}
126+
## Verify connections
115127

116-
1. In a terminal window, run the following commands to connect the Claude Desktop client:
128+
Refer to the relevant section for instructions on how to verify that your setup
129+
is working:
117130

118-
```console
119-
$ docker mcp client connect claude-desktop --global
120-
```
131+
- [Claude Code](#claude-code)
132+
- [Claude Desktop](#claude-desktop)
133+
- [OpenAI Codex](#codex)
134+
- [Continue](#continue)
135+
- [Cursor](#cursor)
136+
- [Gemini](#gemini)
137+
- [Goose](#goose)
138+
- [Gordon](#gordon)
139+
- [LM Studio](#lmstudio)
140+
- [OpenCode](#opencode)
141+
- [Sema4.ai](#sema4)
142+
- [Visual Studio Code](#vscode)
143+
- [Zed](#zed)
121144

122-
2. Restart Claude Desktop if it's running, and it can now access all the servers in the MCP Toolkit.
123-
3. Open Claude Desktop and run a test by submitting the following prompt using the Sonnet 4 model:
145+
### Claude Code
124146

125-
```text
126-
Take a screenshot of the header element on docs.docker.com
127-
```
147+
Verify the connection by running `claude mcp list`. The output should show
148+
`MCP_DOCKER` with a "connected" status:
149+
150+
```console
151+
$ claude mcp list
152+
Checking MCP server health...
153+
154+
MCP_DOCKER: docker mcp gateway run - ✓ Connected
155+
```
156+
157+
Test the connection by submitting a prompt that invokes one of your installed
158+
MCP servers:
159+
160+
```console
161+
$ claude "{{% param test_prompt %}}"
162+
```
163+
164+
### Claude Desktop
165+
166+
Restart Claude Desktop and check the **Search and tools** menu in the chat
167+
input. You should see the `MCP_DOCKER` server listed and enabled:
168+
169+
![Claude Desktop](images/claude-desktop.avif)
170+
171+
Test the connection by submitting a prompt that invokes one of your installed
172+
MCP servers:
173+
174+
```plaintext
175+
{{% param test_prompt %}}
176+
```
177+
178+
### OpenAI Codex {#codex}
179+
180+
Verify the connection by running `codex mcp list`:
181+
182+
```console
183+
$ codex mcp list
184+
Name Command Args Env Cwd Status Auth
185+
MCP_DOCKER docker mcp gateway run - - enabled Unsupported
186+
```
187+
188+
Test the connection by submitting a prompt that invokes one of your installed
189+
MCP servers:
190+
191+
```console
192+
$ codex "{{% param test_prompt %}}"
193+
```
194+
195+
### Continue
196+
197+
Launch the Continue terminal UI by running `cn`. Use the `/mcp` command to view
198+
active MCP servers and their statuses. The `MCP_DOCKER` server should appear in
199+
the list with a "connected" status:
200+
201+
```plaintext
202+
MCP Servers
203+
204+
➤ 🟢 MCP_DOCKER (🔧75 📝3)
205+
🔄 Restart all servers
206+
⏹️ Stop all servers
207+
🔍 Explore MCP Servers
208+
Back
209+
210+
↑/↓ to navigate, Enter to select, Esc to go back
211+
```
212+
213+
Test the connection by submitting a prompt that invokes one of your installed
214+
MCP servers:
215+
216+
```console
217+
$ cn "{{% param test_prompt %}}"
218+
```
219+
220+
### Cursor
221+
222+
Open Cursor and go to **Cursor Settings > Tools & MCP**. You should see
223+
`MCP_DOCKER` under **Installed MCP Servers**:
224+
225+
![Cursor](images/cursor.avif)
226+
227+
Test the connection by submitting a prompt that invokes one of your installed
228+
MCP servers:
229+
230+
```plaintext
231+
{{% param test_prompt %}}
232+
```
233+
234+
### Gemini
235+
236+
Verify the connection by running `gemini mcp list`:
237+
238+
```console
239+
$ gemini mcp list
240+
Configured MCP servers:
241+
242+
✓ MCP_DOCKER: docker mcp gateway run (stdio) - Connected
243+
```
244+
245+
Test the connection by submitting a prompt that invokes one of your installed
246+
MCP servers:
247+
248+
```console
249+
$ gemini "{{% param test_prompt %}}"
250+
```
251+
252+
### Gordon
128253

129-
Claude prompts you for permissions and shares a screenshot of the header element from the Docker documentation page.
254+
Open the **Ask Gordon** view in Docker Desktop and select the toolbox icon in
255+
the chat input area. The **MCP Toolkit** tab shows whether MCP Toolkit is
256+
enabled and displays all the provided tools:
130257

131-
![Screenshot showing the header of Docker docs.](./images/claude-desktop-example.png)
258+
![MCP Toolkit in the Ask Gordon UI](images/ask-gordon.avif)
259+
260+
Test the connection by submitting a prompt that invokes one of your installed
261+
MCP servers, either directly in Docker Desktop or using the CLI:
262+
263+
```console
264+
$ docker ai "{{% param "test_prompt" %}}"
265+
```
266+
267+
### Goose
268+
269+
{{< tabs >}}
270+
{{< tab name="Desktop app" >}}
271+
272+
Open the Goose desktop application and select **Extensions** in the sidebar.
273+
Under **Enabled Extensions**, you should see an extension named `Mcpdocker`:
274+
275+
![Goose desktop app](images/goose.avif)
276+
277+
{{< /tab >}}
278+
{{< tab name="CLI" >}}
279+
280+
Run `goose info -v` and look for an entry named `mcpdocker` under extensions.
281+
The status should show `enabled: true`:
282+
283+
```console
284+
$ goose info -v
285+
286+
mcpdocker:
287+
args:
288+
- mcp
289+
- gateway
290+
- run
291+
available_tools: []
292+
bundled: null
293+
cmd: docker
294+
description: The Docker MCP Toolkit allows for easy configuration and consumption of MCP servers from the Docker MCP Catalog
295+
enabled: true
296+
env_keys: []
297+
envs: {}
298+
name: mcpdocker
299+
timeout: 300
300+
type: stdio
301+
```
132302

133303
{{< /tab >}}
134304
{{< /tabs >}}
135305

306+
Test the connection by submitting a prompt that invokes one of your installed
307+
MCP servers:
308+
309+
```plaintext
310+
{{% param "test_prompt" %}}
311+
```
312+
313+
### LM Studio
314+
315+
Restart LM Studio and start a new chat. Open the integrations menu and look for
316+
an entry named `mcp/mcp-docker`. Use the toggle to enable the server:
317+
318+
![LM Studio](images/lm-studio.avif)
319+
320+
Test the connection by submitting a prompt that invokes one of your installed
321+
MCP servers:
322+
323+
```plaintext
324+
{{% param "test_prompt" %}}
325+
```
326+
327+
### OpenCode
328+
329+
The OpenCode configuration file (at `~/.config/opencode/opencode.json` by
330+
default) contains the setup for MCP Toolkit:
331+
332+
```json
333+
{
334+
"mcp": {
335+
"MCP_DOCKER": {
336+
"type": "local",
337+
"command": ["docker", "mcp", "gateway", "run"],
338+
"enabled": true
339+
}
340+
},
341+
"$schema": "https://opencode.ai/config.json"
342+
}
343+
```
344+
345+
Test the connection by submitting a prompt that invokes one of your installed
346+
MCP servers:
347+
348+
```console
349+
$ opencode "{{% param "test_prompt" %}}"
350+
```
351+
352+
### Sema4.ai Studio {#sema4}
353+
354+
In Sema4.ai Studio, select **Actions** in the sidebar, then select the **MCP
355+
Servers** tab. You should see Docker MCP Toolkit in the list:
356+
357+
![Docker MCP Toolkit in Sema4.ai Studio](./images/sema4-mcp-list.avif)
358+
359+
To use MCP Toolkit with Sema4.ai, add it as an agent action. Find the agent you
360+
want to connect to the MCP Toolkit and open the agent editor. Select **Add
361+
Action**, enable Docker MCP Toolkit in the list, then save your agent:
362+
363+
![Editing an agent in Sema4.ai Studio](images/sema4-edit-agent.avif)
364+
365+
Test the connection by submitting a prompt that invokes one of your installed
366+
MCP servers:
367+
368+
```plaintext
369+
{{% param test_prompt %}}
370+
```
371+
372+
### Visual Studio Code {#vscode}
373+
374+
In Visual Studio Code, select the **Extensions** icon in the activity bar. The
375+
Extensions pane should show the `MCP_DOCKER` server listed under installed MCP
376+
servers:
377+
378+
![MCP_DOCKER installed in Visual Studio Code](images/vscode-extensions.avif)
379+
380+
Test the connection by submitting a prompt that invokes one of your installed
381+
MCP servers:
382+
383+
```plaintext
384+
{{% param test_prompt %}}
385+
```
386+
387+
### Zed
388+
389+
Launch Zed and open agent settings:
390+
391+
![Opening Zed agent settings from command palette](images/zed-cmd-palette.avif)
392+
393+
Ensure that `MCP_DOCKER` is listed and enabled in the MCP Servers section:
394+
395+
![MCP_DOCKER in Zed's agent settings](images/zed-agent-settings.avif)
396+
397+
Test the connection by submitting a prompt that invokes one of your installed
398+
MCP servers:
399+
400+
```plaintext
401+
{{% param test_prompt %}}
402+
```
403+
136404
## Further reading
137405

138406
- [MCP Toolkit](/manuals/ai/mcp-catalog-and-toolkit/toolkit.md)
Binary file not shown.
Binary file not shown.
Binary file not shown.
16.4 KB
Binary file not shown.
43.6 KB
Binary file not shown.
19.9 KB
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.

0 commit comments

Comments
 (0)