You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updated prerequisites and clarified the use of tools for setting up the Docker MCP Toolkit. Added details on the expected output and confirmed environment readiness for AI-assisted migration.
Copy file name to clipboardExpand all lines: content/learning-paths/servers-and-cloud-computing/docker-mcp-toolkit/2-setup.md
+16-4Lines changed: 16 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,15 +8,19 @@ layout: learningpathall
8
8
9
9
## Before you begin
10
10
11
-
You need:
11
+
Make sure the following tools are installed:
12
12
13
13
- Docker Desktop 4.59 or later.
14
14
- VS Code with the GitHub Copilot extension.
15
-
- A GitHub account with a personal access token.
15
+
- A GitHub account with a Personal Access Token(PAT) that allows repository access.
16
16
- A machine with at least 8 GB RAM (16 GB recommended).
17
17
18
+
You will use Docker Desktop to host MCP servers locally, and VS Code with GitHub Copilot to invoke those servers through the MCP Gateway.
19
+
18
20
## Enable the Docker MCP Toolkit
19
21
22
+
The MCP Toolkit allows Docker Desktop to run and manage MCP (Model Context Protocol) servers, which expose structured tools that AI assistants can call.
23
+
20
24
1. Open Docker Desktop.
21
25
2. Go to **Settings** > **Beta features**.
22
26
3. Toggle **Enable Docker MCP Toolkit** on.
@@ -78,6 +82,14 @@ Open GitHub Copilot Chat in VS Code and ask:
78
82
What Arm migration tools do you have access to?
79
83
```
80
84
81
-
You should see tools from all three servers listed. If they appear, your setup is complete.
85
+
If the setup is correct, Copilot will list tools from:
86
+
87
+
- Arm MCP Server
88
+
- GitHub MCP Server
89
+
- Sequential Thinking MCP Server
90
+
91
+
This confirms that tool invocation through the MCP Gateway is working.
92
+
93
+
Your environment is now ready for AI-assisted migration.
82
94
83
-
In the next section, you will examine the demo application to understand what blocks its migration to Arm64.
95
+
In the next section, you will examine the demo application and identify the architecture-specific elements that require adaptation for Arm64.
0 commit comments