docker · dvdksn · Feb 9, 2026 · Feb 10, 2026
@@ -11,30 +11,42 @@ weight: 10
 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: Get started with MCP Toolkit
-   description: Learn how to quickly install and use the MCP Toolkit to set up servers and clients.
-   icon: explore
-   link: /ai/mcp-catalog-and-toolkit/get-started/
- - 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 the MCP Toolkit to manage MCP servers and clients
-   icon: /icons/toolkit.svg
-   link: /ai/mcp-catalog-and-toolkit/toolkit/
- - title: Dynamic MCP
-   description: Discover and add MCP servers on-demand using natural language
-   icon: search
-   link: /ai/mcp-catalog-and-toolkit/dynamic-mcp/
- - title: MCP Gateway
-   description: Learn about the underlying technology that powers the MCP Toolkit
-   icon: developer_board
-   link: /ai/mcp-catalog-and-toolkit/mcp-gateway/
- - title: Docker Hub MCP server
-   description: Explore about the Docker Hub server for searching images, managing repositories, and more
-   icon: device_hub
-   link: /ai/mcp-catalog-and-toolkit/hub-mcp/
+  - title: Get started with MCP Toolkit
+    description: Learn how to quickly install and use the MCP Toolkit to set up servers and clients.
+    icon: explore
+    link: /ai/mcp-catalog-and-toolkit/get-started/
+  - title: MCP Catalog
+    description: Browse Docker's curated collection of verified MCP servers
+    icon: hub
+    link: /ai/mcp-catalog-and-toolkit/catalog/
+  - title: MCP Toolkit
+    description: Learn about the MCP Toolkit to manage MCP servers and clients
+    icon: /icons/toolkit.svg
+    link: /ai/mcp-catalog-and-toolkit/toolkit/
+  - title: MCP Gateway
+    description: Learn about the underlying technology that powers the MCP Toolkit
+    icon: developer_board
+    link: /ai/mcp-catalog-and-toolkit/mcp-gateway/
+  - title: Governance and policy controls
+    description: Control which MCP servers and tools users can access
+    icon: security
+    link: /ai/mcp-catalog-and-toolkit/governance/
+  - title: Dynamic MCP
+    description: Discover and add MCP servers on-demand using natural language
+    icon: search
+    link: /ai/mcp-catalog-and-toolkit/dynamic-mcp/
+  - title: Docker Hub MCP server
+    description: Use the Docker Hub MCP server to search images and manage repositories
+    icon: device_hub
+    link: /ai/mcp-catalog-and-toolkit/hub-mcp/
+  - title: Security FAQs
+    description: Common questions about MCP security, credentials, and server verification
+    icon: security
+    link: /ai/mcp-catalog-and-toolkit/faqs/
+  - title: E2B sandboxes
+    description: Cloud sandboxes for AI agents with built-in MCP Catalog access
+    icon: cloud
+    link: /ai/mcp-catalog-and-toolkit/e2b-sandboxes/
 ---
 
 {{< summary-bar feature_name="Docker MCP Catalog and Toolkit" >}}
@@ -45,47 +57,40 @@ and data sources. By connecting LLMs to local development tools, databases,
 APIs, and other resources, MCP extends their capabilities beyond their base
 training.
 
-Through a client-server architecture, applications such as Claude, ChatGPT, and
-[Gordon](/manuals/ai/gordon/_index.md) act as clients that send requests to MCP
-servers, which then process these requests and deliver the necessary context to
-AI models.
-
-MCP servers extend the utility of AI applications, but running servers locally
-also presents several operational challenges. Typically, servers must be
-installed directly on your machine and configured individually for each
-application. Running untrusted code locally requires careful vetting, and the
-responsibility of keeping servers up-to-date and resolving environment
-conflicts falls on the user.
+The challenge is that running MCP servers locally creates operational friction.
+Each server requires separate installation and configuration for every
+application you use. You run untrusted code directly on your machine, manage
+updates manually, and troubleshoot dependency conflicts yourself. Configure a
+GitHub server for Claude, then configure it again for Cursor, and so on. Each
+time you manage credentials, permissions, and environment setup.
 
 ## Docker MCP features
 
-Docker provides three integrated components that address the challenges of
-running local MCP servers:
-
-MCP Catalog
-: A curated collection of verified MCP servers, packaged and distributed as
-container images via Docker Hub. All servers are versioned, come with full
-provenance and SBOM metadata, and are continuously maintained and updated with
-security patches.
-
-MCP Toolkit
-: A graphical interface in Docker Desktop for discovering, configuring, and
-managing MCP servers. The Toolkit provides a unified way to search for servers,
-handle authentication, and connect them to AI applications.
+Docker solves these challenges by packaging MCP servers as containers and
+providing tools to manage them centrally. Docker provides three integrated
+components: the [MCP Catalog](/manuals/ai/mcp-catalog-and-toolkit/catalog/) for
+discovering servers, the [MCP
+Gateway](/manuals/ai/mcp-catalog-and-toolkit/mcp-gateway/) for running them,
+and the [MCP Toolkit](/manuals/ai/mcp-catalog-and-toolkit/toolkit/) for
+managing everything through Docker Desktop.
 
-MCP Gateway
-: The core open source component that powers the MCP Toolkit. The MCP Gateway
-manages MCP containers provides a unified endpoint that exposes your enabled
-servers to all AI applications you use.
+The [MCP Catalog](/manuals/ai/mcp-catalog-and-toolkit/catalog/) is where you
+find servers. Docker maintains 300+ verified servers, packaged as container
+images with versioning, provenance, and security updates. Servers run isolated
+in containers rather than directly on your machine. Organizations can create
+[custom catalogs](/manuals/ai/mcp-catalog-and-toolkit/catalog/#custom-catalogs)
+with approved servers for their teams.
 
-This integrated approach ensures:
+The [MCP Gateway](/manuals/ai/mcp-catalog-and-toolkit/mcp-gateway/) runs your
+servers and routes requests from AI applications to the right server. It
+handles containerized servers, remote servers, authentication, and lifecycle
+management. Every AI application connects to the Gateway, which means you
+configure credentials and permissions once instead of per-application.
 
-- Simplified discovery and setup of trusted MCP servers from a curated catalog
-  of tools
-- Centralized configuration and authentication from within Docker Desktop
-- A secure, consistent execution environment by default
-- Improved performance since applications can share a single server runtime,
-  compared to having to spin up duplicate servers for each application.
+The [MCP Toolkit](/manuals/ai/mcp-catalog-and-toolkit/toolkit/) provides a
+graphical interface in Docker Desktop for browsing catalogs, enabling servers,
+and connecting clients. You can also use the `docker mcp` CLI to manage
+everything from the terminal.
 
 ![MCP overview](./images/mcp-overview.svg)
 

@@ -1,86 +1,71 @@
 ---
 title: Docker MCP Catalog
-linkTitle: MCP Catalog
+linkTitle: 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, catalog, docker
 weight: 20
 ---
 
 {{< summary-bar feature_name="Docker MCP Catalog" >}}
 
-The [Docker MCP Catalog](https://hub.docker.com/mcp) is a centralized, trusted
-registry for discovering, sharing, and running MCP-compatible tools. Integrated
-with Docker Hub, it offers verified, versioned, and curated MCP servers
-packaged as Docker images. The catalog is also available in Docker Desktop.
+The [Docker MCP Catalog](https://hub.docker.com/mcp) is a curated collection of
+verified MCP servers, packaged as Docker images and distributed through Docker
+Hub. It solves common challenges with running MCP servers locally: environment
+conflicts, setup complexity, and security concerns.
 
-The catalog solves common MCP server challenges:
-
-- Environment conflicts. Tools often need specific runtimes that might clash
-  with existing setups.
-- Lack of isolation. Traditional setups risk exposing the host system.
-- Setup complexity. Manual installation and configuration slow adoption.
-- Inconsistency across platforms. Tools might behave unpredictably on different
-  operating systems.
-
-With Docker, each MCP server runs as a self-contained container. This makes it
-portable, isolated, and consistent. You can launch tools instantly using the
-Docker CLI or Docker Desktop, without worrying about dependencies or
-compatibility.
-
-## Key features
-
-- Extensive collection of verified MCP servers in one place.
-- Publisher verification and versioned releases.
-- Pull-based distribution using Docker infrastructure.
-- Tools provided by partners such as New Relic, Stripe, Grafana, and more.
+The catalog serves as the source of available MCP servers. Each server runs as
+an isolated container, making it portable and consistent across different
+environments.
 
 > [!NOTE]
 > E2B sandboxes now include direct access to the Docker MCP Catalog, giving developers
 > access to over 200 tools and services to seamlessly build and run AI agents. For
 > more information, see [E2B Sandboxes](sandboxes.md).
 
-## How it works
-
-Each tool in the MCP Catalog is packaged as a Docker image with metadata.
-
-- Discover tools on Docker Hub under the `mcp/` namespace.
-- Connect tools to your preferred agents with simple configuration through the
-  [MCP Toolkit](toolkit.md).
-- Pull and run tools using Docker Desktop or the CLI.
+## What's in the catalog
 
-Each catalog entry displays:
+The Docker MCP Catalog includes:
 
-- Tool description and metadata.
-- Version history.
-- List of tools provided by the MCP server.
-- Example configuration for agent integration.
+- Verified servers: All local servers are versioned with full provenance and SBOM
+  metadata
+- Partner tools: Servers from New Relic, Stripe, Grafana, and other trusted
+  partners
+- Docker-built servers: Locally-running servers built and digitally signed by
+  Docker for enhanced security
+- Remote services: Cloud-hosted servers that connect to external services like
+  GitHub, Notion, and Linear
 
-## Server deployment types
+You can browse the catalog at [hub.docker.com/mcp](https://hub.docker.com/mcp)
+or through the **Catalog** tab in Docker Desktop's MCP Toolkit.
 
-The Docker MCP Catalog supports both local and remote server deployments, each optimized for different use cases and requirements.
+### Local versus remote servers
 
-### Local MCP servers
+The catalog contains two types of servers based on where they run:
 
-Local MCP servers are containerized applications that run directly on your machine. All local servers are built and digitally signed by Docker, providing enhanced security through verified provenance and integrity. These servers run as containers on your local environment and function without internet connectivity once downloaded. Local servers display a Docker icon {{< inline-image src="../../desktop/images/whale-x.svg" alt="docker whale icon" >}} to indicate they are built by Docker.
+Local servers run as containers on your machine. They work offline once
+downloaded and offer predictable performance and complete data privacy. Docker
+builds and signs all local servers in the catalog.
 
-Local servers offer predictable performance, complete data privacy, and independence from external service availability. They work well for development workflows, sensitive data processing, and scenarios requiring offline functionality.
+Remote servers run on the provider's infrastructure and connect to external
+services. Many remote servers use OAuth authentication, which the MCP Toolkit
+handles automatically through your browser.
 
-### Remote MCP servers
+## Using servers from the catalog
 
-Remote MCP servers are hosted services that run on the provider's
-infrastructure and connect to external services like GitHub, Notion, and
-Linear. Many remote servers use OAuth authentication. When a remote server
-requires OAuth, the MCP Toolkit handles authentication automatically - you
-authorize access through your browser, and the Toolkit manages credentials
-securely. You don't need to manually create API tokens or configure
-authentication.
+To start using MCP servers from the catalog:
 
-Remote servers display a cloud icon in the catalog. For setup instructions, see
-[MCP Toolkit](toolkit.md#oauth-authentication).
+1. Browse servers in the [MCP Catalog](https://hub.docker.com/mcp) or in Docker
+   Desktop
+2. Enable servers through the MCP Toolkit
+3. Configure any required authentication (OAuth is handled automatically)
+4. Connect your AI applications to use the servers
 
-## Use an MCP server from the catalog
+For detailed step-by-step instructions, see:
 
-To use an MCP server from the catalog, see [MCP Toolkit](toolkit.md).
+- [Get started with MCP Toolkit](/manuals/ai/mcp-catalog-and-toolkit/get-started/) -
+  Quick start guide
+- [MCP Toolkit](/manuals/ai/mcp-catalog-and-toolkit/toolkit/) - Detailed usage
+  instructions
 
 ## Contribute an MCP server to the catalog
 
@@ -95,3 +80,119 @@ within 24 hours on:
 - The [Docker MCP Catalog](https://hub.docker.com/mcp).
 - The [Docker Hub](https://hub.docker.com/u/mcp) `mcp` namespace (for MCP
   servers built by Docker).
+
+## Custom catalogs
+
+Custom catalogs let you curate focused collections of recommended servers. You
+can package custom server implementations alongside public servers, distribute
+curated lists to your team, and define what agents can discover when using
+Dynamic MCP.
+
+Common use cases:
+
+- Curate a subset of servers from the Docker MCP Catalog that your organization
+  approves
+- Include community registry servers that aren't in the Docker catalog
+- Add your organization's private MCP servers
+- Control which versions of servers your team uses
+
+### Custom catalogs with Dynamic MCP
+
+Custom catalogs work particularly well with
+[Dynamic MCP](/manuals/ai/mcp-catalog-and-toolkit/dynamic-mcp/), where agents
+discover and add MCP servers on-demand during conversations. When you specify a
+custom catalog with the gateway, the `mcp-find` tool searches only within your
+curated catalog. If your catalog contains 20 servers instead of 300+, agents
+work within that focused set and can dynamically add servers as needed without
+manual configuration each time.
+
+This gives agents the autonomy to discover and use tools while keeping their
+options within boundaries your team defines.
+
+### Create and curate a catalog
+
+The most practical way to create a custom catalog is to fork the Docker catalog
+and then curate which servers to keep:
+
+```console
+$ docker mcp catalog fork docker-mcp my-catalog
+```
+
+This creates a copy of the Docker catalog with all available servers. Export it
+to a file where you can edit which servers to include:
+
+```console
+$ docker mcp catalog export my-catalog ./my-catalog.yaml
+```
+
+Edit `my-catalog.yaml` to remove servers you don't want, keeping only the ones
+your team needs. Each server is listed in the `registry` section. Import the
+edited catalog back:
+
+```console
+$ docker mcp catalog import ./my-catalog.yaml
+```
+
+View your curated catalog:
+
+```console
+$ docker mcp catalog show my-catalog
+```
+
+#### Alternative: Build incrementally
+
+You can also build a catalog from scratch. Start with an empty catalog or a
+template:
+
+```console
+$ docker mcp catalog create my-catalog
+```
+
+Or create a starter template with example servers:
+
+```console
+$ docker mcp catalog bootstrap ./starter-catalog.yaml
+```
+
+Add servers from other catalog files:
+
+```console
+$ docker mcp catalog add my-catalog notion ./other-catalog.yaml
+```
+
+### Use a custom catalog
+
+Use your custom catalog when running the MCP gateway. For static server
+configuration, specify which servers to enable:
+
+```console
+$ docker mcp gateway run --catalog my-catalog.yaml --servers notion,brave
+```
+
+For Dynamic MCP, where agents discover and add servers during conversations,
+specify just the catalog:
+
+```console
+$ docker mcp gateway run --catalog my-catalog.yaml
+```
+
+Agents can then use `mcp-find` to search for servers within your catalog and
+`mcp-add` to enable them dynamically.
+
+The `--catalog` flag points to a catalog file in `~/.docker/mcp/catalogs/`.
+
+### Share your catalog
+
+Share your catalog with your team by distributing the YAML file or hosting it
+at a URL:
+
+```console
+$ docker mcp catalog export my-catalog ./team-catalog.yaml
+```
+
+Team members can import it:
+
+```console
+$ docker mcp catalog import ./team-catalog.yaml
+$ docker mcp catalog import https://example.com/team-catalog.yaml
+```