docker · craig-osterhout · May 5, 2025 · May 4, 2025 · May 5, 2025
@@ -0,0 +1,43 @@
+---
+title: Docker MCP Catalog and Toolkit
+linkTitle: MCP Catalog and Toolkit
+params:
+  sidebar:
+    group: AI
+    badge:
+      color: green
+      text: New
+weight: 30
+description: Learn about Docker's MCP catalog on Docker Hub and how to use it with the MCP Toolkit extension
+keywords: Docker, ai, mcp servers, ai agents, extension, docker desktop, llm, docker hub
+grid:
+ - title: MCP Catalog
+   description: Learn about the benefits of the MCP Catalog, how you can use it, and how you can contribute
+   icon: hub
+   link: /ai/mcp-catalog-and-toolkit/catalog/
+ - title: MCP Toolkit
+   description: Learn about how to use the MCP Toolkit extension on Docker Desktop
+   icon: manufacturing
+   link: /ai/mcp-catalog-and-toolkit/toolkit/
+---
+
+The Model Context Protocol (MCP) is a modern standard that transforms AI agents from passive responders into action-oriented systems. By standardizing how tools are described, discovered, and invoked, MCP enables agents to securely query APIs, access data, and execute services across diverse environments.
+
+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.
+
+## What is Docker MCP Catalog and Toolkit?
+
+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:
+
+- Discovery: A central catalog with verified, versioned tools
+- Credential Management: OAuth-based and secure by default
+- Execution: Tools run in isolated, containerized environments
+- Portability: Use MCP tools across Claude, Cursor, VS Code, and more — no code changes needed
+
+With Docker Hub and the Docker Desktop extension, you can:
+
+- Launch MCP servers in seconds
+- Add tools via CLI or GUI
+- Rely on Docker’s pull-based infrastructure for trusted delivery
+
+{{< grid >}}
@@ -0,0 +1,94 @@
+---
+title: Docker MCP Catalog
+description: Learn about the benefits of the MCP Catalog, how you can use it, and how you can contribute
+keywords: docker hub, mcp, mcp servers, ai agents, calatog, docker
+---
+
+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 also solves common MCP server challenges:
+
+- Environment conflicts: Tools often need specific runtimes that may clash with existing setups.
+- Lack of isolation: Traditional setups risk exposing the host system.
+- Setup complexity: Manual installation and configuration result in slow adoption.
+- Inconsistency across platforms: Tools may behave unpredictably on different OSes.
+
+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.
+
+## Key features
+
+- Over 100 verified MCP servers in one place
+- Publisher verification and versioned releases
+- Pull-based distribution using Docker’s infrastructure
+- Tools provided by partners such as New Relic, Stripe, Grafana, and more
+
+## How it works
+
+Each tool in the MCP Catalog is packaged as a Docker image with metadata. Developers can:
+
+- Discover tools via Docker Hub under the mcp/ namespace.
+- Connect tools to their preferred agents with simple configuration through the [MCP Toolkit](toolkit.md)
+- Pull and run tools using Docker Desktop or the CLI.
+
+Each catalog entry provides:
+
+- Tool description and metadata
+- Version history
+- Example configuration for agent integration
+
+## Example: How to use an MCP server from Docker Hub
+
+The following example uses the Puppeteer MCP server to take a screenshot of a website and invert the colors using Claude Desktop.
+
+{{< tabs >}}
+{{< tab name="Using the MCP Toolkit (Recommended)" >}}
+
+1. Make sure you have [installed the Docker Desktop Docker MCP Toolkit extension](toolkit.md).
+2. From the extension, search for the Puppeteer MCP server in the **MCP Servers** tab, and toggle it on to enable.
+3. From the **MCP Clients** tab, select the **Connect** button for Claude Desktop. 
+4. Within Claude Desktop, submit the following prompt using the Sonnet 3.5 model:
+
+   ```text
+   Take a screenshot of docs.docker.com and then invert the colors
+   ```
+
+{{< /tab >}}
+{{< tab name="Manually set it up" >}}
+
+1. Update the `claude_desktop_config.json` file to include the following configuration:
+
+   ```json
+   {
+     "mcpServers": {
+       "puppeteer": {
+         "command": "docker",
+         "args": [
+           "run",
+           "-i",
+           "--rm",
+           "-e",
+           "DOCKER_CONTAINER",
+           "mcp/puppeteer"
+         ],
+         "env": {
+           "DOCKER_CONTAINER": "true"
+         }
+       }
+     }
+   }
+   ```
+2. Restart Claude Desktop to apply the changed config file.
+3. Submit the following prompt using the Sonnet 3.5 model:
+
+   ```text
+   Take a screenshot of docs.docker.com and then invert the colors
+   ```
+
+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.
+
+{{< /tab >}}
+{{< /tabs >}}
+
+## Contribute an MCP server to the catalog
+
+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).
@@ -0,0 +1,53 @@
+---
+title: MCP Toolkit
+description:
+keywords: 
+---
+
+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.
+
+## Key features
+
+- Cross-LLM compatibility: Works out of the box with Claude Desktop, Cursor, Continue.dev, and [Gordon](/manuals/ai/gordon/_index.md).
+- Integrated tool discovery: Browse and launch MCP servers that are available in the Docker MCP Catalog, directly from Docker Desktop.
+- No manual setup: Skip dependency management, runtime setup, and manual server configuration.
+
+## How it works
+
+The **MCP Servers** tab lists all available servers from the Docker MCP Catalog. Each entry includes:
+
+- Tool name and description
+- Partner/publisher
+- Number of callable tools and what they are
+
+To enable an MCP server, simply use the toggle switch to toggle it on.
+
+> [!NOTE]
+>
+> 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.
+
+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.
+
+## Installation
+
+To install the Docker MCP Toolkit extension:
+
+1. In the Docker Desktop Dashboard, select the **Extensions** view, and then select **Manage**.
+2. Select the **Browse** tab and search for **Docker MCP Toolkit**.
+3. On the **Docker MCP Toolkit** result, select install.
+
+The extension then appears under the **My extensions** tab.
+
+### Example
+
+The following example assumes you have already installed and set up Claude Desktop.
+
+1. In the Docker MCP Toolkit extension, search for the Puppeteer MCP server in the **MCP Servers** tab, and toggle it on to enable.
+2. From the **MCP Clients** tab, select the **Connect** button for Claude Desktop. 
+3. Within Claude Desktop, submit the following prompt using the Sonnet 3.5 model:
+
+   ```text
+   Take a screenshot of docs.docker.com and then invert the colors
+   ```
+
+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.
diff --git a/data/engine-cli/docker_image_build.yaml b/data/engine-cli/docker_image_build.yaml
@@ -51,7 +51,7 @@ long: |-
     file to exclude files and directories that you don't require in your build from
     being sent as part of the build context.
 
-    #### Accessing paths outside the build context
+    #### Access paths outside the build context
 
     The legacy builder will error out if you try to access files outside of the
     build context using relative paths in your Dockerfile.