publish updates from main

.vscode/docker.code-snippets

@@ -39,6 +39,16 @@
     ],
     "description": "Insert a Hugo tabs block with two tabs and snippet stops for names and content",
   },
+  "Insert Hugo code block (no title)": {
+    "prefix": ["codeblock", "block"],
+    "body": ["```${1:json}", "$2", "```", ""],
+    "description": "Insert a Hugo code block with an optional title",
+  },
+  "Insert Hugo code block (with title)": {
+    "prefix": ["codeblock", "codettl", "block"],
+    "body": ["```${1:json} {title=\"$2\"}", "$3", "```", ""],
+    "description": "Insert a Hugo code block with an optional title",
+  },
   "Insert a Button": {
     "prefix": ["button"],
     "body": ["{{< button url=\"$1\" text=\"$2\" >}}"],

assets/css/utilities.css

@@ -144,12 +144,8 @@
     font-size: 0.875em;
     border: 1px solid;
     border-radius: 0.25rem; /* theme("spacing.1") fallback */
-    background: var(--color-white-main);
-    border-color: var(--color-gray-300);
-    .dark & {
-      background: var(--color-gray-200);
-      border-color: var(--color-gray-400);
-    }
+    border: none;
+    background: transparent;
     &::before,
     &::after {
       content: none !important;
@@ -185,7 +181,7 @@
   }
 
   .highlight {
-    @apply my-4 overflow-x-auto p-3;
+    @apply my-0 overflow-x-auto p-2;
 
     /* LineTableTD */
     .lntd {

content/manuals/_index.md

@@ -42,7 +42,7 @@ params:
     link: /model-runner/
   - title: MCP Catalog and Toolkit
     description: Augment your AI workflow with MCP servers.
-    icon: /assets/icons/toolbox.svg
+    icon: /icons/toolkit.svg
     link: /ai/mcp-catalog-and-toolkit/
   products:
   - title: Docker Desktop

content/manuals/ai/gordon/mcp/_index.md

@@ -11,10 +11,6 @@ grid:
   description: Configure MCP tools on a per-project basis.
   icon: manufacturing
   link: /ai/gordon/mcp/yaml
-- title: MCP Server
-  description: Use Gordon as an MCP server
-  icon: dns
-  link: /ai/gordon/mcp/gordon-mcp-server/
 aliases:
  - /desktop/features/gordon/mcp/
 ---
@@ -33,4 +29,4 @@ external APIs, etc.
 Gordon, along with other MCP clients like Claude Desktop or Cursor, can interact
 with MCP servers running as containers.
 
-{{< grid >}}
+{{< grid >}}

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

@@ -5,39 +5,48 @@ params:
   sidebar:
     group: AI
     badge:
-      color: green
-      text: New
+      color: blue
+      text: Beta
 weight: 30
-description: Learn about Docker's MCP catalog on Docker Hub and how to use it with the MCP Toolkit extension
+description: Learn about Docker's MCP catalog on Docker Hub
 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
+   description: Learn about the MCP toolkit to manage MCP servers and clients
+   icon: /icons/toolkit.svg
    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.
 
+> **Example**
+> 
+> In simple terms, an MCP server is a way for an LLM to interact with an external system.
+> 
+> For example:
+> If you ask a model to create a meeting, it needs to communicate with your calendar app to do that.
+> An MCP server for your calendar app provides _tools_ that perform atomic actions, such as:
+> "getting the details of a meeting" or "creating a new meeting".
+
 ## 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:
+Docker MCP Catalog and Toolkit is a comprehensive solution for securely building, sharing, and running MCP tools. It simplifies the developer experience across these 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:
+With Docker Hub and the MCP Toolkit, you can:
 
 - Launch MCP servers in seconds
 - Add tools via CLI or GUI
-- Rely on Docker’s pull-based infrastructure for trusted delivery
+- Rely on Docker's pull-based infrastructure for trusted delivery
 
 {{< grid >}}

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

@@ -4,30 +4,32 @@ description: Learn about the benefits of the MCP Catalog, how you can use it, an
 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 [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.
 
-The catalog also solves common MCP server challenges:
+The catalog 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.
+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
+- 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:
+Each tool in the MCP Catalog is packaged as a Docker image with metadata:
 
-- Discover tools via Docker Hub under the mcp/ namespace.
-- Connect tools to their preferred agents with simple configuration through the [MCP Toolkit](toolkit.md)
+- 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:
@@ -36,59 +38,10 @@ Each catalog entry provides:
 - Version history
 - Example configuration for agent integration
 
-## Example: How to use an MCP server from Docker Hub
+## Use an MCP server from the catalog
 
-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 >}}
+To use an MCP server from the catalog, see [MCP toolkit](toolkit.md).
 
 ## 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).
+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).