Skip to content

Commit 1c5b9d8

Browse files
ArthurFlagArthurFlag
committed
mcp toolkit: native tab
1 parent f4f1a45 commit 1c5b9d8

File tree

5 files changed

+69
-92
lines changed

5 files changed

+69
-92
lines changed

‎content/manuals/ai/gordon/mcp/gordon-mcp-server.md‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,6 @@ aliases:
66
- /desktop/features/gordon/mcp/gordon-mcp-server/
77
---
88

9-
## Gordon as an MCP server
10-
119
In addition to functioning as an MCP client, Gordon can also act as an MCP
1210
server. This means that all the tools configured in the toolbox section of
1311
Gordon can be exposed to another MCP client like Claude Desktop, Cursor and

‎content/manuals/ai/mcp-catalog-and-toolkit/_index.md‎

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,15 @@ The Model Context Protocol (MCP) is a modern standard that transforms AI agents
2525

2626
As agents move into production, MCP solves common integration challenges — interoperability, reliability, and security — by providing a consistent, decoupled, and scalable interface between agents and tools. Just as containers redefined software deployment, MCP is reshaping how AI systems interact with the world.
2727

28+
> **Example**
29+
>
30+
> In simple terms, an MCP server is a way for an LLM to interact with an external system.
31+
>
32+
> For example:
33+
> If you ask a model to create a meeting, it needs to communicate with your calendar app to do that.
34+
> An MCP server for your calendar app provides _tools_ that perform atomic actions, such as:
35+
> "getting the details of a meeting" or "creating a new meeting".
36+
2837
## What is Docker MCP Catalog and Toolkit?
2938

3039
Docker MCP Catalog and Toolkit is a comprehensive solution for securely building, sharing, and running MCP tools. It simplifies the developer experience across four key areas:
@@ -38,6 +47,6 @@ With Docker Hub and the Docker Desktop extension, you can:
3847

3948
- Launch MCP servers in seconds
4049
- Add tools via CLI or GUI
41-
- Rely on Docker’s pull-based infrastructure for trusted delivery
50+
- Rely on Docker's pull-based infrastructure for trusted delivery
4251

4352
{{< grid >}}

‎content/manuals/ai/mcp-catalog-and-toolkit/catalog.md‎

Lines changed: 12 additions & 59 deletions
Original file line numberDiff line numberDiff line change
@@ -4,30 +4,32 @@ description: Learn about the benefits of the MCP Catalog, how you can use it, an
44
keywords: docker hub, mcp, mcp servers, ai agents, calatog, docker
55
---
66

7-
The [Docker MCP Catalog](https://hub.docker.com/catalogs/mcp) is a centralized, trusted registry for discovering, sharing, and running MCP-compatible tools. Seamlessly integrated into Docker Hub, it offers verified, versioned, and curated MCP servers packaged as Docker images.
7+
The [Docker MCP Catalog](https://hub.docker.com/catalogs/mcp) is a centralized, trusted registry for discovering, sharing, and running MCP-compatible tools. Seamlessly integrated into Docker Hub, it offers verified, versioned, and curated MCP servers packaged as Docker images. The catalog is also available in Docker Desktop.
88

9-
The catalog also solves common MCP server challenges:
9+
The catalog solves common MCP server challenges:
1010

1111
- Environment conflicts: Tools often need specific runtimes that may clash with existing setups.
1212
- Lack of isolation: Traditional setups risk exposing the host system.
1313
- Setup complexity: Manual installation and configuration result in slow adoption.
1414
- Inconsistency across platforms: Tools may behave unpredictably on different OSes.
1515

16-
With Docker, each MCP server runs as a self-contained container so it is portable, isolated, and consistent. You can launch tools instantly using Docker CLI or Docker Desktop, without worrying about dependencies or compatibility.
16+
With Docker, each MCP server runs as a self-contained container so it is
17+
portable, isolated, and consistent. You can launch tools instantly using Docker
18+
CLI or Docker Desktop, without worrying about dependencies or compatibility.
1719

1820
## Key features
1921

2022
- Over 100 verified MCP servers in one place
2123
- Publisher verification and versioned releases
22-
- Pull-based distribution using Docker’s infrastructure
24+
- Pull-based distribution using Docker's infrastructure
2325
- Tools provided by partners such as New Relic, Stripe, Grafana, and more
2426

2527
## How it works
2628

27-
Each tool in the MCP Catalog is packaged as a Docker image with metadata. Developers can:
29+
Each tool in the MCP Catalog is packaged as a Docker image with metadata:
2830

29-
- Discover tools via Docker Hub under the mcp/ namespace.
30-
- Connect tools to their preferred agents with simple configuration through the [MCP Toolkit](toolkit.md)
31+
- Discover tools via Docker Hub under the `mcp/` namespace.
32+
- Connect tools to their preferred agents with simple configuration through the [MCP Toolkit](toolkit.md).
3133
- Pull and run tools using Docker Desktop or the CLI.
3234

3335
Each catalog entry provides:
@@ -36,59 +38,10 @@ Each catalog entry provides:
3638
- Version history
3739
- Example configuration for agent integration
3840

39-
## Example: How to use an MCP server from Docker Hub
41+
## Use an MCP server from the catalog
4042

41-
The following example uses the Puppeteer MCP server to take a screenshot of a website and invert the colors using Claude Desktop.
42-
43-
{{< tabs >}}
44-
{{< tab name="Using the MCP Toolkit (Recommended)" >}}
45-
46-
1. Make sure you have [installed the Docker Desktop Docker MCP Toolkit extension](toolkit.md).
47-
2. From the extension, search for the Puppeteer MCP server in the **MCP Servers** tab, and toggle it on to enable.
48-
3. From the **MCP Clients** tab, select the **Connect** button for Claude Desktop.
49-
4. Within Claude Desktop, submit the following prompt using the Sonnet 3.5 model:
50-
51-
```text
52-
Take a screenshot of docs.docker.com and then invert the colors
53-
```
54-
55-
{{< /tab >}}
56-
{{< tab name="Manually set it up" >}}
57-
58-
1. Update the `claude_desktop_config.json` file to include the following configuration:
59-
60-
```json
61-
{
62-
"mcpServers": {
63-
"puppeteer": {
64-
"command": "docker",
65-
"args": [
66-
"run",
67-
"-i",
68-
"--rm",
69-
"-e",
70-
"DOCKER_CONTAINER",
71-
"mcp/puppeteer"
72-
],
73-
"env": {
74-
"DOCKER_CONTAINER": "true"
75-
}
76-
}
77-
}
78-
}
79-
```
80-
2. Restart Claude Desktop to apply the changed config file.
81-
3. Submit the following prompt using the Sonnet 3.5 model:
82-
83-
```text
84-
Take a screenshot of docs.docker.com and then invert the colors
85-
```
86-
87-
Once you've given your consent to use the new tools, Claude spins up the Puppeteer MCP server inside a container, navigates to the target URL, captures and modify the page, and returns the screenshot.
88-
89-
{{< /tab >}}
90-
{{< /tabs >}}
43+
To use an MCP server from the catalog, see [MCP toolkit](toolkit.md).
9144

9245
## Contribute an MCP server to the catalog
9346

94-
If you would like to add you MCP server to the Docker MCP Catalog, fill out the Docker [MCP submission form](https://www.docker.com/products/mcp-catalog-and-toolkit/#get_updates).
47+
To add an MCP server to the Docker MCP catalog, fill out the Docker [MCP submission form](https://www.docker.com/products/mcp-catalog-and-toolkit/#get_updates).

‎content/manuals/ai/mcp-catalog-and-toolkit/toolkit.md‎

Lines changed: 47 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -1,53 +1,72 @@
11
---
22
title: MCP Toolkit
3-
description:
4-
keywords:
3+
description:
4+
keywords: MCP server, MCP toolkit
55
---
66

7-
The Docker MCP Toolkit is a Docker Desktop extension local that enables seamless setup, management, and execution of containerized MCP servers and their connections to AI agents. It removes the friction from tool usage by offering secure defaults, one-click setup, and support for a growing ecosystem of LLM-based clients. It is the fastest path from MCP tool discovery to local execution.
7+
The Docker MCP Toolkit enables seamless setup, management, and execution of containerized MCP servers and their connections to AI agents. It removes the friction from tool usage by offering secure defaults, one-click setup, and support for a growing ecosystem of LLM-based clients. It is the fastest path from MCP tool discovery to local execution.
88

99
## Key features
1010

1111
- Cross-LLM compatibility: Works out of the box with Claude Desktop, Cursor, Continue.dev, and [Gordon](/manuals/ai/gordon/_index.md).
1212
- Integrated tool discovery: Browse and launch MCP servers that are available in the Docker MCP Catalog, directly from Docker Desktop.
1313
- No manual setup: Skip dependency management, runtime setup, and manual server configuration.
1414

15-
## How it works
15+
## Install an MCP server
1616

17-
The **MCP Servers** tab lists all available servers from the Docker MCP Catalog. Each entry includes:
17+
To install an MCP server:
1818

19-
- Tool name and description
20-
- Partner/publisher
21-
- Number of callable tools and what they are
19+
1. select **MCP Toolkit** and select the **Catalog** tab. Each server shows:
20+
21+
- Tool name and description
22+
- Partner/publisher
23+
- The list of callable tools the server provides.
2224

23-
To enable an MCP server, simply use the toggle switch to toggle it on.
25+
2. Find the MCP server of your choice and select **Add**.
26+
3. Optional: Some servers require extra configuration. To configure them, select
27+
the **Config** tab and follow the instructions available on the repository of the provider of the server.
28+
4. Optional: Install a corresponding MCP client from the **Clients** tab.
29+
30+
>[!NOTE]
31+
>If you have the MCP Toolkit extension installed, you can uninstall it.
2432
25-
> [!NOTE]
26-
>
27-
> Some MCP servers requires secrets or tokens to be configured before it can be enabled. Instructions on how to do this can be found on each MCP servers' repository.
33+
To learn more about the MCP server catalog, see [Catalog](catalog.md).
2834

29-
The **MCP Clients** tab lets you connect your enabled MCP servers to supported agents. Connection is as simple as selecting **Connect**, so you can switch between LLM providers without altering your MCP server integrations or security configurations.
35+
## Examples
3036

31-
## Installation
37+
### Use the GitHub MCP server
3238

33-
To install the Docker MCP Toolkit extension:
39+
Imagine you want to enable Ask Gordon to interact with your GitHub account:
3440

35-
1. In the Docker Desktop Dashboard, select the **Extensions** view, and then select **Manage**.
36-
2. Select the **Browse** tab and search for **Docker MCP Toolkit**.
37-
3. On the **Docker MCP Toolkit** result, select install.
38-
39-
The extension then appears under the **My extensions** tab.
40-
41-
### Example
42-
43-
The following example assumes you have already installed and set up Claude Desktop.
44-
45-
1. In the Docker MCP Toolkit extension, search for the Puppeteer MCP server in the **MCP Servers** tab, and toggle it on to enable.
46-
2. From the **MCP Clients** tab, select the **Connect** button for Claude Desktop.
41+
1. From the **MCP Toolkit** menu, select the **Catalog** tab and find
42+
the **GitHub Official** server and add it.
43+
2. In the server's **Config** tab, insert your token generated from
44+
your [GitHub account](https://github.com/settings/personal-access-tokens).
45+
3. In the Clients tab, ensure Gordon is connected.
46+
4. From the **Ask Gordon** menu, you can now send request related to your
47+
GitHub account, in accordance to the tools provided by the GitHub MCP server. To test it, ask Gordon:
48+
49+
```text
50+
What's my GitHub handle?
51+
```
52+
53+
>[!NOTE]
54+
>Make sure to allow Gordon to interact with GitHub by selecting **Always allow** in Gordon's answer.
55+
>
56+
57+
### Use Claude Desktop with Docker Desktop
58+
59+
If you have already installed and set up Claude Desktop, you can use Docker to
60+
set up Puppeteer instead of configuring Claude Desktop manually. Puppeteer is an
61+
MCP server that can interact with a web browser. To install it via Docker
62+
Desktop:
63+
64+
1. From the **MCP Toolkit** menu, select the **Catalog** tab and find the **Puppeteer** server and add it.
65+
2. From the **Clients** tab, select **Connect** next to **Claude Desktop**.
4766
3. Within Claude Desktop, submit the following prompt using the Sonnet 3.5 model:
4867

4968
```text
5069
Take a screenshot of docs.docker.com and then invert the colors
5170
```
5271

53-
Once you've given your consent to use the new tools, Claude spins up the Puppeteer MCP server inside a container, navigates to the target URL, captures and modify the page, and returns the screenshot.
72+
Once you've given your consent to use the new tools, Claude spins up the Puppeteer MCP server inside a container, navigates to the target URL, captures and modify the page, and returns the screenshot.

‎hugo_stats.json‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,6 @@
8080
"Mac-with-Apple-silicon",
8181
"Mac-with-Intel-chip",
8282
"Manually-create-assets",
83-
"Manually-set-it-up",
8483
"NetworkManager",
8584
"Node",
8685
"Non-compliant",
@@ -114,7 +113,6 @@
114113
"Use-OpenAI",
115114
"Using-the-CLI",
116115
"Using-the-GUI",
117-
"Using-the-MCP-Toolkit-Recommended",
118116
"VS-Code",
119117
"Vue",
120118
"WSL-2-backend-Arm-Early-Access",

0 commit comments

Comments
 (0)